Failback Replicas
failback_replicasFail back failed-over vSphere replicas by starting synchronization to an original, re-created, or custom target, then committing or undoing the failback and setting switchover timing.
Instructions
Failback of failed-over vSphere replicas, in steps:
start- sync replica changes back totarget(OriginalVM: the original VM,OriginalLocation: re-create it where it was,Customized: elsewhere).switchoverdecides when production takes over (Auto,Manualthenswitch_to_production, orScheduled; change it later withchange_switchover_time).commit- finalize; orundo- return to the failed-over state.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"action": "<action>",
"replica_point_ids": "<replica_point_ids>"
},
"name": "failback_replicas"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| target | No | action='start': where to fail back to. | |
| customized | No | target='Customized': extra ViVMSnapshotReplicaCustomizedFailbackSpec fields - destinationhost, resourcePool, datastore, folder, network (see describe_model). | |
| switchover | No | ReplicaFailbackModeSpec {'type': 'Auto'|'Manual'|'Scheduled', 'scheduledTime': ISO-8601}. | |
| confirm_token | No | ||
| dr_site_proxy_ids | No | ||
| replica_point_ids | Yes | ||
| power_on_target_vm | No | ||
| production_site_proxy_ids | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||