Reference Guide

also pause, and subsequently resume, a replication session.
• Paused_for_NDU
• Paused_for_Migration
Parameters
Type Name Description Schema
Path
id
required
Unique identifier of the replication session. string
Responses
HTTP
Code
Description Schema
204 Success No Content
400 Invalid request error_response
404 Not Found error_response
422 Operation Failed error_response
POST /replication_session/{id}/failover
Description
Fail over a replication session instance. Failing over the replication session changes the role of the
destination system. After a failover, the original destination system becomes the source system, and
production access is enabled for hosts and applications for recovery. Failovers can be planned or
unplanned.
Planned failovers are issued from the source system and are indicated by setting the is_planned
parameter to true. When you fail over a replication session from the source system, the destination
system is fully synchronized with the source to ensure that there is no data loss. During a planned
failover, stop I/O operations for any applications and hosts. If a synchronization error occurs
during a planned failover, the replication session enters the System_Paused state. You cannot pause
a replication session during a planned failover. The following operations can be performed during
planned failover:
• Unplanned failover
• Delete the replication session by removing the protection policy on the storage resource
After a planned failover, the replication session is in an inactive state. You can use the reprotect
action to synchronize the destination storage resource, and then resume the replication session.
The auto-reprotect feature can also be used after a planned failover by using the reverse
190
Dell EMC PowerStore REST API Reference Guide