Dell PowerStore 9200T EMC PowerStore Protecting Your Data - Page 22

Failover, Perform a failover test

Get Dell PowerStore 9200T PDF manuals and user guides View all Dell PowerStore 9200T manuals
Add to My Manuals
Save this manual to your list of manuals

Page 22 highlights

● Operating normally ● System paused While a replication session is synchronizing, you can take the following actions: ● Planned failover from the source system ● Fail over from the destination system ● Pause replication sessions from the source or destination system ● Delete a replication session by removing a protection policy If synchronization fails, the replication session is placed in a system paused state. When the system recovers, the replication session continues from the same point as when the system was paused. Failover Failing over a replication session includes switching roles between the source and destination systems and reversing the direction of the replication session. There are two types of failovers: ● Planned failover - User initiated, includes synchronization between source and destination to prevent data loss. ● Unplanned failover - Initiated by the destination system in response to source system failure. During a replication session failover, the system performs the following actions: ● Stop I/Os on the source object. ● Synchronize the source and destination storage objects (occurs only in a planned failover). ● Stop the replication session. ● Reverse roles between source and destination systems. ● Promote the latest object version on the new source. ● Resume I/Os on the new source (initiated by the user). After a failover, you can access applications on the new source system to recover data. Perform a failover test After you set up a replication session, you can test the connection to ensure that your sites are correctly configured and prepared for disaster recovery. During a failover test, the system performs a failover and production access is provided to the destination site using replicated data or a point-in-time snapshot. The destination storage resource is available in read/write mode, and production access is enabled for hosts and applications. You can verify your disaster recovery configuration while replication continues to run in the background. When you wish to stop the failover test, select one of the following actions: ● Failover to the current test data - If you made changes to the data during the failover test, you can use the updated test data. This will stop the test and preserve the test data. Any data replicated from the source during the test will be discarded and the destination system will become the source. NOTE: You must acknowledge these changes before failing over to the test data. ● Stop the failover test - When you stop the test, production access to the destination will be disabled for hosts and applications and the destination storage resource will be updated with the latest data synched from the source system. You can create a backup snapshot of the test data before stopping the failover test. Restrictions A failover test can only be performed under the following conditions: ● The PowerStore system version on both the source and destination system is 2.x or later. ● The replication session state is not Initializing, Failing Over, Failed Over, Paused for NDU/Migration, or Failover Test in Progress. During the failover test, you cannot execute the following actions on the destination system: ● Change volume group membership 22 Replication

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
●
Operating normally
●
System paused
While a replication session is synchronizing, you can take the following actions:
●
Planned failover from the source system
●
Fail over from the destination system
●
Pause replication sessions from the source or destination system
●
Delete a replication session by removing a protection policy
If synchronization fails, the replication session is placed in a system paused state. When the system recovers, the replication
session continues from the same point as when the system was paused.
Failover
Failing over a replication session includes switching roles between the source and destination systems and reversing the
direction of the replication session.
There are two types of failovers:
●
Planned failover - User initiated, includes synchronization between source and destination to prevent data loss.
●
Unplanned failover - Initiated by the destination system in response to source system failure.
During a replication session failover, the system performs the following actions:
●
Stop I/Os on the source object.
●
Synchronize the source and destination storage objects (occurs only in a planned failover).
●
Stop the replication session.
●
Reverse roles between source and destination systems.
●
Promote the latest object version on the new source.
●
Resume I/Os on the new source (initiated by the user).
After a failover, you can access applications on the new source system to recover data.
Perform a failover test
After you set up a replication session, you can test the connection to ensure that your sites are correctly configured and
prepared for disaster recovery.
During a failover test, the system performs a failover and production access is provided to the destination site using replicated
data or a point-in-time snapshot. The destination storage resource is available in read/write mode, and production access is
enabled for hosts and applications. You can verify your disaster recovery configuration while replication continues to run in the
background.
When you wish to stop the failover test, select one of the following actions:
●
Failover to the current test data - If you made changes to the data during the failover test, you can use the updated test
data. This will stop the test and preserve the test data. Any data replicated from the source during the test will be discarded
and the destination system will become the source.
NOTE:
You must acknowledge these changes before failing over to the test data.
●
Stop the failover test - When you stop the test, production access to the destination will be disabled for hosts and
applications and the destination storage resource will be updated with the latest data synched from the source system. You
can create a backup snapshot of the test data before stopping the failover test.
Restrictions
A failover test can only be performed under the following conditions:
●
The PowerStore system version on both the source and destination system is 2.x or later.
●
The replication session state is not Initializing, Failing Over, Failed Over, Paused for NDU/Migration, or Failover Test in
Progress.
During the failover test, you cannot execute the following actions on the destination system:
●
Change volume group membership
22
Replication