Versions Compared

Version Old Version 5 New Version 6
Changes made by

Hanan Kenan

Hanan Kenan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Customer DR software should Identify DPOD failure (for example by ping to IP access UI URL or both)
  2. Customer DR Software should launch the passive DPOD server and change its IP address (if not already configured) to be the different address from the failed active DPOD.
  3. Customer DR Software should run commands/script to change DPOD IP address as described in documentation.
  4. Customer 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.
  5. 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 .(Will be provided in v1.0.5.0Please refer to Devices REST API for API named - Setup all devices' host aliases -For DR )

DPOD will be available in the following way:

...

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:

  1. Customer's DR software should Identify DPOD failure (for example by ping to IP access UI URL or both)
  2. 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 (Will be provided in v1.0.5.0Please refer to Devices REST API for an API named - Enable Standby installation -For DR).
  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.

...

  • Although the passive DPOD has a different IP, all the DataPower appliances’ will be able to access it since their internal host alias point to DPOD will be replaced (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 Active DPOD will be lost  !

 

 In a "Return to Normal" scenario:

  1. Right after launching the Active installation it is crucial run an API 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).. 
  2. 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).. 
  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.

Backups

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

...