itlv2015 wrote:1. Could you explain a little why the Wan Accelerator placement isn't a big deal for my situation?
You should set up a pair of WAN accelerators, one per each location so that they could transfer data efficiently between them. Actual location of WAN accelerator within the site does not really matter, it just should be placed somewhere near the storage.
itlv2015 wrote:2. Wow what a great thought, we never really thought your method of taking stress off the production storage. So I can understand fully, I currently do a daily backup job from production server to "Main Site Nas" just like you said. After that I am currently running a "backup copy" to the datacenter NAS. How can I tell if the backup copy job is pulling data from the production server or if it's just copying the data from Main site NAS and syncing that over the WAN?
Backup copy job always uses backup files as a source, it does not touch production VMs.
itlv2015 wrote:If I take your suggestion and do a "backup copy" job from On-site NAS to backup ESX server, how do I actually turn on the VM's on the backup server if the main server fails? It's my understanding that you do your recovery through the Veeam server user interface, which if the host is down then my Veeam server is also down. I think this is where I keep getting stuck in this situation.
A common practice is to make a second Veeam B&R installation located at the DR host/location responsible for replication jobs. This will allow for automatic failover in case main instance is down. Alternatively, you can perform manual failover (just start the VMs using vSphere Client).