Cross vCenter vMotion

[kirk]

Hi, I have some questions about migration between different vCenters.

[Prerequisites.]
- Ihave two vCenters with different SSO domains.
- Veeam Backup is already connected to each vCenter.
- I have a vSphere Enterprise Plus license, which supports Advanced Cross vCenter vMotion.
- The two vCenter Servers share the same LUN on the same storage.[/list]

[Purpose]
- I want to migrate virtual machines between different vCenter Servers with no downtime.
- I want to migrate virtual machines with Veeam backup chain and backup jobs inherited.

[What I know]
- I want to migrate between different vCenter Servers with no downtime.

[What I want to know]
1. Can the backup chain and backup jobs be taken over by using Veeam's migration function? (Whether reconfiguration is necessary or not)
2. What is the expected downtime of virtual machines by using Veeam's migration function?


I would like to know if there are any other references that would be helpful.

Thank you in advance.

Translated with DeepL.com (free version)

[PetrM]

Hello and Welcome to Veeam R&D Forums!

Veeam uses the native vMotion mechanisms whenever possible, and according to the information provided on this page, hot migration of VMs across different vCenter server systems is supported. Based on this, I would not anticipate any downtime. However, it is strongly advised to test this in your specific environment. I recommend attempting to migrate a few test VMs to assess the process and its outcome.

Regarding your question 1, migrating backup jobs and chains is not possible. When a VM is migrated to a different vCenter, it becomes a completely new object from Veeam's perspective. Consequently, it requires the creation of a new job and backup for that VM.

Thanks!