Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
Cisco Prime Network Registrar IPAM 8.1.1 Disaster Recovery Guide - Using MySQL Replication
13
from the DR Executive to the Production Executive.
Then, on the Production Executive, run the
prepslave.sh script provided in the
$INCHOME/etc/support directory using the
parameters generated when the prepmaster.sh script
was executed on the DR Executive in the previous
step. This will load the database dump file and make
the appropriate MySQL changes to create a Passive
Master. In addition, it will generate the correct
command line options for the connect_to_passive.sh
script to be run on the DR Executive.
3.1.3.4 Complete the connection between Executive databases
Since the Active Master is currently running on the DR
Executive, it must be informed about the Passive
Master settings used on the Production Executive.
This is accomplished by running the
connect_to_passive.sh script located in the
$INCHOME/etc/support directory using the
parameters generated by the prepslave.sh script run on
the Production Executive.
3.1.3.5 Demote the database on the DR Executive
Now that the Active-Passive Master configuration is setup,
it is now a simple matter to reverse their roles. Simply
run the demote_master.sh script located in the
$INCHOME/etc/support directory on the DR
Executive. Later you will run the promote_master.sh
script on the Production Executive using the
parameters generated by this script.
> $INCHOME/etc/support/demote_master.sh
3.1.3.6 Stop Cisco Prime Network Registrar IPAM Services on DR Executive
3.1.3.6.1 Linux/Solaris
Run the Cisco Prime Network Registrar IPAM script to stop
all services on the DR Executive:
> $INCHOME/etc/incontrol stop
> $INCHOME/etc/incontrol stop
3.1.3.7 Demote the DR Executive to standby status
Revert the DR Executive to standby by running the
“demote” script which will configure the system to
start only MySQL.