Recovering virtual machines from Azure / Azure Stack to Azure / Azure Stack
Using Veritas Resiliency Platform 10.4, you can configure and protect your virtual machines for recovery from Azure to Azure using the Resiliency Platform Data Mover which includes combination of :
Azure Stack to Azure Stack
Azure Stack to Azure region
Azure region to Azure region
Azure region to Azure Stack
You can use the same or different Azure cloud subscriptions for using the Azure resources. Following are the features supported for this use case:
NRT discovery support is enabled for the virtual machines which are present at the target data center. Using NRT, the real-time updates related to network and virtual machines are discovered.
You can now edit the migrated virtual machine, add/ remove the virtual machine from a resiliency group on the target data center.
Rehearsal operation is enabled when target data center is Azure and vice versa.
Network customization feature is added where you can enable or disable IP customization on both source and target data center.
The following table provides the summary for deployment, configuration, and recovery of virtual machines to a data center on Azure to Azure which includes (Azure Stack to Azure Stack, Azure Stack to Azure region, Azure region to Azure region and Azure region to Azure Stack).
Table: Recovering virtual machines from Azure to Azure
Tasks | More information |
|---|---|
Plan your environment | Refer to the Overview and Planning Guide to know about the product, its components, features, and capabilities. Refer to the Release Notes for release information such as main features, known issues, and limitations. Ensure that the configuration details in your environment are compatible with the requirements mentioned in the checklist. |
Deploy and configure the virtual appliances | Veritas Resiliency Platform is deployed as virtual appliances. Download and deploy the virtual appliances in the Azure cloud data center on source and target data centers.
|
Set up the resiliency domain | Set up the infrastructure and basic settings of the Veritas Resiliency Platform resiliency domain. These tasks are performed after you configure the Resiliency Manager and log in to the web console.
Using the Resiliency Platform console, you can add one or more Azure Stack private cloud instances to the non-cloud datacenter (premise) at source, or at target or both data centers. Azure Stack private cloud can be added to non-cloud datacenter only.
|
Add asset infrastructure | Before you can monitor and manage data center assets from the console, you must add the asset infrastructure to Veritas Resiliency Platform. The IMS then discovers the asset information for monitoring and operations in the console. |
Infrastructure Pairing | For recovering assets to Azure you have to do following Infrastructure Pairing:
|
Create resiliency groups | After adding the assets to Resiliency Platform, you organize the related assets into a resiliency group that you can protect and manage as a single entity. You can create a resiliency group either for basic monitoring (start or stop virtual machines) or for remote recovery. |
Advance features | Virtual business services, resiliency plans, and evacuation plans are some of the features of Veritas Resiliency Platform that you can additionally use to customize the process of recovery of your assets. |
Perform remote recovery operations | Once you have configured the resiliency groups for remote recovery, you can perform rehearsal and cleanup rehearsal operations on the resiliency groups. You can also perform migrate, recover, or resync operations on the resiliency groups. From version 10.4, Resiliency Platform supports rehearsal operation from Azure region to Azure region along with (Azure Stack to Azure Stack, Azure Stack to Azure region, and Azure region to Azure Stack) . |
Monitor assets | You can monitor risks to the recoverability or continuity of your protected assets. Run various reports to view the status of the assets in your data center. And view details about operations such as the status (in-progress, finished, or failed), start and end time, and the objects on which the operation was performed on the Activities page. |
Miscellaneous references | After the virtual appliances are deployed and configured, you are given limited menu-based access to the operating system and the product. You need to use klish menu to manage the configuration-related changes to the product and to troubleshoot. |
