Disaster Recovery Test for Objects

Disaster Recovery Test for Objects is a LI REQ operation performed at the host that groups one or more clusters into a disaster recovery (DR) "family".

The object DR family contains any combination of clusters in a grid that the user wants to include in the Object Disaster Recovery (ODR) test. The DR family is assigned via LI REQ, and clusters will be considered Production Host, or DR Host sites. Through the Management Interface (MI), cloud names are assigned to DR Families, and only those cloud names will be considered when a DR test is active.

Prerequisites:

Supported Configurations

  • Must be a VED or newer models
  • Can be stand-alone or in a Grid
  • Supported on TS7770D, TS7770T, TS7770C, TS7780D, TS7780T, or TS7780C
  • Must have FC 5283 installed on the TS7700s to take advantage of this feature
  • All clusters in the grid must be at R6.0 code level or higher to enable disaster recovery for object testing. This is regardless of whether the cluster is FC 5283 enabled or not. No mixed code level environments allowed.
  • Starting with R5.3, only TS7770 VED clusters are supported, so no older TS7700 models can exist in the grid to enable DR testing for objects.

The user will start the ODR SNAP from the LI REQ command. When an Object DR SNAP for an Object DR family is enabled, the following rules will be enforced from the SNAP's start "Point in Time," based on whether a cluster is a Production site or a DR site.

Production Host can:

  • Read existing objects
  • Delete/Create Objects and Containers
  • Copy Polices are honored across grid
  • Note: All changes remain after SNAP, STOP.

Production Host CANNOT:

Access Objects/Containers created by DRHOST after SNAP START

DR Host can:

  • Read all existing objects (At time of SNAP)
  • Delete/Create/Read Objects and Containers
  • Copy policies are ignored
Note: All changes are removed after SNAP, STOP.
DR Host CANNOT:
  • Access Objects/Containers created by Production Host after SNAP START

Note: The ODR SNAP can be stopped or reset (reset Point in Time) by using LIREQ.