pufferdude wrote:What is the best practice for backing up a vCenter VM with Veeam? Based on other topics here it looks like you should not point the job at the vCenter and then select the VM, but instead point directly at the host the vCenter is running on. However, this seems like it would make it necessary to manually edit the job every time you happen to vMotion the vCenter VM to another host. Is this correct, and just a fact of life using veeam to back up the vCenter, or am I missing something obvious that would let the vCenter move around and veeam could still find it?
We are just looking into our vCenter backup again after moving to vSphere 4.1.
Could you not create multiple vss jobs for each server that vCenter could vMotion or DRS to?
Each night 1 backup should succeed and the others fail, no matter which server the vCenter is on
When restoring you just choose the latest file (or can you point multiple veeam jobs at the same file?)
Worst case seems to me is that you could have multiple backup files for vCenter (but it tends to be pretty small anyway? At least it is for us - 12 hosts)
J.Leeflang wrote:I don't know if it is possible to use the incremental and/or deduplication function because of a change of VMID, but I rather see a properly backup of my vCenter with an extra use of diskspace than a non-consistant backup with less diskspace.
Users browsing this forum: No registered users and 12 guests