TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


server:replication

This is an old revision of the document!


Enabling Replication

To enable TapeTrack High Availability Replication:

Steps On Remote Server

Install the TapeTrack Framework Server software on your remote machine.

Stop the service on the remote machine.

Delete all database files on the remote 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) from the line rep-set-priority 0 to make the machine a Replicant.

Edit the replication local (replicant) and remote (master) host names in the DB_CONFIG file.

  • Replace replicant-1.tapetrack.com 5010 with the domain name (or IP address) of your replicant server.
  • Replace master.tapetrack.com 5010 with the domain name (or IP address) of your master server.

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 primary TapeTrack server.

Edit the DB_CONFIG file to define the local and remote server.

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

Start the primary 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.1529291189.txt.gz · Last modified: 2025/01/21 22:07 (external edit)