Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
Cisco Prime Network Registrar IPAM 8.1.1 Disaster Recovery Guide - Using MySQL Replication
17
are located in $INCHOME/etc. When copied to the
DR Executive, they must be named
default.incontrol.primary and incstatus.primary,
respectively, and located in $INCHOME/etc.
3.2.2 Disaster Recovery Procedure
This section describes the procedure necessary to initiate a DR
event or exercise under this scenario.
3.2.2.1 Demote the Production Executive database, if possible
If this is a planned DR exercise where the Production
Executive will eventually resume its role as the Active
Master database, then demoting the Production
Executive database at the start is preferable. To do
this, execute the demote_master.sh script located in the
$INCHOME/etc/support directory on the Production
Executive:
> $INCHOME/etc/support/demote_master.sh
This script will ensure that no unintended writes will occur
on the Production Executive database and will help
with a smooth transition back to “normal” operation.
In addition it will generate the appropriate parameters
to call the promote_master.sh script on the DR
Executive.
3.2.2.2 Promote the database on the DR Executive to Active Master
At this point, we will assume that either the Production
Executive is down, or that the Production Executive
database has been demoted to a Passive Master.
Therefore, we need to promote the database on the DR
Executive to an Active Master. The process varies
slightly dependent upon if the Production Executive
was demoted. If it was demoted we will use the
parameters generated from the demote_master.sh
script. If not, we will call the promote_master.sh script
with the ‘-c’ parameter.
If Production Executive database was demoted:
> $INCHOME/etc/support/promote_master.sh –l
<logfile> -s <logfile position>
<logfile> -s <logfile position>