How to edit jobs with migration to new vCenter Server v5?

[nbarsotti]

I am going to replace my current vCenter Server v4 with a new vCenter Server v5 without doing an upgrade so I can move to the new vCenter Server Appliance. It will be a fresh clean install of vCenter v5. Once I register my ESXi hosts to the new server and remove them from the the old vCenter server how do I edit my replication and backup jobs so that they use the new vcenter server without the job thinking it is a totally new vm and needing to backup a full copy?

[Vitaliy S.]

Hello Nick,

In order to re-use replication and backup jobs, VMs should the receive the same moref IDs once they are registered in the vCenter inventory. That is not possible to achieve without upgrading the existing version of vCenter Server. You may want to re-use the same database where all the IDs are stored during vSphere 5 installation, but if you install it from scratch that is not going to work.

Hope this helps.

[nbarsotti]

hmmm. I was afraid of that. I am running vCenter Server v4 on a Windows XP 64 bit computer with the built-in SQL database, Even if I wanted to upgrade the Windows installation I would need to setup a new machine with a server version of the OS and then do a migration to a new SQL server. There is no upgrade path for the new vCenter Server Appliance that I am aware of at all. It seems like I might just have to bite the bullet and re-seed the replication.

Can anyone else think of another option?

[Bunce]

One option is for veeam to introduce a 'mapping' facility that would alleviate this and a number of other issues, by mapping vm identifiers to veeam's identifiers.

[mike.freestone]

Veeam does not currently work with Vcenter 5, will not recognise datastores. Unless Veeam have fixed this in the past 2 days.

[cstringer]

Please let me know if there is any update which fixes this, I am in the same boat...

[Vitaliy S.]

We will provide official statement on vSphere 5 support shortly (as soon as our QC completes full regressive testing of vSphere 5 RTM code), until then we strongly recommend staying on vSphere 4 as per System Requirements for the current product version.

[simon617]

LOOK FORWARD TO THAT!

[jcmachadouga]

Any update on this ?

[Vitaliy S.]

For all updates regarding vSphere 5 support, please look at this topic: vSphere 5