Monitoring Cross-site Replication

To monitor the status of cross-site replication, on your primary site run the following as-admin commands:
  • show local site to monitor the number of operations waiting to be sent to the DR site.
  • show sites or show remote site to monitor the status of the connection to the DR site.
The number of operations waiting to be sent to the DR site should be kept to a minimum. If the number of operations reported in the Pending Route Actions field of the show local site command seems unusually high or starts to grow, check to ensure the DR site is still online by running the show sites command.
Caution: It is important to make sure that the size of the internal space used for cross-site replication does not grow large enough that you run out of memory on your system. Be sure to have a strategy in place for the scenario where your DR site is down for an extended period and you have to disable cross-site replication during that period. Your strategy should include how to ensure that your data is synchronized between your primary and DR sites before bringing the DR site back online.
If the DR site is not online or if too many network errors occur when communicating with the DR site, the site is automatically placed in the offline state. Unless you have manually suspended the DR site, ActiveSpaces automatically detects when the DR site comes back online and continues replicating operations.
Important: Pending operations held in the internal space are not persisted. If the primary site goes down, any pending operations waiting to be sent to the DR site will be lost.