Table of Contents
Enabling Replication
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 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
Install the TapeTrack Framework Server software on your Replicant machine.
Stop the service on the Replicant machine.
 |
Navigate Windows File Explorer to the TapeTrack Framework Server installation directory (TapeTrack\TapeTrack Framework Server) to the var\db folder.
Delete all database files on the Replicant machine (all files in the TapeTrack\TapeTrack Framework Server\var\db directory) EXCEPT the DB_CONFIG file).
 |
Open the DB_CONFIG file in Notepad, or equivalent text editor.
Edit the TapeTrack\TapeTrack Framework Server\DB_CONFIG file to 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 (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.
Steps On Master Server
Stop the TapeTrack service on the Master TapeTrack server.
Edit the TapeTrack\TapeTrack Framework Server\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 (your_replicant_IP_address used as Replicant IP example).
- Replace master.tapetrack.com with the domain name (or IP address) of your Master Server (your_master_IP_address used as Master IP example).
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.
 |
Start The Servers
Start the Master TapeTrack Server.
 |
Once the Master server is running, 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 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.
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.
Master $DB_Msg.txt file showing connection between Master and Replicant and the process of sending database information.
Replicant $DB_Msg.txt file showing connection between Master and Replicant, validation of connection and receiving database information.
Another way of testing the replication is correct and functioning is to 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).
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.
