Moved server from 1 host to another

[brichardson1991_obk]

We had a server located on host 2 that was backed up daily (tue-sat - 01:30) and a weekly backup - weekend (sat - 07:30)

We have moved this server from host 2 to host 8

Will there be any problems with the backups tonight after we have moved it? Do we need to do anything with Veeam B&R for it to see the move?

[PTide]

Hi,

If you used a vCenter for that migration then everything will be ok. Any operations involving reregistering a VM (i.e. delete-restore) will change its morefID therefore the VM will be treated as a new one causing full backup instead of incremental.

[brichardson1991_obk]

So even if it was stored on a SAN and managed via vcenter and we removed it and re-added it from one host to the new host it will need a full backup?

[PTide]

So even if it was stored on a SAN and we removed it and re-added it from one host to the new host it will need a full backup?

Since you removed (thus unregistered) its morefID has changed, so yes, the initial run is going to be full. If you need to move some VMs to another host/vCenter in future please contact support team prior to doing that - they can help preserving morefID.

Thank you.

[brichardson1991_obk]

Would this still be the case if we had migrated it?

Just been informed that we migrated it instead of remove/re-add

[PTide]

In case you've migrated the VM with vSphere migration then morefIDs should have stayed intact. If you used Veeam for migration with "Force Veeam quick migration option" enabled then full backup is going to happen.

[brichardson1991_obk]

We used vsphere migration.

Thanks for your input Pavel, very helpful.

[brichardson1991_obk]

Is there any way to check that this will definitely backup and only do the changes without manually starting the job?

[PTide]

Hi,

Sorry for the delay.

If the VM's ID has not changed during the migration then everything will be fine, no full will be preformed. You can check if VM's id after migration matches the one stored in Veeam's database. First, you obtain Id from Veeam:

Code: Select all

#Get all objects from "Backup Job Name" job
PS C:\Users\PTide> $objects=GetVBRJobObject("Backup Job Name")
#List objects' properties including refid
PS C:\Users\PTide> $objects.GetObject()

Info               : Veeam.Backup.Model.CDbObjectInfo
Id                 : 8f6a6260-3a67-465b-875d-a23a1304cc8f
Name               : VM1
ObjectId           : vm-1414
HostId             : 1b74d34d-ec31-4ce3-bbe8-44a90cd92e22
GuestInfo          : Veeam.Backup.Model.CGuestInfo
Uuid               : 42082727-aced-c67a-bf2e-fc9a572b2dca
Type               : VM
Platform           : EVmware
FaultToleranceType : None
Host               : Veeam.Backup.Core.Common.CHost
ViType             : VirtualMachine
ObjectRef          : vm-1414

Info               : Veeam.Backup.Model.CDbObjectInfo
Id                 : 0640bf11-d28f-47f2-8f2a-058454d5087d
Name               : VM2
ObjectId           : vm-1417
HostId             : 1b74d34d-ec31-4ce3-bbe8-44a90cd92e22
GuestInfo          : Veeam.Backup.Model.CGuestInfo
Uuid               : 4208c1c6-72e2-9364-7091-4a5ae87f84a7
Type               : VM
Platform           : EVmware
FaultToleranceType : None
Host               : Veeam.Backup.Core.Common.CHost
ViType             : VirtualMachine
ObjectRef          : vm-1417


PS C:\Users\PTide>

You need ObjectRef. Let's pick vm-1417, VM2

Next, you connect to your vCenter via PowerCLI:

Code: Select all

PowerCLI C:\> Connect-VIServer vcenter.domain.local -User domain\Ptide
PowerCLI C:\> Get-VM | ft -Property Name,ID -AutoSize

VM9                                      VirtualMachine-vm-100
VM2                                      VirtualMachine-vm-1417
VM12                                     VirtualMachine-vm-1155
VM122                                    VirtualMachine-vm-1051
VM123                                    VirtualMachine-vm-1238
VM124                                    VirtualMachine-vm-1236

If reference IDs match then Veeam will recognize the VM that has been moved.

[brichardson1991_obk]

Hi Pavel,

We didn't see a full job run so it worked as we expected.