Running and Scheduling Storage Plans
After you create and configure a storage plan, run a successful readiness check and a DataLab test, the plan can be considered ready for failover. You can invoke various actions for the plan, depending on the current plan state.
Storage plans can acquire the following stable states:
Plan has never been tested or has never passed a readiness check.
Plan has failed to be tested or has failed to pass a readiness check.
Plan has been tested successfully or has passed a readiness check.
Plan has stopped due to either an error or user intervention.
Failover process completed successfully.
Failover process completed with warnings.
Failover process completed with errors.
Undo Failover process completed successfully.
Undo Failover process completed with warnings.
Undo Failover process completed with errors.
Plan testing has stopped due to either an error or user intervention.
Storage plans can acquire the following active states:
Plan is currently being created.
Plan is currently being edited.
Plan is currently being saved.
Plan editing and executing in this state are not available.
Plan is currently being executed.
Plan is currently being executed, a number of warnings encountered.
Plan is currently being executed, a number of errors encountered.
Plan testing has been started, but the DataLab required to test the plan has not been powered on yet.
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.
Plan testing is currently being halted.
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.
Plan readiness check is currently being halted.
Plan is currently being halted.
Plan testing is currently being powered off.
Plan is currently being resetted.
Plan is currently being deleted.
If you perform any infrastructure configuration changes (add, delete or rename VMs) or changes to Veeam ONE Client groups, Orchestrator will not automatically apply these changes to plans that are currently executing or testing — such plans are ‘locked’ and cannot be edited. The changes will take effect only if the plans enter the VERIFIED or NOT VERIFIED state.
Storage plans can acquire the following modes:
Plan is ready to be verified and executed.
Plan editing in this mode is not available. Automatic report updates in this mode are enabled.
Plan is ready to be edited and verified.
Scheduled plan execution in this mode is not available. Automatic report updates in this mode are disabled.
Plan is either in one of the active states (except the EDITING state) or in one of the stable states (except the VERIFIED and NOT VERIFIED states).
Plan editing and disabling in this mode are not available. Automatic report updates in this mode are disabled.
When a plan is in an active state, you can switch to the Plan Details page, select a VM being recovered in the Virtual Machines column, and click the VM Console link to connect directly to the VM desktop.
Orchestrator will connect to the VM through the vCenter Server system. To avoid connection failures, make sure the following requirements are met:
In vSphere 6.0 and later, each newly created ESXi host is by default provisioned with a self-signed certificate from the VMware Certificate Authority. If you want to use such a certificate when accessing the VM desktop, download the root CA certificate from the host where the VM is registered. To learn how to manage certificates for ESXi hosts, see VMware Docs.
To run a storage plan, it must be ENABLED. To enable a plan:
- Log in to the Orchestrator UI as an Orchestrator Administrator or Plan Author. For more information, see Accessing Orchestrator UI.
- Navigate to Orchestration Plans.
- Select the plan.
- From the Manage menu, select Enable.
If you do not enable a plan before you run it, the Run Plan wizard will force you to do that as soon as you try running the plan.
For more information on roles that can be assigned to users and user groups working with the Orchestrator UI, see Managing Permissions.
In This Section