Versions Compared

Version Old Version 27 New Version 28
Changes made by

Hanan Kenan

Hanan Kenan

Saved on

Key

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

...

3rd party DR software - a software tool that assist in identify the the primary node state has changed from active to inactive and initiate the process of launching the secondary node as an active node .



DPOD Scalability vs. HA/DR

...

  1. The customer has DataPower appliances deployed using either an Active/Passive, Active/Standby or Active/Active configuration. All DataPower appliances in any of these configurations have unique IP addresses.
  2. The customer has storage replication capabilities to replicate DPOD disks based on the disks’ replication policy described above.
  3. Primary 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).
  4. 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).The customer has storage replication capabilities to replicate DPOD disks based on the disks’ replication policy described above.
  5. The customer has a 3rd party software tool or scripts that can:
    • Identify unavailability of the primary DPOD server node.
    • Launch a secondary DPOD node using the same IP address as the primary one (usually on a different physical hardware).

6. The secondary DPOD node is not running when business is as usual, since disks replication is required and it has the same IP address as the primary DPOD node.

During a disaster:

7. This scenario might not be suitable for high load implementation as replication of DPOD data disk might not be acceptable.

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).
  2. The customer's DR software should launch the secondary DPOD node using the same IP address as the failed primary server node (or change the IP address if not already configured that way).

DPOD will be available in the following way:

  • As the secondary DPOD server node has the same IP, all DataPower appliances will be able to access it.
  • Since all DataPower appliances will have the same IP addresses - DPOD can continue to sample them.
  • Since the secondary DPOD server node has the same IP address as the primary one, access to DPOD console will be with the same URL.

Scenario B: Active/Passive – DPOD's IP Address changes - Shared Storage

Assumptions:

  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).  All DPOD network services (NTP, SMTP, LDAP etc.) have the same  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 script is required to be run by the DR software).The customer has storage replication capabilities to replicate DPOD disks based on the disks’ replication policy described above.
  5. The customer has a 3rd party software tool or scripts that can:

...

6. The secondary DPOD node is not running when business is as usual, since disks replication is required.

7. This scenario might not be suitable for high load implementation as replication of DPOD data disk might not be acceptable.

During a disaster:

  1. The customer's DR software should Identify a failure in DPOD primary server node (e.g. by pinging access IP, sampling user interface URL or both).
  2. The customer's DR software should launch the secondary DPOD server node using a different IP address than the failed primary server node (or change the IP address if not already configured that way).
  3. The customer's DR software should execute a command/script to change DPOD's IP address.
  4. The customer's DR software should change the DNS name for the DPOD servernode's web console to reference an actual IP address or use an NLB in front of both DPOD web consoles.
  5. The customer's DR 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 "refreshAgents" API under Devices REST API.

...

  • 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 5 above).
  • As all DataPower appliances retain the same IP addresses - the secondary DPOD server node that was just became active can continue to sample them.
  • Although the 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 4 above).

Scenario C: Active/Standby – 2 DPOD separate installations - no shared storage

Assumptions:

  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 servers nodes are installed (requires DPOD version 1.0.5 +), one operates as the active Active node and the other one as standby nodeStandby. After  After installing the standby secondary DPOD node, it must be configured as a standby nodeto run in Standby state. See "makeStandby" API under DR REST API.
  3. Both DPOD servers nodes should have the same environment name. The environment name is set by the customer during DPOD software deployment or during upgrade,  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 to monitor all DataPower Devices (active, standby and passive). Since DPOD as a stendalone including all system parameters, security groups / roles/ LDAP params / Certificates, custom reports and reports scheduling, custom alerts and alerts scheduling, maintance 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). As both servers are up, no configuration or data replication can exist in this scenario. Especially, customer must add DataPower instances to Customer must add DataPower instances to the standby DPOD server 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 server 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 server node can still be online as disk replication is not required.

During a disaster:

  1. The customer's DR This scenatio will not provide data High Availabilty. To load data from Primary node customer is required to restore backups taken from primary nodes.
  2. During state transition of the Secondary from Active to Standby there might be some data loss.

During a disaster:

  1. The customer's DR software should Identify a failure in DPOD primary server node (e.g. by pinging access IP, sampling user interface URL or both).
  2. The customer's DR software should enable the standby DPOD server node by calling the "standbyToActive" API (see DR REST API). This API will point DPOD's log targets and host aliases of the monitored devices to the standby server node and enable most timers based services (Reports,Alerts ...) on secondary serversnodes.
  3. The customer's DR software should change the DNS name for the DPOD servernode's web console to reference an actual IP address or use an NLB in front of both DPOD web consoles.

DPOD will be available in the following way:

  • Although the standby secondary DPOD server 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  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 -


    Note

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


 In a "Return to Normal" scenario:

  1. Right after re-launching the primary servernode, call the "standbyToInactive" API (see DR REST API) to disable the standby servernode.
  2. Call the "activeBackToActive" API (see DR REST API) to re-enable the primary server node - this will point DPOD's log targets and host aliases on the monitored devices back to the primary DPOD servernode.
  3. The customer's DR software should change the DNS name for the DPOD servernode's web console to reference an actual IP address or use an NLB in front of both DPOD web consoles.
  4. During state transition of the Primary from Active to Standby there might be some data loss.

Scenario D: Limited Active/Active – 2 DPOD separate installations - no shared storage

Assumptions:

  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 servers nodes are installed (both are v1.0.5.0+), both operate as the activerunning in Active state. 
  3. Both DPOD servers should nodes must have the 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):Image Removed
  4. Both DPOD servers nodes are configured separately to monitor all DataPower Devices (active, standby and passive). Since DPOD v1.0.5.0 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 servers are up, no configuration replication can exist in this scenarionew 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 system parameters, security groups / roles/ LDAP params / Certificates, custom reports and reports scheduling, custom alerts and alerts scheduling, maintance 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 added DataPower devices to the standby DPOD server 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 server 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 may capture information while the other is shut down for maintenance.
  11. 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

...

  1. The customer's DR software should Identify a failure in DPOD primary server node (e.g. by pinging access IP, sampling user interface URL or both).

...

  • Although the passive DPOD server 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 server 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. Right after re-launching the primary servernode, call the "standbyToInactive" API (see DR REST API) to disable the standby servernode.
  2. Call the "activeBackToActive" API (see DR REST API) to re-enable the primary server node - this will point DPOD's log targets and host aliases on the monitored devices back to the primary DPOD servernode.
  3. The customer's DR software should change the DNS name for the DPOD servernode's web console to reference an actual IP address or use an NLB in front of both DPOD web consoles.

...