Page Comparison

...

1. Customer have DataPower appliances in Active/Passive or Active/Standby. All DataPower appliances in any configuration must have unique IP address
After
2. . 
3. Install two DPODs, one as the active machine and one as the standby machine, after installing the DPOD that is supposed to be standby device, run the makeStandby DR REST API to designate it as such.
4. When the DPOD will be installed, maintained and configured twice. DPOD will be configured installation is in DR Standby mode, a message will appear next to the environment name (press F5 to reflect recent changes if you just run the makeStandby API or changed DPOD from active to standby or vice versa)
   
   Image Added
   
   
5. Both DPODs will need to be configured separately to monitor all DataPower Devices (active, standby and passive) - in v1.0.6.0 5 a new API was exposed to add a new DataPower to DPOD and it can be consumed from a script
   Since both servers are up no replication can exist.
6. The Specfiically, the customer will need to add devices to the standby DPOD and set the agents for each device from the Device Management page in the web console or using the Device REST API, setting up the devices in the standby DPOD will not make any changes on to the monitored DataPower devices (no log targets, host aliases or configuration changes will be made)
   When the DPOD installation is in DR Standby mode, a message will appear next to the environment name (press F5 to reflect recent changes if you just changed DPOD from active to standby or vice versa)
   Image Removed
   
7. All DPOD network services (NTP, SMTP, LDAP ..) must have the same IP address (otherwise a post configuration script is required to be run by the DR software)
8. Customer is required to have a 3rd party software tool or scripts that can provide:

• • Identify unavailability of primary DPOD server/s.
  • Launch the passive DPOD servers with differentIP address

68. The standby DPOD server can still be online since NO disks are required to be replicated.

79. It is acceptable for a customer to have its standby DPOD activated without any of data collected by the active DPOD since no replication occurs.

...

 In a "Return to Normal" scenario:

1. Right after re-launching the Active installation, run a REST API called standbyToInactive (see DR REST API reference) to disable the StandBy installation  
2. Call a REST API to re-enable the Active installation - activeBackToActive (see DR REST API reference) - this REST API will point DPOD's log targets and host aliases on the monitored devices back to the active DPOD machine
3. Customer's DR Software must change DNS name for DPOD server web console to reference to actual IP or use an NLB in front of both DPOD web console.

...

 To improve product recovery administrator should perform regular backups as described in the backup section