# Performing a Failover for a Replication Consistency Group (Deprecated)

#### Function

This API is used to perform a failover for a replication consistency group. When an exception occurs in the primary AZ, a failover can be performed to change the primary site of a replication consistency group from the primary AZ to the secondary AZ and enable DR ECSs and DR disks in the secondary AZ to provide services.

After the failover, the replication_status value of the replication consistency group is active-stopped. In this case, EVS replication is available only after the primary AZ is restored and the replication consistency group is synchronized.

This API has been deprecated. To use this function, see Storage Disaster Recovery Service API Reference.

#### Constraints

If a fault occurs in the physical environment of the primary AZ due to force majeure and services become unavailable, perform a failover for the replication consistency group.

#### URI

- URI format

  POST /v2/{project_id}/os-vendor-replication-consistency-groups/{replication_consistency_group_id}/action

- Parameter description

  Parameter | Mandatory | Description
  --- | --- | ---
  project_id | Yes | Specifies the project ID.
  replication_consistency_group_id | Yes | Specifies the ID of the replication consistency group.

#### Request

- Parameter description

  Parameter | Mandatory | Type | Description
  --- | --- | --- | ---
  os-failover-replication-consistency-group | Yes | object | The parameter value is null, indicating that a replication consistency group failover will be performed.

- Example request

      {
          "os-failover-replication-consistency-group": null
      }

#### Response

None

#### Status Codes

- Normal

  Returned Value | Description
  --- | ---
  200 | The server has processed the request.

- Abnormal

  Returned Value | Description
  --- | ---
  400 Bad Request | The server failed to process the request.
  401 Unauthorized | You must enter the username and password to access the requested page.
  403 Forbidden | You are forbidden to access the requested page.
  404 Not Found | The requested page was not found.
  405 Method Not Allowed | You are not allowed to use the method specified in the request.
  406 Not Acceptable | The response generated by the server cannot be accepted by the client.
  407 Proxy Authentication Required | You must use the proxy server for authentication. Then, the request can be processed.
  408 Request Timeout | The request timed out.
  409 Conflict | The request cannot be processed due to a conflict.
  500 Internal Server Error | Failed to complete the request because of an internal service error.
  501 Not Implemented | Failed to complete the request because the server does not support the requested function.
  502 Bad Gateway | Failed to complete the request because the server has received an invalid response.
  503 Service Unavailable | Failed to complete the request because the service is unavailable.
  504 Gateway Timeout | A gateway timeout error occurs.

Parent topic: Replication Consistency Group (Deprecated)