...
- Customer have DataPower appliances in Active/Passive or Active/Standby. All DataPower appliances in any configuration must have unique IP address
- DPOD will be installed, maintained and configured twice (in v1.0.5 a new API was exposed to add a new DataPower to DPOD and it can be consumed from a script.). DPOD will be configured to monitor all DataPower (active, standby and passive).
Since both servers are up no replication can exist. - 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 RES API, setting up the devices in the standby DPOD will not change anything on the monitored devices (no log targets, host aliases or configuration changes will be made)
- 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)
- Customer is required to have a 3rd party software tool or scripts that can provide:
...
6. The standby DPOD server can still can be up online since NO disks are required to be replicated.
7. 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.8. When the Standby installation of DPOD should become in non-active stated again customer will need to run scripts on both the Active installation and the StandBy installation - see "Return To Normal Scenario".
In a disaster scenario:
- Customer's DR software should Identify DPOD failure (for example by ping to IP, access UI URL, or both)DPOD create 2 aliases in each configured DataPower. Customer
- The customer's DR Software should run a script with SOMA request to change this aliases to DPOD current IP address and enable and disable all DPOD log targets (Please refer to Devices REST API for an API named - Enable Standby installation -For DR)enable the standBy installation by calling a REST API called standbyToActive (see DR REST API reference) - this REST API will point DPOD's log targets and host aliases on the monitored devices to the standby machine.
- 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.
...
- Although the passive DPOD has a different IP, all the DataPower appliances’ will be able to access it since their internal host alias point points to DPOD will be replaced (by the REST API called in step 2)
- Since all DataPower appliances will have the same IPs than - DPOD can continue to sample them.
- Although the passive DPOD has a different IP, all users can access DPOD’s web console because its DNS name has been changed by step 3
- Note - All Data exists in from the Active DPOD will not be lost available !
In a "Return to Normal" scenario:
- Right after launching the Active installation it is crucial run an API , run a REST API called standbyToInactive (see DR REST API reference) to disable the DPOD background processing in the StandBy installation (Please refer to Devices REST API for an API named - Disable Standby installation -For DR).. DPOD create 2 aliases in each configured DataPower. Customer DR Software should run a script with SOMA request to change this aliases to DPOD current IP address and enable and disable all DPOD log targets. (Please refer to Devices REST API for an API named - Resume Active installation -For DR)..
- 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
- 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.
...