High Availability (HA), Resiliency or Disaster Recovery (DR) Implementation
There are multiple methods available to achieve DPOD HA/DR planning and configuration. These methods are determined based on the customer's requirements, implementation and infrastructure.
Terminology
Node State/mode - A DPOD node can be in one of the following states: Active (Onpowered on, performing monitoring activities), Inactive (Offpowered off, not performing any monitoring activities), DR Standby (Onpowered on, not performing monitoring activities).
...
3rd party DR software - A software tool that assists in the process of identifying when the primary node state has changed from active to inactive and initiates the process of launching the secondary node as active .
DPOD Scalability vs. HA/DR
The DPOD architecture supports installation of multiple DPOD nodes for scalability - to support high throughput in cases 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 node is installed, but the same scenarios and considerations apply for multiple nodes installations.
Important HA/DR Considerations
Consult your BCP/DR/System/Network Admin and address the following questions before selecting which method(s) of HA/DR implementation with DPOD to use:
...
Does your DataPower architecture use an active/passive deployment? If so - will the passive DataPower have the same IP address when it switches to active?
Common Scenarios for DPOD HA/DR Implementation
Scenario A: Active/Passive - DPOD's IP Address remains the same - Shared Storage
...
- No action is required. The DataPower instance will push data to both instance
- The data gathered throughout the disaster period can not be synced back to the recovered node
Backups
To To improve product recovery, an administrator should perform regular backups as described in the backup section.
...