TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • tmss10listdrstrategies • tmsslevelnames • groups • volume_flags • promedia_labels • tmssexceloutputpath • components • library_manager • tmss10sync • tmss10listusage
server:replication

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
server:replication [2021/10/19 23:32] – [Enabling Replication] Scott Cunliffeserver:replication [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Enabling Replication ====== ====== Enabling Replication ======
  
-The following information illustrates the steps required to enable a High Availability Replicant Server.  +The following information illustrates the steps required to enable a High Availability Replicant Server.  
 + 
 +All steps must be **performed in the order presented** to create a successful connection between the Master and Replicant Server.  
 + 
 +===== Prerequisites ===== 
 + 
 +Functional installation of TapeTrack Server running that will become the Master. 
 + 
 +IP addresses of both the Master and Replicant servers.  IP addresses included in the instructions are for demonstration only, these must be replaced with your correct values. 
 + 
 +You have made a **complete [[server:backups|backup]] of the Master database** before attempting any of these instructions to maintain the database information should you not complete the process successfully. 
  
-It is assumed that you already have a functional installation of TapeTrack Server running. 
  
-All steps must be **performed in the order presented** to create a successful connection between the Master and Replicant Server. 
  
-IP addresses included in the instructions are for demonstration only, these must be replaced with your correct values. 
  
-You have made a **complete [[server:backups|backup]] of the master database** before attempting any of these instructions to maintain the database information should you not complete the process successfully. 
 ===== Steps On Remote Server ===== ===== Steps On Remote Server =====
  
Line 30: Line 37:
 Edit the Replicant Server and Master Server host names in the [[server:DB_CONFIG|DB_CONFIG]] file. Edit the Replicant Server and Master Server host names in the [[server:DB_CONFIG|DB_CONFIG]] file.
   * Replace **replicant-1.tapetrack.com** with the IP address of **your** Replicant Server (your_replicant_IP_address used as Replicant IP example) and port number if not using the default 5100 value.   * Replace **replicant-1.tapetrack.com** with the IP address of **your** Replicant Server (your_replicant_IP_address used as Replicant IP example) and port number if not using the default 5100 value.
-  * Replace **master.tapetrack.com** with the IP address of **your** Master Server (your_master_IP_address used as Master IP example) and port number if not using the default 5100 value.+  * Replace **master.tapetrack.com** with the IP address of **your** Master Server (your_Master_IP_address used as Master IP example) and port number if not using the default 5100 value.
  
 <note important>Ensure you use the IP4 address for the Master and Replicant Server as using the domain name can cause issues with the IP6 address replacing the IP4 address, stopping the Master and Replicant communication.</note> <note important>Ensure you use the IP4 address for the Master and Replicant Server as using the domain name can cause issues with the IP6 address replacing the IP4 address, stopping the Master and Replicant communication.</note>
Line 42: Line 49:
 ===== Steps On Master Server ===== ===== Steps On Master Server =====
  
-[[server:start_stop|Stop the TapeTrack service on the master TapeTrack server]].+[[server:start_stop|Stop the TapeTrack service on the Master TapeTrack server]].
  
 Edit the TapeTrack\TapeTrack Framework Server\[[server:db_config|DB_CONFIG]] file and remove the comments (#'s) starting from the line **rep-set-priority 1** to make the machine a master server. Edit the TapeTrack\TapeTrack Framework Server\[[server:db_config|DB_CONFIG]] file and remove the comments (#'s) starting from the line **rep-set-priority 1** to make the machine a master server.
Line 55: Line 62:
 Delete all, and only, the files starting with ''_db.'' and ''db.rep.''.  This step is made easier if you sort the files in ascending order of file names to group them all together. Delete all, and only, the files starting with ''_db.'' and ''db.rep.''.  This step is made easier if you sort the files in ascending order of file names to group them all together.
  
-These files will be rebuilt when the server is restarted using the information of the new master and replicant details.+These files will be rebuilt when the server is restarted using the information of the new Master and Replicant details.
  
 |{{master_replicant_remove_db_files.gif}}| |{{master_replicant_remove_db_files.gif}}|
Line 64: Line 71:
 ===== Start The Servers ===== ===== Start The Servers =====
  
-[[server:start_stop|Start the master TapeTrack Server]].+[[server:start_stop|Start the Master TapeTrack Server]].
  
 |{{server_helper_start.gif}}| |{{server_helper_start.gif}}|
  
-Once the master server is running, [[server:start_stop|start the TapeTrack service]] on the remote machine.+Once the Master server is running, [[server:start_stop|start the Replicant TapeTrack service]].
  
-The replicant server will prepare the database for connection to the master server and move into ''Start Pending'' mode while waiting for the master server to respond.+The Replicant server will prepare the database for connection to the Master server and move into ''Start Pending'' mode while waiting for the Master server to respond.
  
 |{{start_pending.png}}| |{{start_pending.png}}|
  
-The master server will now connect to the replicant server and load the database information across the connection.  This may take time depending on the database size.+The Master server will now connect to the Replicant server and load the database information across the connection.  This may take time depending on the database size.
  
-Once the database is fully replicated the replicant server will now display running.+Once the database is fully replicated the Replicant server will now display running.
  
  
 ===== Confirming Functionality Of Primary And Replicant Servers ===== ===== Confirming Functionality Of Primary And Replicant Servers =====
  
-Open ''$DB_Msg.txt'' file (in the ''var/db'' directory) on both the primary and replicant server to ensure that replication is functional.+Open ''$DB_Msg.txt'' file (in the ''var/db'' directory) on both the primary and Replicant server to ensure that replication is functional.
  
-<note tip>Ensure that all firewall ports are open to allow the replication traffic to pass between the replicants.</note>+<note tip>Ensure that all firewall ports are open to allow the Replication traffic to pass between the Replicants.</note>
  
-Master $DB_Msg.txt file showing connection between master and replicant and the process of sending database information.+Master $DB_Msg.txt file showing connection between Master and Replicant and the process of sending database information.
  
 {{master_db_msg.png}} {{master_db_msg.png}}
  
-Replicant $DB_Msg.txt file showing connection between master and replicant, validation of connection and receiving database information.+Replicant $DB_Msg.txt file showing connection between Master and Replicant, validation of connection and receiving database information.
  
 {{replicant_db_msg.png}} {{replicant_db_msg.png}}
  
-Another way of testing the replication is correct and functioning is to [[desktop:adding_connection|create a connection]] to the replicant database through Tapemaster using the replicants IP address.  Remember to use the replicants connection port (usually 5000) and not the replication data port (5010).+Another way of testing the replication is correct and functioning is to [[desktop:adding_connection|create a connection]] to the Replicant database through TapeMaster using the Replicants IP address.  Remember to use the Replicants connection port (usually 5000) and not the replication data port (5010).
  
 {{login_replicant.png}} {{login_replicant.png}}
  
-As this database is a replication of the master server, all user-ID's from the master are functional in the replicant server for login purposes.+As this database is a replication of the Master server, all user-ID's from the Master are functional in the replicant server for login purposes.
  
-When you connect to the replicant database you will receive a popup reminding you the server is Read Only.  While you can view Customer, Media and Volume information, any attempted updates will be blocked by security protocols.+When you connect to the Replicant database you will receive a popup reminding you the server is Read Only.  While you can view Customer, Media and Volume information, any attempted updates will be blocked by security protocols.
  
 {{read_only_replicant.png}} {{read_only_replicant.png}}
Line 109: Line 116:
 ==== See Also ==== ==== See Also ====
  
-[[server:replicant_to_master|Restoring replicant server to master server status]]+[[server:replicant_to_master|Restoring Replicant server to Master server status]]
  
 <-   ^ server:advanced|Advanced Administration ^ server:port_change|Changing the default port  -> <-   ^ server:advanced|Advanced Administration ^ server:port_change|Changing the default port  ->
server/replication.1634686363.txt.gz · Last modified: 2025/01/21 22:07 (external edit)