Cisco Cisco Prime Network Registrar 8.3 故障排查指南
Cisco Prime Network Registrar IPAM 8.3 Disaster Recovery Guide
7
3 DR Configuration Options
This section details the options for Disaster Recovery (DR) of IPAM Executive
services.
There are three configurations of the Production and DR Executives that can
support a DR scenario:
services.
There are three configurations of the Production and DR Executives that can
support a DR scenario:
1. DR Executive assumes the IP of Production Executive
2. Production and DR Executive use different IPs
3. Production and DR Executives share a SAN/NAS or mirrored database and
2. Production and DR Executive use different IPs
3. Production and DR Executives share a SAN/NAS or mirrored database and
share a virtual IP
3.1 DR Executive assumes the IP of the Production Executive
All
Services
Running
MySQL
Running
Production
Executive
DR Executive
DBMover Script
1.1.1.1
2.2.2.2
Figure 1. Server configuration prior to DR Event
As shown in Figure 1, the Production Executive database will be backed up on a
regular basis onto the DR Executive using the DBMover script. Only the
MySQL database service is running on the DR Executive. When the Production
regular basis onto the DR Executive using the DBMover script. Only the
MySQL database service is running on the DR Executive. When the Production
Exec fails, the DR Exec assumes the Production Executive’s IP address and
starts all services using a script as shown in Figure 2.
starts all services using a script as shown in Figure 2.
Note: For this scenario
to succeed a VLAN needs to be in place or the DR Executive needs to be
on the same subnet.
All deployed agents will continue to point to the same IP
address as before so no agent-side changes are required.