This is an archive version of the document. To get the most up-to-date information, see the current version.

Running and Scheduling Failover Plans

After you create and configure a failover plan, run a successful readiness check and a virtual lab test, the plan can be considered ready for failover. You may invoke various actions for the plan, depending on the current plan state.

Failover plans may acquire the following stable states:

Plan State	Icon	Description
NOT VERIFIED		Plan has never been tested and/or has never passed a readiness check.
NOT VERIFIED		Plan has failed to be tested and/or has failed to pass a readiness check.
VERIFIED		Plan has been tested successfully and/or has passed a readiness check.
HALTED		Plan has stopped either due to error, or user intervention.
FAILOVER		Failover process is complete successfully.
		Failover process is complete with warnings.
		Failover process is complete with errors.
UNDO FAILOVER		Undo Failover process is complete successfully.
		Undo Failover process is complete with warnings.
		Undo Failover process is complete with errors.
PERMANENT FAILOVER		Permanent Failover process is complete successfully.
		Permanent Failover process is complete with warnings.
		Permanent Failover process is complete with errors.
FAILBACK		Failback process is complete successfully.
		Failback process is complete with warnings.
		Failback process is complete with errors.
UNDO FAILBACK		Undo Failback process is complete successfully.
		Undo Failback process is complete with warnings.
		Undo Failback process is complete with errors.
COMMIT FAILBACK		Commit Failover process is complete successfully.
		Commit Failover process is complete with warnings.
		Commit Failover process is complete with errors.
TESTING HALTED		Plan testing has stopped.

Failover plans may acquire the following active states:

Plan State	Icon	Description
EDITING		Plan is currently edited.
PROCESSING		Plan is currently executing.
		Plan is currently executing, a number of warnings encountered.
		Plan is currently executing, a number of errors encountered.
TESTING PENDING		Plan testing has been started, but the virtual lab required to test the plan has not been powered on yet.
TESTING		Plan testing is in progress.
		Plan testing is in progress, a number of warnings encountered.
		Plan testing is in progress, a number of errors encountered.
TEST HALTING		Plan testing is currently halting.
CHECKING		Plan readiness check is in progress.
		Plan readiness check is in progress, a number of warnings encountered.
		Plan readiness check is in progress, a number of errors encountered.
CHECKING HALTING		Plan readiness check is currently halting.
HALTING		Plan is currently halting.
POWERING OFF		Plan testing is currently powering off.

Running and Scheduling Failover Plans Note:

If you perform any infrastructure configuration changes (add, delete or rename VMs) or changes to Veeam ONE Monitor groups, VAO will not automatically apply these changes to plans which are currently executing or testing — such plans are ‘locked’ and may not be edited.

The changes will take effect only if the plans enter the VERIFIED or NOT VERIFIED state. However, you will have to wait for the synchronization between VAO sites to complete. The synchronization interval will depend on the selected data collection settings. For more information on editing synchronization settings, see Configuring Veeam Availability Orchestrator.

Before You Begin

To run a failover plan, it must be ENABLED. To enable a plan:

Log in to the VAO UI in the DR site as a Site Administrator or Failover Plan Author. For details, see Accessing VAO UI.
Navigate to Failover Plans.
In the Enabled column, select the check box next to the plan name.

Running and Scheduling Failover Plans Note:

For security purposes, all ‘real-world’ actions associated with failover plans (such as failover and failback) require password confirmation.

In This Section