| Name | Description |
| cleanupTest |
Cleanup after a test run.
|
| failover |
Failover the recovery plan to the peer site. The user can failover multiple
times in case problems occured on previous runs. Once completed successfully,
the plan should be deleted or reprotected.
For a plan to be successfully failed over, all of the groups in the plan must be
in the shadowing, recovered, or partiallyRecovered states.
|
| migrate |
Migrate the recovery plan to the peer site. Once completed successfully,
the plan should be deleted or reprotected.
For a successful migration to occur all of the groups in the plan must be in the
shadowing or recovered states.
Since SRM API 3.0
|
| reprotect |
Complete an already finished recovery, and start protecting the groups so they
may be recovered on the peer site.
This will unregister the VMs on the peer site, configuring the storage, and the
shadow VMs. This operation may only be performed when the sites are connected,
and at least one protection group is in the recovered or partiallyRecovered
state.
|
| revert |
Revert a recovery, abandoning all the VMs on the peer site and powering on the
original VMs on the local site.
This operation is not allowed unless all of the replication groups are in the
shadowing, recovered, or partially recovered state.
If the sites are not connected, the peer VMs may be left running. In order to
correct this situation, revert may be re-run after the sites are connected.
|
| test |
Run a test-failover at this site, leaving the primary state unaffected.
For a plan to be successfully tested, all of the protection groups must be in
the shadowing state.
|