TODO - ADD Active/Active - full duplication scenario
...
High Availability (HA), Resiliency or Disaster Recovery (DR) Implementation
There are multiple methods available to achieve DPOD HA/DR planning and configuration. These methods depend on the customer's requirements, implementation and infrastructure.
DPOD Scalability vs. HA/DR
DPOD supports installing multiple DPOD servers for scalability to support high throughput in case of high rate of transactions per second (TPS). However, this does not provide a solution for HA/DR requirements.
For simplicity, this document assumes that only one DPOD server is installed, but exactly the same scenarios and considerations apply for multiple servers installations.
Important HA\DR considerations
Consult your BCP/DR/System/Network Admin and address the following questions before selecting the method(s) of HA/DR implementation with DPOD to use:
11. For large installations, DPOD can capture vast volumes of data. Replicating that much data to for DR purposes may consume significant network bandwidth, and may incur 3rd party storage replication license costs.
You should consult and decide: Is it cost effective to replicate DPOD data or is it is acceptable to launch DPOD on a backup server another instance of DPOD with configuration replication only?
2. The software used for Active/Passive scenario:
Does DPOD in your DPOD runs case run on a virtual infrastructure like VMWare VMware or can you use VMware VMotion or Active\Passive Cluster cluster management tools that can help identify and relaunch DPOD on a different cluster member?
...
3. The customer is You are expected to have an Active/Passive software or another mechanism in place to identify when the DPOD server becomes inactive and launch a new one in an active Cluster cluster member.
Do you have such a tool (DR Softwaresoftware)?
...
4. When launching a new DPOD instance on the backup cluster member:
Will the new server instance keep the same network configuration of the primary node instance (for example: IP Address, DNS, NTP, LDAP, SMTP) or or will the configuration change?
...
5. Some DataPower architecture solutions (Active/Passive or Active/Active) effect DPOD configuration. If the DataPower IP address changes - then your DPOD configuration may need to change.
...
Common scenarios for implementing DPOD HA/DR
Scenario A
...
: Active/Passive - DPOD's IP Address remains the same
Assumptions:
- 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.
- DPOD is server is installed once and is configured to monitor all DataPower appliances (active, standby and passive). HANAN - WHY ONCE? WE HAVE ACTIVE AND PASSIVE. IF THIS IS TRUELY ONCE THEN THE PHRASING SHOULD BE DIFFERENT AND TELL THE CUSTOMER TO BRING UP THE SAME SERVERS ON A DIFFERENT VM RACK
- All DPOD network services (NTP, SMTP, LDAP etc.) have the same IP address 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.
- The customer has a 3rd party software tool or scripts that can:
- Identify unavailability of the primary DPOD server/s.
- Launch the a passive DPOD servers using server using the same IP address as the active primary one.
6. The passive DPOD server is not up running when business is as usual (since in this scenario it has the same IP address as the active DPOD server).
During a disaster:
- The customer's DR software should Identify a DPOD failure (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 server using the same IP address as the failed primary server (or change the IP address ( if not already configured ) to be identical to the failed active DPODthat way).
DPOD will be available in the following way:
- As the passive DPOD 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 passive DPOD has the same IP address as the primary one, access to DPOD console will be with the same URL.
...