Performing Riverbed Disaster Recovery › How to Prepare and Test a Riverbed SteelStore Warm Disaster Recovery › Peer Replication Disaster Recovery Scenarios

Peer Replication Disaster Recovery Scenarios

Your Disaster Recovery procedures should already include the following systems:

• Plans and processes to recover the MVS system
• CA Vtape subsystems, applications, parameter libraries, and the Global VCAT and BSDS control files
• The catalog and tape management systems

Recovering these systems can be critical for business resumption.

The following scenarios describe the basic recovery strategies when running SteelStore Peer Replication.

• If service to the secondary appliance is temporarily interrupted and the primary is unable to replicate to the secondary, then the primary appliance pauses replication to the cloud. The data is stored only locally until service to the secondary appliance is restored.

  If the interruption is only a temporary condition, the primary appliance resumes replication as soon as the secondary appliance becomes available. No further action is required.

• If service to the primary appliance is temporarily interrupted, the secondary appliance state remains unchanged. You can continue to use the secondary appliance to provide read access to stored data.

  If the interruption is only a temporary condition, the primary appliance resumes replication as soon as the primary appliance becomes available. No further action is required.

• If the secondary appliance goes down permanently, then you can disable Peer Replication on the primary appliance to return it to stand-alone mode. The primary appliance retains ownership for management and can then resume replication of data that is stored at the cloud provider.

  To disable Peer Replication on the primary appliance, connect through the command-line interface and enter the following commands:

  whitewater > enable
  whitewater # configure terminal
  whitewater # no service enable
  whitewater # no replication peer enable
  whitewater # service enable
  whitewater # show service
  

  Note: Riverbed changed the product name from Whitewater to SteelStore. The commands are customizable and may not reflect this change. For more information about these commands, see the Whitewater Cloud Storage Appliance Command-Line Interface Reference Manual.

• If the primary appliance goes down permanently, switch the secondary appliance to replace it.

  To return the secondary appliance to stand-alone mode, disable Peer Replication. In this mode, you can switch ownership for management and replication of the data that is stored at the cloud provider to the secondary appliance. Starting the optimization service after disabling Peer Replication causes the appliance to request a switch in ownership of the cloud data. The process can take some time, depending on the amount of data stored.

• After the switch of ownership completes, you can mount the NFS exports of the appliance for read/write access.
• To disable Peer Replication on the secondary appliance, connect through the command-line interface and enter the following commands:

  whitewater > enable
  whitewater # configure terminal
  whitewater # no service enable
  whitewater # no replication peer enable
  whitewater # service enable
  whitewater # show service