Checking the Status of the Disaster Recovery Configuration
You check the status of the disaster recovery configuration:
After starting the disaster recovery process to ensure that the disaster recovery configuration is accurate, files are being replicated, and the disaster recovery watchdog is monitoring the disaster recovery setup
After stopping the disaster recovery process, to ensure that file replication and disaster recovery watchdog process have stopped
You execute the jmp-dr health
command to check the
status of the disaster recovery configuration. This command checks
the status of asynchronous data replication, file transfer, and disaster
recovery watchdog, and the role of clusters in the disaster recovery
setup. Errors found during command execution are listed in the command
output.
If you have already executed the jmp-dr health
command and the execution is in progress, executing another jmp-dr health
command can display incorrect output. The output
from the jmp-dr health
command also lists whether another
instance of the command is being executed.
To check the status of the disaster recovery configuration at a site:
- Log in to the CLI of the Junos Space node at the site
on which the VIP or the eth0:0 interface is configured.
The Junos Space Settings Menu is displayed.
- Enter 6 (if you are using a
hardware appliance) or 7 (if you are using
a virtual appliance) at the Junos Space Settings Menu prompt to run
shell commands.
The following is a sample output from a virtual appliance:
admin@10.206.41.183's password: Last login: Mon Aug 17 06:17:58 2015 from 10.206.41.42 Welcome to the Junos Space network settings utility. Initializing, please wait Junos Space Settings Menu 1> Change Password 2> Change Network Settings 3> Change Time Options 4> Retrieve Logs 5> Security 6> Expand VM Drive Size 7> (Debug) run shell A> Apply changes Q> Quit R> Redraw Menu Choice [1-7,AQR]: 7
You are prompted to enter the administrator password.
- Enter the administrator password.
- Enter
jmp-dr health
at the shell prompt.Junos Space Platform checks the status (overall health) of the disaster recovery configuration at the site.
The following is a sample output of the
jmp-dr health
command after you start the disaster recovery process and execute the command at the active site:[user1@host]# jmp-dr health The DR role of this site: active The DR state of this site: started The status of DR watchdog: ready The status of DR remote site: up Check admin password of DR remote site [ OK ] Check mysql ca and server certificates [ OK ] Check mysql replication users [ OK ] Check file replication: backup cron job should be added [ OK ] Check mysql replication: node (10.206.41.221, user1@host) and peer node of same site (10.206.41.222, user2@host) should be master-master [ OK ] Check pgsql replication: Pgsql replication betwwen this node (10.206.41.221, user1@host) and peer node of same site (10.206.41.222, user2@host) should be master-slave. [ OK ] Services (jboss, jboss-dc, etc.) should be up [ OK ] DR watchdog should be up [ OK ] Command completed.
The following is a sample output of the
jmp-dr health
command after you start the disaster recovery process and execute the command at the standby site:[user3@host]# jmp-dr health The DR role of this site: standby The DR state of this site: started The status of DR watchdog: ready The status of DR remote site: up Check admin password of DR remote site [ OK ] Check mysql ca and server certificates [ OK ] Check mysql replication users [ OK ] Check file replication: poll cron job should be added [ OK ] Check mysql replication: node (10.206.41.226, user3@host) and peer node of same site (10.206.41.227, user4@host) should be master-slave, and node (10.206.41.226, user3@host) and mysql VIP node of remote site (10.206.41.220) should be slave-master [ OK ] Check pgsql replication: Pgsql replication between node (10.206.41.226, user3@host) and peer node of same site (10.206.41.227, user4@host) should be master-slave, and replication node (10.206.41.226, user3@host) and pgsql VIP node of remote site (10.206.41.220) should be slave-master [ OK ] Services (jboss, jboss-dc, etc.) should be down [ OK ] DR watchdog should be up [-] [ OK ] Command completed.
The following is a sample output of the
jmp-dr health
command after you stop the disaster recovery process and execute the command at the active site:[user2@host]# jmp-dr health The DR role of this site: active The DR state of this site: stopped The status of DR watchdog: ready The status of DR remote site: up Check admin password of DR remote site [ OK ] Check mysql ca and server certificates [ OK ] Check mysql replication users [ OK ] Check file replication: cron jobs should be removed [ OK ] Check mysql replication: node (10.206.41.222, user2@host) and peer node of same site (10.206.41.221, user1@host) should be master-master [ OK ] Services (jboss, jboss-dc, etc.) should be up [ OK ] DR watchdog should be down [ OK ] Command completed.
The following is a sample output of the
jmp-dr health
command after you stop the disaster recovery process and execute the command at the standby site:[user3@host]# jmp-dr health The DR role of this site: standby The DR state of this site: stopped The status of DR watchdog: ready The status of DR remote site: up Check admin password of DR remote site [ OK ] Check mysql ca and server certificates [ OK ] Check mysql replication users [ OK ] Check file replication: cron jobs should be removed [ OK ] Check mysql replication: node (10.206.41.226, user3@host) and peer node of same site (10.206.41.227, user4@host) should be master-master [ OK ] Services (jboss, jboss-dc, etc.) should be down [ OK ] DR watchdog should be down [ OK ] Command completed.