TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


troubleshooting: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
troubleshooting:replication [2018/07/31 23:51] Scott Cunliffetroubleshooting:replication [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Troubleshooter: Replication ====== ====== Troubleshooter: Replication ======
  
---> Replication previously set up and running +The purpose of this troubleshooter is to diagnose why Replication is not being performed. 
-Is the master server running + 
---> Yes +The symptom of Replication not working is [[object:volume|Volume]] movements executed in the Main database are not being Replicated in the Replication database. 
-Is the replicant server running + 
---> Yes +To begin diagnosing the problem select from the following options: 
-Are the ports used by the master and replicant open and listening + 
---> Yes +  * [[troubleshooting:replication:setup_yes|Replication previously set up and running]] 
-<-- +  * [[troubleshooting:replication:setup_no|Replication not previously set up]] 
---> No + 
-Have your network staff open the required ports for inbound and outbound communications + 
-<-- +
---> Not sure +
---> Checking master to replicant port access +
-<-- +
---> Checking replicant to master port access +
-<note tip>The following commands are using default install values.  If these values do not match our installation you will need to replace with the correct database location and required ports</note> +
-Stop the replicant server+
-Open config file, comment out replicant section and save file +
-restart server in foreground mode, using the command in an administrative command line window +
-<sxh> +
-TMSS10Server -f -h "%TMSS10DB%" -p 5010 +
-</sxh> +
-Open another administrative command line window and execute the command +
-<sxh> +
-netstat -na  find "5010" +
-</sxh> +
-to check that the port is actively listening.  If it is you will receive output similar to +
-<sxh> +
-netstat -na  | find "5010" +
- TCP    0.0.0.0:5010           0.0.0.0:             LISTENING +
-</sxh>+
  
-From the master server run the command TMSS10Ping with the replicant server address and port. 
---> Connection successful 
-<-- 
---> Connection unsuccessful 
-Have your network staff open the port 
-<-- 
-<-- 
-<-- 
-<-- 
---> No 
-Restart the replicant server using the Framework Server Helper, administrative command line or windows services 
-<-- 
-<-- 
---> No 
-<-- 
---> Not sure 
-From an administrative command line window on the master server run the command TMSS10Ping       
---> Connection Successful 
-From an administrative command line window on the replicant server run the command TMSS10Ping  
---> Connection Successful 
-<-- 
---> Connection Unsuccessful 
-<-- 
-<-- 
---> Connection Unsuccessful 
-Restart the master server using the Framework Server Helper, administrative command line or windows services 
-<-- 
-<-- 
-<-- 
---> Replication not previously set up 
-Replication setup attempted 
---> Yes 
-<-- 
---> No 
-Follow instructions for [[server:replication|server replication]] 
-<-- 
-<-- 
  
  
troubleshooting/replication.1533081102.txt.gz · Last modified: 2025/01/21 22:07 (external edit)