Differences

This shows you the differences between two versions of the page.

--- server:replicant_to_master [2018/07/19 12:36] – Scott Cunliffe
+++ server:replicant_to_master [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Restoring Replicant Server To Master Server Status ======
+====== Restoring A Replicant Server To Master Server Status ======
+In the event of your master server going offline and you need to restore your replicant database from read only to fully functional master server you will need to:
+<note tip>Examples shown use fictional server addresses.  Your DB_CONFIG file will contain your DNS or IP addresses in the displayed code.</note>
 Navigate to TapeTrack Framework Server installation folder (default installation location C:\Program Files\TapeTrack\TapeTrack Framework Server)
@@ Line 9: / Line 13: @@
 Using the # symbol comment out the lines of code:
-<sxh>
+<code>
 rep_set_priority 0
 repmgr_site replicant-1.tapetrack.com 5010 db_local_site on
 repmgr_site master.tapetrack.com 5010 db_bootstrap_helper on
 rep_set_config DB_REP_CONF_BULK on
-</sxh>
+</code>
 to match the following example
-<sxh>
+<code>
 #rep_set_priority 0
 #repmgr_site replicant-1.tapetrack.com 5010 db_local_site on
 #repmgr_site master.tapetrack.com 5010 db_bootstrap_helper on
 #rep_set_config DB_REP_CONF_BULK on
-</sxh>
+</code>
 Save the file.
+[[server:start_stop|Restart the TapeTrack Framework Service]].
+The Framework server will now function as a master server and not a replicant.
+<note important>Any TapeTrack client software will need to use the DNS/IP connection to the appropriate server</note>
+{{tag> update_doco}}