Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerVault ME4 Series Storage System CLI Guide

PDF

recover replication-set

Description Provides options to recover a replication set after a disaster. All options work with either a single volume or a volume group. First you run the command to perform a failover operation. After this operation completes, you rerun the command to perform one of the following recovery operations: failback-no-restore, or reverse.
CAUTION:The reverse operation is designed to discard the latest updates to a primary volume. This is not a problem if the operation proceeds without error. However, if errors occur, you could lose data. To mitigate this potential problem, take a snapshot of the primary volume before performing this recovery operation.
Minimum role manage
Syntax recover replication-set

operation failover|failback-no-restore|reverse

replication-set-ID

Parameters

operation failover

Moves the replication set into the "failed over" state, which is required for performing a subsequent recovery operation. You must run this on the secondary system. To use this option:
  • The replication set can be in any state except "failed over."
  • Peer communication can be online or offline.

failback-no-restore

Restores the replication set to functioning as it did before the failover operation was performed, without using updates made to the secondary volume while the replication set was failed over to the secondary system. You must run this on the secondary system. To use this option:
  • The replication set must be in the "failed over" state.
  • Peers must be operational with both systems healthy and communicating.

reverse

Restores the replication set to normal operation but with the replication roles reversed. You must run this on the secondary system. To use this option:
  • The replication set must be in the "failed over" state.
  • Peers must be operational with both systems healthy and communicating.

replication-set-ID

The name or serial number of the replication set. A name that includes a space must be enclosed in double quotes.
Examples Assume that a disaster took the primary system for replication set RS1 offline. To move RS1 into "failed over" state and make its secondary volume accessible, you ran the following command:

# recover replication-set operation failover RS1

You then mapped the secondary volume and updates to its data started. Now repairs have been made, the primary system is back online, and peer communication has been reestablished. You want to replace the old data on the primary system with the current data on the secondary system. Also, you want to preserve the data state of volumes on the primary systems to avoid risk of data loss. You would do the following:
  1. On the primary system, snap local replication set volumes.
  2. On the secondary system:
    1. Snap local replication set volumes.
    2. Run: recover replication-set operation reverse RS1
    3. Run: replicate RS1
  3. On the primary system:
    1. Confirm that the replication has completed by periodically running:

      show replication-sets RS1

    2. Run: recover replication-set operation failover RS1
    3. Run: recover replication-set operation reverse RS1
    4. Reestablish primary volume mappings.
See also

create snapshots

map volume

show replication-sets


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\