When the primary server is started it attempts to communicate with the secondary. It continues to attempt communication until it connects to the secondary and can begin replicating the database.
When you make a change in the database of the primary, the database replication process makes the same change in the database of the secondary.
Navigate to the /bsc/campusMgr/bin/ directory on the Secondary. Run the following script:
You should receive a response that is similar to the following:
Host Host Name
SQL version 5.0.18,
slave is inactive
If the response contains the line slave is inactive, database replication is not active. If the response contains the line slave is active, database replication is active.
If for any reason the database is not replicated correctly on the secondary before failover, the recovery process gives you the option of retaining the older database located on the primary.