replication policy

DPOD has 3 disks (DPOD Developer Edition is not supported for HA\DR):

• • Disk 1 – Operating System,
  • Disk 2 – Application & Configuration,
  • Disk 3 – Data of all monitored Data Power’s transaction and configuration.

1. For launching DPOD server in a replicated environment customer must replicate Disk1 and Disk 2 on a regular basis as they usually have a reasonable rate of changes.
2. Replicating Data Disk (Disk 3) can generate  massive IOPS and bandwidth usage which can be a burden on the customer replication mechanism.
   In cases it is acceptable for customer to launch its passive server without the data, customer can follow this step to create a clean working data disk (disk 3):
   1. Customer must create a full back of disk 3 when all DPOD services are down.
   2. Customer must copy the backup of disk 3 to passive DPOD server storage and make sure it is attached to the passive DPOD server.
   3. Customer must start the passive DPOD server and verify that DPOD is fully started and operational.
   4. Customer should delete DPOD data (if exists) using the DPOD web console (Manage -> Internal Health -> Store)
   5. Customer can shut down the secondary DPOD and start the replication for DISK 1 and 2 only.
   6. After each DPOD upgrade it is recommended to rerun this procedure in case directory structure in Disk 3 changed.