VM moved to new vCenter

[leduke]

Hello.

I'm using a Veeam back server and a vSphere Cluster with 3 nodes, the veeam backup server has discovered the VMs managed by the vCenter.
I will perform an upgrade of the vSphere infrastructure. I will install a new vCenter server (because an inplace migration is not supported, actually the vCenter is a 36bit server)... So ... Must I recreat the job or complete a brand new backups of my virtual machine after they will be moved ?

Thank you.

[dellock6]

If the jobs you created are saving the same VMs even once they are moved to the new vCenter, you can use "map backups" to use the restore points you already created.

Luca.

[leduke]

OK !

thanks, it already OK if the new host is in upgraded to vSphere 4.1 ?

Thank you.

[dellock6]

Yes, you can register both the "new" ESXi server and the vCenter, as always.
Luca.

[foggy]

If the jobs you created are saving the same VMs even once they are moved to the new vCenter, you can use "map backups" to use the restore points you already created.

Alex, you will have to re-add VMs to the jobs as their moref ID's will change after registering in new vCenter. Veeam B&R tracks the VMs by their ID's, not names, and will not be able to locate them by their old identifiers. Once you've done this, please map the VMs into existing backup files/replica VMs.

[dellock6]

Yes, sorry for my too fast reply, re-reading it sounds confusing, I meant "if the NEW job" is recreated then... thanks Alexander for clarification

[leduke]

Alex, you will have to re-add VMs to the jobs as their moref ID's will change after registering in new vCenter. Veeam B&R tracks the VMs by their ID's, not names, and will not be able to locate them by their old identifiers. Once you've done this, please map the VMs into existing backup files/replica VMs.

Ok, so first is it better to delete the VMs from the existing job, migrate VMs and then re-add the VM to the jobs with new ID ?


thank you all

[foggy]

No matter when you remove the old VMs - before or after the migration. Note, that you cannot have a job with no VMs in it.

[Cokovic]

Sure you can. If you choose an empty folder or datastore

[foggy]

Sure you can. If you choose an empty folder or datastore

Then actually no need to change the job in the case of a new vCenter (if VMs are added through container and you have the same container in the new one).

[Cokovic]

Thats true. Just a joke

[leduke]

It's OK for me !

I add the new vCenter and edit the backup Jobs, remove the virtual machines and re-add them by choosing the new vCenter !

Thank you all !

[gvinpin]

[merged]

I have moved all hosts to a new VC, and was expecting to get errors because of unique ID, so I have re-added VM's.
Now I am getting "The object has already been deleted..." message.
I really do not want to re-create jobs as we have ~150 of them.
Are any quick ways of fixing this?

[Vitaliy S.]

Could you please clarify where do you see this message? Do you have both vCenter Servers added to the backup console?

[gvinpin]

I see it as a error message in a backup job statistic window "3/07/2012 10:05:18 PM :: The object has already been deleted or has not been completely created"
Yes, both VC's are in backup console.
After I have moved host with VM's to new VC, backups were failing with "Object XXXXX not found".
I have edited jobs and deleted servers it could not see and re-added it inside the job.