Hi
We have several ESX servers that are connected to vCenter using IP adress. We now need to change these to FQDN so they will be disconnected and then connected again using FQDN. All VM's are using tags to be incroporated in Veeam backup jobs so they wil ldo a new Full when the job starts.
Is there any way to "fool" Veeam so we can continue the current backup chain?
The problem is:
- A new Full bakcup will create a new chain taking up a lot of storage on local repositories
- A new Full will aslso mean a full copy over slow WAN links
//Mats
-
- Expert
- Posts: 170
- Liked: 15 times
- Joined: Apr 20, 2018 8:12 am
- Full Name: Mats Holm
- Contact:
-
- VP, Product Management
- Posts: 27375
- Liked: 2799 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Effect on Backup and copy when change of ESX from IP to FQDN?
Hi Mats,
If you re-register VMs in the virtual infrastructure, they will receive a new moref ID, thus full backup will be created. As a workaround, you can migrate VMs from one host to another, rename the host, add it back and migrate VMs (via vCenter Server functionality) to the original location.
Thanks!
If you re-register VMs in the virtual infrastructure, they will receive a new moref ID, thus full backup will be created. As a workaround, you can migrate VMs from one host to another, rename the host, add it back and migrate VMs (via vCenter Server functionality) to the original location.
Thanks!
Who is online
Users browsing this forum: No registered users and 100 guests