We're a small org with 3 hosts in our primary site and 2 in another (20ish VMs). We're using ESXI essentials, so no vMotion or anything and all host rely on local storage. We have multiple hosts to mitigate long downtimes, but management is not investing in super lower RTOs. With that in mind, each host is big enough to support other VMs if needed and the plan for host failure is to restore VMs to a different host until the problem is fixed or the server is replaced.
Well, we had a host go down yesterday and included in its VMs was our primary Veeam backup server. The host recovered and we didn't need to move VMs, but I realized I had not planned well for no access to the primary backup server. We backup the Veeam config daily to separate storage, so I had that but if I'm honest I'm not sure what to do with it. We have our 'primary' Veeam VM at our primary site, and a proxy in our DR site. We back up VMs local to their site and send backup copies to the remote site.
If I lose the primary backup VM, what do I need to do? Install Veeam somewhere else, restore the Veeam backup file, then start restoring VMs? Can I setup a secondary Veeam server that already has access to jobs and what not on it to avoid extra work during an already flustering time?
We're using Veeam Backup and Replication and I have plans to replicate servers between hosts, so they're all more readily available if we lose a host. However, I'm not sure how that works if the primary Veeam server is not available either. Same scenario or can VMware manage the replica (power it on)?
Not trying to re-invent the wheel here just some help to better understand how I should manage my backup servers in the event it is lost. Thanks in advance.