Prepare production workloads, Azure Cleanroom and Commvault environment to perform a recovery into a Cleanroom site.
Production Workloads
Complete the steps listed below to prepare production workloads.
-
Windows VMs
-
Enable SAN Policy on the Source VM.
Note
No reboot is required, but it is still recommended.
-
Verify that all other steps required to convert VMs into Azure are successfully completed.
-
Linux VMs
-
Make a snapshot or backup of the source VM before modifying it.
-
In addition, perform the following steps:
-
Edit the /etc/dracut.conf file, and then add the following:
add/_drivers+="hv/_vmbus hv/_netvsc hv/_storvsc"
-
Verify that no dracut conf files (for example, /usr/lib/dracut/dracut.conf.d/01-dist.conf) contain the following lines. If it contains, comment out the lines
hostonly="yes" <br>
- Rebuild the initramfs:
Reboot the VM and check that it still boots fine.sudo dracut -f -v <br>
-
-
Install Azure Linux Agent on Source VMs. No reboot is required, but it is still recommended.
-
Verify that all other steps required to convert VMs into Azure are successfully completed.
-
Azure Cleanroom
Complete the steps listed below to prepare Azure Cleanroom.
1. Verify the Subscription
Ensure your Azure Cleanroom subscription has been created.
2. Verify the Resource Providers are Enabled in Azure Cleanroom
The following Resource Providers must be enabled in Azure Cleanroom:
- microsoft.support
- microsoft.Storage
- microsoft.SerialConsole
- microsoft.ResourceNotifications
- microsoft.ResourceGraph
- microsoft.Portal
- microsoft.OperationalInsights
- microsoft.Network
- microsoft.MarketplaceOrdering
- microsoft.MarketplaceNotfications
- microsoft.MachineLearning
- microsoft.GuestConfiguration
- microsoft.Features
- microsoft.CostManagement
- microsoft.Consumption
- microsoft.Compute
- microsoft.Commerce
- microsoft.CloudShell
- microsoft.ClassicSubscription
- microsoft.ChangeAnalysis
- microsoft.Billing
- microsoft.Authorization
- microsoft.ADHybridHealthService
3. Create an Azure App Registration for Commvault
Verify that an App Registrationhas been created for Commvault with correct permissions for the entire Cleanroom subscription and for the Storage Account (Storage Account Contributor and Storage Blob Data Contributor).
4. Verify the Staging Storage Account
Verify that the Resource Group and Storage Account is created with accurate configuration in the region where the VMs will be recovered (only locally-redundant storage (LRS) and StorageV2-general purpose v2-accounts are supported).
Note
Make sure that the virtual network where the access nodes will be created has access to the storage account.
5. Set Up a Virtual Network for Cleanroom Recovered VMs
- Verify that a virtual network is created where the Cleanroom recovery VMs are recovered.
-
Verify that the Cleanroom virtual network is isolated. This means there must be no inbound and outbound connectivity, except RDP/SSH through specific IP addresses to access the recovered machines.
Alternatively, you can enable bastion host to access the machines directly from the Azure portal without opening the RDP/SSH ports.
6. Set Up a Virtual Network for Commvault Access Nodes
Create an additional virtual network where the auto-scaled access nodes will be created. This virtual network should have inbound and outbound connectivity to the Cleanroom recovered Control Plane (CommServe).
The following ports must be open on the additional virtual network:
- 8400 and 8403 for Control Plane connectivity
- 443 for AGP connectivity
Commvault Environment
Complete the steps listed below to prepare Commvault environment.
1. Verify the Commvault Version
Verify that you are using Commvault Platform Release 2024 (11.34.13) or a more recent version.
2. Upload CommServe Disaster Recovery (DR) Backups on Commvault Cloud
Verify that the Commvault CommServe DR backups are uploaded to Commvault Cloud.
3. Access Cloud Command
Verify that you are able to access Commvault Cloud.
4. Verify Auxiliary Copies on Air Gap Protect
- Verify that auxiliary copy jobs on Air Gap Protect are not fallen behind and at least one full backup is completed and hosted in Cleanroom to perform recovery.
- Verify the jobs available inside the Air Gap Protect copy and ensure that there is at least one full backup per VM.
- Verify that the Air Gap Protect region and the Cleanroom target region are the same.
For more information, see the following topics:
5. Create a Cleanroom Hypervisor
While this task can be done in the Cleanroom using the recovered control plane, every time Cleanroom spins up it should be repeated. To stay prepared in advance, create the Cleanroom Hypervisor(s) on the production Control Plane (CommServe).
6. Enable Auto-Scaling for Access Nodes
While this task can be done in the Cleanroom using the recovered Control Plane, every time Cleanroom spins up it should be repeated. To stay prepared in advance, enable auto-scaling for Azure access nodes in the production Control Plane (CommServe).
7. Create a Cleanroom Recovery Target
While this task can be performed in the Cleanroom using the recovered Control Plane, every time the Cleanroom spins up, you must repeat this step. To stay prepared in advance, create the Cleanroom targets on the production Control Plane (CommServe).
8. Create Cleanroom Recovery Groups
While this task can be performed in the Cleanroom using the recovered Control Plane, every time the Cleanroom spins up, you must repeat this step. To stay prepared in advance, create the Cleanroom recovery group(s) on the production Control Plane (CommServe).
9. Consistent Backups
For VMs with databases, configure pre-scripts or application-aware backups for consistent backups.
For more information, see the following topics:
- Configuring Pre- and Post-Processing Scripts Using VMware Tools
- Pre-Process and Post-Process Scripts for Google Cloud Platform
- Performing Pre-Freeze and Post-Thaw Processing Using Nutanix Guest Tools
- Application-Aware Backups
10. Control Plane (CommServe) DR Backups on Commvault Cloud
Log on to Commvault Cloud with your credentials and verify that the latest Control Plane (CommServe) DR Backups are uploaded.