once the primary site comes back up you will have to re replicate the VMs back to primary using the primary site vms as seeds (if it isnt a total loss). You can fail over manually - ive tested this thoroughly, but its not ideal - bc you would lose all restore points after you consolidate the replica disk at the DR site and they will no longer be tracked by veeam. trust me, running veeam and ALSO vcenter out of the dr site is the way to go. you can install as many instances of veeam without licensing issues bc its not tied to installs. if you lose the DR site you can restore the config at the primary site and start running from there.
Install two instances of veeam one at the primary site and one at the DR site, but run everything out of the DR site and back up the configuration. Additional Veeam licensing required (or not - Can someone answer this?) Pros, Failover can be done almost immediately.Ĭons, 2 "Brains and one body" for Veeam proxy and Veeam Repository services running on the PROD Veeam server - or another proxy server in PROD is required, also the possibility of backup jobs running at the same time as replication jobs and causing failure of either. Have Replication jobs running from DR Veeam server all the time and just start failover from there. Pros, Only one license required (or can we use the same rental license in DR to replicate VM's licensed in PROD?), Only one server is controlling the proxy and repository services on the PROD Veeam server.Ĭons, Another manual step is required at failover time.Ģ.
If failover is required, restore Config backup of PROD Veeam server to DR Veeam server and start failover plans. Have replication jobs run in PROD Veeam server. Setting up replication jobs now and I have thought of 2 options:ġ. We backup many VM's in PROD and we want to replicate some to DR. We have VCenter high availability so all Vmware DataCenters are under 1 vCenter. We have a PROD Veeam server (physical & uses SAN snaps) and a standby DR Veeam Server in a DR site (VM).
0 kommentar(er)
