Skip to content

Commvault Migration Path — Validation & Checklist ​

Validation steps for each migration hop and the complete pre-migration checklist.


Hop 1 Validation — Hyper-V Staging ​

After the Commvault restore, validate each VM before proceeding to Azure Migrate:

CheckCommand / MethodExpected Result
VM bootsHyper-V Manager — check VM stateRunning
Network connectivityping <gateway> from VMSuccessful
IP address correctipconfig /all / ip addrMatches expected (or new IP if re-IPed)
DNS resolutionnslookup <hostname>Resolves correctly
AD domain membershipTest-ComputerSecureChannelTrue
Services runningGet-Service / systemctl statusExpected services active
Application smoke testBrowser / curl / DB queryExpected response
Disk integrityEvent Viewer / dmesgNo disk errors

Hop 2 Validation — Azure Local ​

After Azure Migrate cutover, repeat all Hop 1 checks plus:

CheckMethodExpected Result
Azure Local VM statusAzure portal -> Azure Local -> VMsConnected
Azure Monitor agentAzure portal -> Monitor -> AgentsReporting
Defender for CloudAzure portal -> DefenderVM visible, no critical alerts
Update ManagerAzure portal -> Update ManagerVM inventoried
DNS (if re-IPed)nslookup <hostname> from multiple clientsResolves to correct IP
Application sign-offApp owner full functional testPass

Rollback Decision Points ​

StageRollback Action
After restore to Hyper-V — validation failsPower off restored VMs -> power source Nutanix VMs back on
After Azure Migrate test migration — issues foundClean up test VMs; source VMs still safe on Nutanix
After Azure Migrate cutover — issues foundPower source Nutanix VMs back on while target issues are remediated

CAUTION

Never delete source VMs until holding period expires Maintain source Nutanix VMs powered off for at least 2-4 weeks after Azure Local validation. Only decommission after the holding period.


Pre-Migration Checklist ​

ItemStatusOwnerNotes
Commvault release and module support confirmed☐InfraValidate AHV or ESXi workflow
Commvault control plane healthy☐InfraNo service degradation
Media or worker components sized for batch☐InfraThroughput confirmed
Commvault storage target tested☐InfraCapacity available
Hyper-V staging target provisioned☐InfraStorage and switch mapping verified
Restore workflow validated in pilot☐InfraOne representative VM completed end-to-end
Re-IP procedure prepared and tested☐InfraOnly if staging subnet differs
Azure Migrate project created☐CloudSubscription and RG selected
Azure Migrate appliance deployed and registered☐CloudDiscovery complete
Azure Local cluster healthy and integrated☐InfraCSV capacity available
Network ports open between all components☐NetworkingSee prerequisites table
VM inventory sorted into batches☐Migration LeadBatch spreadsheet complete
IP and VLAN mapping complete☐NetworkingSource to target for all VMs
Application baselines documented☐App OwnersServices and smoke tests captured
Rollback procedure tested☐AllSource VM power-on verified

Released under the MIT License.