You can monitor the status of a recovery plan and determine the operation that is allowed in each state. The states of the protection groups within a recovery plan determine the state of the plan.
| State | Description |
|---|---|
| Ready | Recovery steps are cleared. For storage policy protection groups, recovery steps do not show virtual machines and consistency groups when a recovery plan is in this state. You can verify protected virtual machines in a recovery plan in the Virtual Machines tab. |
| Test in progress | Canceling a test moves plan to Cancel in progress state. |
| Test complete | Test completed with or without errors. If a failure occurs during the test, plan goes to Test Interrupted state. |
| Test interrupted | Server failed while a test was running. |
| Cleanup in progress | After successful cleanup, plan state goes to Ready. If cleanup is incomplete, state goes to Cleanup Incomplete. If you set the Force Cleanup option, state goes to Ready after an error. If a failure occurs during cleanup, state goes to Cleanup Incomplete. |
| Cleanup incomplete | Errors occurred during cleanup. You can run the cleanup again. When running cleanup from this state, the cleanup wizard provides an option to ignore errors. |
| Cleanup interrupted | Site Recovery Manager failed during cleanup. You cannot change recovery options. |
| Recovery in progress | If you cancel recovery, the state goes to Cancel in progress. |
| Disaster recovery complete | During recovery at the protected site, VM shutdown encountered errors, possibly because the sites were not connected, the step before split brain. System prompt warns of split brain and to run recovery again when sites reconnect. When sites are connected, state goes to Recovery required (split brain). |
| Recovery started | A recovery started on the peer site, but if the sites are not connected, the exact state is unknown. Log in to the recovery site or reconnect the sites to get the current state. |
| Recovery required (split brain) | Sites were disconnected during recovery. Split-brain scenario detected when sites reconnect. System prompts you to run recovery again to synchronize the sites. For storage policy protection groups, recovery steps do not show virtual machines and consistency groups when a recovery plan is in this state. You can verify protected virtual machines in a recovery plan in the Virtual Machines tab. |
| Recovery complete | If errors, VMs are all recovered but with errors. Running recovery again does not fix the errors. Plan goes to this state after the split brain recovery is resolved. You can see the recover steps of the last recovery run. For storage policy protection groups, recovery steps do not show virtual machines and consistency groups when a recovery plan is in this state. You can verify protected virtual machines in a recovery plan in the Virtual Machines tab. Sites were disconnected during recovery. The connection status is the only property that triggers this state. |
| Incomplete recovery | Canceled recovery or datastore error. Run recovery again. You must either resolve errors and rerun recovery, or remove protection for VMs in error. The plan detects the resolution of errors in either of these ways and updates state to Recovery complete. |
| Partial recovery | Some but not all protection groups are recovered by an overlapping plan. |
| Recovery interrupted | A failure during recovery causes the recovery to pause. Click Run to continue. You cannot change recovery options. |
| Cancel in progress | Canceling a test results in Test complete with last result canceled. Canceling a recovery results in Incomplete recovery with last result canceled. If the operation is canceled early enough, might result in a Ready state. |
| Reprotect in progress | If the server fails during this state, it goes to Reprotect interrupted. |
| Partial reprotect | Overlapping plan was reprotected. The already reprotected groups go to Ready state, but this is valid, since the other groups are in the Recovered state. |
| Incomplete reprotect | Reprotect did not complete the storage operations. Sites must be connected for the reprotect to succeed on the new run. Reprotect completed the storage operations but did not complete creating shadow virtual machines. You can run reprotect again even if the site running the virtual machines is disconnected, then proceed to recovery immediately after. |
| Reprotect interrupted | If the Site Recovery Manager Server fails during reprotect, run reprotect again to continue and properly clean up the state. |
| Waiting for user input | Test is paused. Close the prompt to resume the test. Recovery is paused. Close the prompt to resume recovery. |
| Protection groups in use | Plan contains groups that are being used for a test by another plan. This state also occurs when the other plan has completed a Test operation on the groups, but has not run Cleanup. Wait for the other plan to complete the test or cleanup or edit the plan to remove the groups. |
| Direction error | Groups are in a mixed state, which is an invalid state. The plan contains different groups that are Ready in opposite directions. Select one direction as correct and remove the protection groups that are in the opposite direction. For this error to occur, overlapping plans have run and reprotected some of the groups in the plan already. |
| Deleting | Plan enters this brief state while waiting for deletion of a peer plan. Plan automatically completes when the other plan is deleted. |
| Plan out of sync | This state can occur under different circumstances:
Opening the plan for editing and saving the changes after edit causes Site Recovery Manager to force synchronization of Site Recovery Manager internal data about the plan between protection and recovery Site Recovery Manager servers, which clears the Plan out of sync status . |
| No protection groups | The plan contains no protection groups and the plan cannot run. You can edit the plan including the recovery site. You can create empty plans through the API or UI, or by deleting protection groups. |
| Internal error | A protection group with an unknown state is in the plan, or some other unexpected error occurred. You cannot run the plan but you can delete it. |
