Disaster Recovery Promote Standby To Active

Promotes the current server to take over as the single standalone VCO. The current server is expected to be a standby in the drState FAILURE_MYSQL_STANDBY_STATUS, meaning that DR protection had been engaged (with the last successful replication status observed at lastDRProtectedTime), but that standby has been unable to replicate since that time. If the standby server is in the drState STANDBY_RUNNING, meaning that it has detected no problems in replicating from the active server, the operator can force promotion of the standby using the optional force parameter passed with a value of true. In this case, the standby server will call demoteActive/force on the active server. The operator should, if possible, ensure that the formerly active server is demoted by running demoteServer directly on that server if the standby server was unable to do so successfully.

Privileges required:

CREATE REPLICATION

Request

URI

POST

https://{api_host}/portal/rest/disasterRecovery/promoteStandbyToActive

COPY

Request Body

{
    "force": false
}

boolean

force

Optional

force

Responses

200

Request was successfully processed

Returns disaster_recovery_promote_standby_to_active_result of type(s) application/json

This response body class contains all of the following: Inlinedisaster_recovery_promote_standby_to_active_result0

{
    "rows": 1
}

400

Returns generic_400 of type(s) application/json

Operation doesn't return any data structure

500

Returns generic_500 of type(s) application/json

Operation doesn't return any data structure

Code Samples

COPY

                    curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{}' https://{api_host}/portal/rest/disasterRecovery/promoteStandbyToActive

On This Page

Description

Request

Request Body

Response

200 Response Body

Errors

All Operations

POST

Disaster Recovery Configure Active For Replication

POST

Disaster Recovery Demote Active