Backup Status Monitoring

If you are running a backup server to be used in the event of a primary failure, the status of the replication (backup) process can be monitored by DMan and reported in the Agent Status widget in Flow to provide a more convenient location to see current replication status. Backups are often affected by latent network and the Agent Status will indicate if the backup process is getting too far behind due to network latency or complete disconnect. The Agent Status will move to the warning (red) if backup replication gets 5 minutes behind the primary or if replication fails completely.

Utility Status

The Backup Status Monitor requests the status from the backup server every minute. A variety of statuses can come back from the server and DMan will help qualify if a problem is forming with your replication.

When replication is not properly backing up your main server or the backup gets more than 5 minutes behind the primary in processing data, the Agent Status of the Replication Monitor will be a warning (red)

Configurable Preferences

The status of the backup server cannot be obtained from the main server, so backup server credentials need to be provided to DMan through the Preferences Tab in the System Configuration module in Flow.

By default these keys have no data associated with them. When these values are blank, DMan assumes you do not have a backup server running and this module will not be scheduled to run.

System > Replication Slave Location

The location of your backup server. Provide either an IP or a resolvable machine name. By default this value is blank to indicate no backup system present.

1147pxSystem > Replication Slave User

The user account associated with the replication account on the backup server. By default this value is blank to indicate no backup system present. A typical user name is blbackup.

System > Replication Slave Password

The password used for the user account on the backup server. By default this value is blank to indicate no backup system present.