Page Comparison

...

1. The customer has DataPower appliances deployed using either an Active/Passive or Active/Stand-by configuration. All DataPower appliances in any of these configurations have unique IP addresses.
2. DPOD node is installed once and is configured to monitor all DataPower appliances (active, standby and passive).  The secondary node will use the same disks on shared storage.
3. The customer has storage replication capabilities to replicate DPOD disks based on the disks’ replication policy described above.
4. All DPOD network services (NTP, SMTP, LDAP etc.) have the same IP addresses even after failover (otherwise a post configuration post configuration script is required to be run by the DR software).
5. The customer has a 3rd party software tool or scripts that can:

• • Identify unavailability of the primary DPOD node.
  • Launch a secondary  secondary DPOD node using a different IP address than the primary one (usually on a different physical hardware).

...

1. The customer has DataPower appliances deployed using either an Active/Passive or Active/Stand-by configuration. All DataPower appliances in any of these configurations have unique IP addresses.
2. Two DPOD nodes are installed (requires DPOD version 1.0.5 +), one operates as the Active node and the other one as Standby. After installing the secondary DPOD node, it must be configured to run in Standby state. See "makeStandby" API under DR REST API.
3. Both DPOD nodes should have the same environment name. The environment name is set by the customer during DPOD software deployment or during upgrade,  and and is visible at the top navigation bar (circled in red in the image below):
   
   
   
   
4. When the DPOD node is in DR Standby mode, a message is shown next to the environment name in the Web Console. A refresh (F5) may be required to reflect recent changes if the makeStandby API has just been executed, or when the DPOD status has changed from active to standby or vice versa. See the image below:
   
   
   
   
5. As both nodes are up, no configuration or data replication can exist in this scenario. The customer is expected to configure each DPOD node as a stendalone including all standalone including all system parameters, security groups / roles/ LDAP params parameters/ Certificates, custom reports and reports scheduling, custom alerts and alerts scheduling, maintance plan maintenance plan and user preferences. DPOD is not performing any configuration synchronization.
6. Especially, customer must add DataPower instances to each installation to monitor all DataPower Devices (active, standby and passive). Since DPOD v1.0.5 a new REST API may be utilized to add a new DataPower device to DPOD without using the UI (see Devices REST API).Customer must add DataPower instances to the standby DPOD node and set the agents for each device from the Device Management page in the web console (or by using the Devices REST API). Setting up the devices in the standby DPOD node will not make any changes to the monitored DataPower devices (no log targets, host aliases or configuration changes will be made).
7. All DPOD network services (NTP, SMTP, LDAP etc.) have the same IP addresses even after failover (otherwise a post configuration script is required to be run by the DR software).
8. The customer has a 3rd party software tool or scripts that can:
   
   • Identify unavailability of the primary DPOD node.
   • change the state of the secondary node (that is in standby state) to Active state  .
9. The standby DPOD node can still be online as disk replication is not required.
10. This scenatio scenario will not provide data High AvailabiltyAvailability. To load data from Primary node customer is required to restore backups taken from primary nodes.
11. During state transition of the Secondary from Active to Standby there might be some data loss.

...

• Although the secondary DPOD node has a different IP address, all the DataPower appliances will still be able to access it since their internal host aliases pointing to DPOD will be replaced (step 2 above).
• As all DataPower appliances retain the same IP addresses - DPOD can continue to sample them.

• Although the secondary  secondary DPOD node has a different IP, all users can access DPOD’s web console because its DNS name has been changed or it is behind an NLB (step 3 above).

  
  

  Note
  All Data from the originally Active DPOD will not be available!

  
  

...

1. The customer has DataPower appliances deployed using either an Active/Passive , Active/Active or Active/Stand-by configuration. All DataPower appliances in any of these configurations have unique IP addresses.
2. Two DPOD nodes are installed (both are v1.0.5+), both running in Active state. 
3. Both DPOD nodes must have different environment name. The environment name is set by the customer during DPOD software deployment, and is visible at the top navigation bar (circled in red in the image below):
4. Both DPOD nodes are configured separately to monitor all DataPower Devices (active, standby and passive). Since DPOD v1.0.5 a new REST API may be utilized to add a new DataPower device to DPOD without using the UI (see Devices REST API). As both nodes are up, no configuration replication can exist in this scenario.
5. As both nodes are up, no configuration or data replication can exist in this scenario. The customer is expected to configure each DPOD node as a stendalone including all a standalone including all system parameters, security groups / roles/ LDAP params parameters/ Certificates, custom reports and reports scheduling, custom alerts and alerts schedulingand alerts scheduling, maintance plan  maintenance plan and user preferences. DPOD is not performing any configuration synchronization.
6. Especially, customer must add DataPower instances to each installation to monitor all DataPower Devices (active, standby and passive). Since DPOD v1.0.5 a new REST API may be utilized to add a new DataPower device to DPOD without using the UI (see Devices REST API).Customer must add DataPower instances to the standby DPOD node and DPOD node and set the agents for each device from the Device Management page in the web console (or by using the Devices REST API). Setting up the devices in the standby DPOD node DPOD node will not make any changes to the monitored DataPower devices (no log targets, host aliases or configuration changes will be made).
7. All DPOD network services (NTP, SMTP, LDAP etc.) have the same IP addresses even after failover (otherwise a post configuration script is required to be run by the DR software).
8. The customer added DataPower devices to the standby DPOD node and set the agents for each device from the Device Management page in the web console (or by using the Devices REST API). Setting up the devices in the standby DPOD node will not make any changes to the monitored DataPower devices (no log targets, host aliases or configuration changes will be made). Customer is expected to replicate all configurations and definitions for each installation. DPOD is not replication neither data nor configurations/definitions.
9. All DPOD network services (NTP, SMTP, LDAP etc.) have the different IP addresses .
10. Since the two installations are completely independant and no data is replicated this may lead to data inconsistency as once Customer is expected to replicate all configurations and definitions for each installation. DPOD is not replication neither data nor configurations/definitions.
11. Importanat ! - Since the two installations are completely independant and no data is replicated this may lead to data inconsistency as once may capture information while the other is shut down in Down state for maintenance .or even started in different time. This might have effect on reports and alerts.
12. Importanat ! - Each DPOD installation will create for each domain 2 log targets. If one DataPower is connected to 2 DPODs than for each domain you will need 4 log targets . As DataPower have a limitation of ~1000 log targets starting FW 7.6 than customer must be aware notreach limitation of log targets
13. All logs and information will be sent twice over network thus network bandwith will be doubled !
    
    

During a disaster:

1. The customer's DR software should Identify a failure in DPOD primary node (e.g. by pinging access IP, sampling user interface URL or both).No action is required . DataPower instance will push data to both instances

DPOD will be available in the following way:

• Although the passive DPOD node has a different IP address, all the DataPower appliances will still be able to access it since their internal host aliases pointing to DPOD will be replaced (step 2 above).
• As all DataPower appliances retain the same IP addresses - DPOD can continue to sample them.
• Although the passive DPOD node has a different IP, all users can access DPOD’s The active node will continue to operate as it was operating before.
• All users can access DPOD’s web console because its DNS name has been changed or it is behind an NLB (step 3 above)as it was accesiable before the disaster.
• Note - All  Some Data from the originally Active DPOD will not be available! available 

 In a "Return to Normal" scenario:

1. Right after re-launching the primary node, call the "standbyToInactive" API (see DR REST API) to disable the standby node.
2. Call the "activeBackToActive" API (see DR REST API) to re-enable the primary node - this will point DPOD's log targets and host aliases on the monitored devices back to the primary DPOD node.
3. The customer's DR software should change the DNS name for the DPOD node's web console to reference an actual IP address or use an NLB in front of both DPOD web consoles.No action is required . DataPower instance will push data to both instance
4. The data gathered while the disaster period can not be sync back to the recovered node 
   
   

Backups

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

...