How Orchestrator Manages HPE Storage Failover
Orchestrator orchestrates storage failover in the following way when running an HPE storage plan:
- Before Orchestrator starts processing inventory groups included in the plan, it performs a number of pre-plan steps to prepare the failover environment:
- Orchestrator runs the VM Control step to shut down source VMs running in the production vCenter Server. To answer VM questions that appear while shutting the VMs down, Orchestrator applies default answers specified in the vCenter Server settings.
The VM Control step has a preconfigured timeout parameter that defines the exact amount of time for the step to execute. If the step execution time exceeds the defined parameter value, Orchestrator powers the source VMs off.
- Orchestrator runs the Storage Failover step. It stops the remote copy group, performs failover on the remote copy group, mounts the secondary volumes to the target vCenter Server, and then mounts the recovered datastores to all hosts in the required storage recovery location.
For more information on the way Orchestrator identifies storage recovery locations required to recover datastores, see How Orchestrator Places VMs During Storage Failover.
- When processing inventory groups, Orchestrator registers target VMs on hosts in the disaster recovery site, and then powers the VMs on.
For more information on the way Orchestrator defines hosts where recovered VMs will be registered, see How Orchestrator Places VMs During Storage Failover.
- After Orchestrator finishes processing inventory groups, it performs a number of post-plan steps to finalize the storage failover process:
- Orchestrator runs the Unregister Source VMs step to unregister source VMs from hosts in the production site.
- Orchestrator runs the Unmount Source Datastores step to unmount the source volumes from the source vCenter Server.
When Orchestrator orchestrates storage failover, it handles specific internal elements — protection groups and storage items:
Protection groups and storage items were introduced into Orchestrator to exclusively support the storage failover process. That is why the Orchestrator UI does not show these elements, but you may come across them in some reports and log entries.