...
- The customer's DR software should Identify a failure in DPOD failure primary server (e.g. by pinging access IP, User Interface sampling user interface URL or both).
- The customer's DR Software software should launch the passive DPOD server and change its using a different IP address than the failed primary server (or change the IP address ( if not already configured ) to be a different address to the one used by the failed active DPODthat way).
- The customer's DR Software software should execute a commandscommand/script to change DPOD's IP address as described in documentation.
- The customer's DR Software must software should change the DNS name for the DPOD server's web console to reference an actual IP address or use an NLB in front of both DPOD web consoleconsoles.
- DPOD creates 2 aliases in each configured DataPower. The customer's DR Software should run a script with a SOMA request to change the aliases to DPOD current IP address and enable and disable all DPOD log targets .(Please refer to the Devices REST API for API named - Setup software should disable all DPOD log targets, update DPOD host aliases and re-enable all log targets in all DataPower devices. This is done by invoking a REST API to DPOD. See Devices REST API, under "Setup all devices' host aliases - For DR for DR").
DPOD will be available in the following way:
- Although the passive DPOD has a different IP address, all the DataPower appliances will still be able to access it since their internal host alias aliases pointing to DPOD will be replaced . (Step step 5 above).
- As all DataPower appliances retain the same IP addresses - 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 . (Step or is behind an NLB (step 4 above).
Scenario C- Active/Standby – 2 DPOD separated installation.
...