Reset Standby

• URL:https://<root>/data/<datastoreID>/resetStandby(POST only)
  
• Required Capability: Default administrator role | Publisher role
• Version Introduced:11.2

Description

The resetStandby operation resets the tracking mechanism used to identify a failure of the primary relational data store and forces a reconfiguration of the standby relational data store. If administrators choose to redeploy the standby's underlying PersistentVolumeClaim (PVC), the PVC is deleted as part of the reset. Doing so allows for the standby's StatefulSet to be rescheduled to a separate availability zone without a volume affinity conflict with the existing PersistentVolume.

Request parameters

Parameter	Details
redeploy	Specifies whether the underlying PVC is deleted as part of the standby instance reset. The default value is false. Values: true | false
async	Specifies whether the operation should run synchronously or asynchronously. If false, the operation is run synchronously. If true, the operation is run asynchronously and the response returns a JSON object containing job information that can be used to track the job's status. The default is false. Values: true | false
f	The response format. The default format is html. Values: html | json | pjson

Example usage

The following is a sample POST request for the resetStandby operation:

POST /context/admin/data/438a9119c8dc4eb2900abd075327e2c5/resetStandby HTTP/1.1
Host: organization.domain.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []

redeploy=true&async=true&f=pjson&token=P4Vn2uao41gcVGxM8p3lwYgQnt9t20hRo8s4TDsH2XRtiF3xh-lNTfn1dIOaw3ke2P8nCQwjxeLV4kNiftyKCESSEPXiIbQGt9Ph7Bx_LQIGkIoXYZBNOWnOi7Fw8Z5GRg2_xYSWoLg8zzZcO3utdVsIG1Ew7Ab8f-Ti28TfUvtv7cWM9BzRaw00EtqbdJj0zu23kTYNsOO0KaXkJ5IR8wF1qGxD6-KmVyOdfC9ms51khCiq473WAo4Ho8zwkdwV

JSON Response example

{
  "jobsUrl": "https://organization.domain.com/context/admin/jobs/ja2ca1a35-881c-400c-a49a-b26883002d6c",
  "jobID": "ja2ca1a35-881c-400c-a49a-b26883002d6c",
  "jobStatus": "SUBMITTED"
}