-
- Expert
- Posts: 103
- Liked: 3 times
- Joined: Sep 13, 2017 11:12 am
- Full Name: Tore Mejlænder-Larsen
- Contact:
New vCenter
Hi.
We had a crach on one vcenter - and we installed a new vcenter - and moved all servers to this.
If we now connect to the new vcenter from the Veeam server - and remove the old servers (from the old vcenter) and add the one from the new vcenter.
Will Veeam then create a new full backup - or will it manage to use the existing backup and continue from there.
There has not been running backup for one month - so there is a big gap in the data.
Tore
We had a crach on one vcenter - and we installed a new vcenter - and moved all servers to this.
If we now connect to the new vcenter from the Veeam server - and remove the old servers (from the old vcenter) and add the one from the new vcenter.
Will Veeam then create a new full backup - or will it manage to use the existing backup and continue from there.
There has not been running backup for one month - so there is a big gap in the data.
Tore
-
- Veeam Software
- Posts: 688
- Liked: 150 times
- Joined: Jan 22, 2015 2:39 pm
- Full Name: Stefan Renner
- Location: Germany
- Contact:
Re: New vCenter
Hi Tore
as soon as VMs are moved to a new Vcenter, the Managed Object Reference ID (MoRef ID) of the VM will change. And that’s the Id we use to identify the VM. So in your case, if you don’t modify those IDs, a new full backup will be created.
Thanks
as soon as VMs are moved to a new Vcenter, the Managed Object Reference ID (MoRef ID) of the VM will change. And that’s the Id we use to identify the VM. So in your case, if you don’t modify those IDs, a new full backup will be created.
Thanks
Stefan Renner
Veeam PMA
Veeam PMA
-
- Product Manager
- Posts: 14840
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: New vCenter
Hello,
yes - new VCenter means new IDs in the background. We use the managed object reference ID (MoRefID) instead of the name... because a VM could be renamed easily
There are (unsupported) ways to continue with the backups. Forum search for MoRefID brings for example this thread
Best regards,
Hannes
yes - new VCenter means new IDs in the background. We use the managed object reference ID (MoRefID) instead of the name... because a VM could be renamed easily
There are (unsupported) ways to continue with the backups. Forum search for MoRefID brings for example this thread
Best regards,
Hannes
-
- Veeam Legend
- Posts: 822
- Liked: 128 times
- Joined: May 11, 2018 8:42 am
- Contact:
-
- Veeam Vanguard
- Posts: 636
- Liked: 154 times
- Joined: Aug 13, 2014 6:03 pm
- Full Name: Chris Childerhose
- Location: Toronto, ON
- Contact:
Re: New vCenter
That utility mentioned in the KB link works extremely well but you need to have run this prior to removing the old vCenter from Veeam VBR so that it could get the IDs from it before moving to the new vCenter.
-----------------------
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
-
- Product Manager
- Posts: 14840
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: New vCenter
ah thanks - in my memory, the migration tool required that the old VCenter still exists (which is not the case here)
Who is online
Users browsing this forum: No registered users and 71 guests