TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • tmss10listconsignments • adding_connection_config • server_argument • barcode • tmsskerberos • tmss10listusage • report_examples • volume_properties_window • config_file • replication
server:replication
 
 Volume-ID Building →

This is an old revision of the document!

 
Cookbook  
 Volume-ID Building →

Table of Contents

 
 Changing the default port →

Enabling Replication

The following information illustrates the steps required to enable a High Availability Replicant Server.

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 Replican Server.

IP addresses included in the instructions are for demonstration only, these must be replaced with your correct values.

Steps On Remote Server

Install the TapeTrack Framework Server software on your Replicant machine.

Stop the service on the Replicant machine.

Delete all database files on the Replicant machine (all files in the var/db directory) EXCEPT the DB_CONFIG file).

DO NOT delete the DB_CONFIG file.

Edit the DB_CONFIG file and remove the comments (#'s) starting from the line rep-set-priority 0 to make the machine a Replicant.

Edit the Replicant Server and Master Server host names in the DB_CONFIG file.

  • Replace replicant-1.tapetrack.com with the IP address of your Replicant Server (RRR.RRR.RRR.RRR used as Replicant IP example).
  • Replace master.tapetrack.com with the IP address of your Master Server (MMM.MMM.MMM.MMM used as Master IP example).
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.

Ensure that the replication TCP/IP ports specified in the DB_CONFIG file are open for inbound connections.

Start the TapeTrack service on the remote machine.

Steps On Master Server

Stop the TapeTrack service on the master TapeTrack server.

Do Not delete any files on the master server

Edit the 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 DB_CONFIG file to define the local and remote server. Edit the Replicant Server and Master Server host names in the DB_CONFIG file.

  • Replace replicant-1.tapetrack.com with the domain name (or IP address) of your Replicant Server (RRR.RRR.RRR.RRR used as Replicant IP example).
  • Replace master.tapetrack.com with the domain name (or IP address) of your Master Server (MMM.MMM.MMM.MMM used as Master IP example).

Ensure that the replication TCP/IP ports are open for inbound/outbound connections.

Start the master TapeTrack Server.

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.

Ensure that all firewall ports are open to allow the replication traffic to pass between the replicants.
The replication communications are not encrypted so if replication is enabled you should ensure that all machines that are replicated are in a trusted network or connected via a secure VPN connection.

Server replication troubleshooting

See Also

Restoring replicant server to master server status

 
Advanced Administration  
 Changing the default port →
server/replication.1615413096.txt.gz · Last modified: 2025/01/21 22:07 (external edit)