Skip to main content
commvault.com commvault.com
Answer

Migration vCenter from windows based to an appliance

  • June 23, 2022
  • 5 replies
  • 177 views
L
Novice
Forum|alt.badge.img

As a new user of Commvault we would like to rely on your experience.

We are planning to upgrade our vCenter from a windows based vCenter version 6.5 to an appliance with version 7.0u3. The plan is to do an in-place upgrade of the vCenter, name and IP-details stay the same.
As the vCenter will change OS from windows to Linux based, The Commserve could see the vCenter as a new client. 

We would like to know if this update can trigger a Full backup on all VM's in this vCenter..? 

Hopefully some one has done this before and knows the impact.
 

Best answer by LeonM

Thanks for all your quick answers, that gives us more confidence to proceed with the upgrade.

We moved some some hosts to a different vCenter, which triggered a Full backup on all VM's running on this host, with a new created backupset on each client. We are using a cloud based setup of Commvault in Azure, so a full backup causes very high usage on the main WAN link to Azure. Which slows down the daily bakups. This worried us with the upgrade of the vCenter in mind. 

 

5 replies

Aplynx
Vaulter
Forum|alt.badge.img+12
  • AplynxVaulter
  • Vaulter
  • June 23, 2022

I would recommend running a full after changing the out to the appliance to make sure nothing is missed.

Liam
DMowers
Vaulter
Forum|alt.badge.img+3
  • DMowersVaulter
  • Vaulter
  • June 23, 2022

Here is some documentation in regards to your question(s):

https://documentation.commvault.com/commvault/v11_sp16/article?p=32032.htm

Also here is some additional information on VM Centric operations:

https://documentation.commvault.com/11.26/essential/114216_vm_centric_operations_in_command_center.html

 

Have a good day

Dwayne

P
Certified Expert
Forum|alt.badge.img+7

Hello, 

as long the vcentername is the same as before you should not run in any issues and if the vcenter name changes it is also not a problem, you can change this easy in the vsa client. 

 

Hope this helps you !

 

Onno van den Berg
Community All Star
Forum|alt.badge.img+22

This should definitely not trigger a full backup of all your VM's on the next backup after the upgrade. As long as the upgrade path is supported and the metadata remains the same you should be good to go! 

L
Novice
Forum|alt.badge.img
  • LeonMNovice
  • Author
  • Novice
  • Answer
  • June 24, 2022

Thanks for all your quick answers, that gives us more confidence to proceed with the upgrade.

We moved some some hosts to a different vCenter, which triggered a Full backup on all VM's running on this host, with a new created backupset on each client. We are using a cloud based setup of Commvault in Azure, so a full backup causes very high usage on the main WAN link to Azure. Which slows down the daily bakups. This worried us with the upgrade of the vCenter in mind. 

 

Terms & ConditionsCookie settingsAccessibility statement