Discussions specific to the VMware vSphere hypervisor
Post Reply
rlewin
Novice
Posts: 4
Liked: 1 time
Joined: Mar 16, 2015 3:28 pm
Full Name: Rick Lewin
Contact:

Deployment Advice

Post by rlewin » Mar 29, 2017 2:26 pm

I'm deploying Veeam in our environment and am looking for some advice. My environment consists of two data centers that are less than two miles apart. These data centers are well connected with fiber SAN and 10G ethernet. I have a single VSphere cluster, consisting of two hosts at each site and SAN storage at each site. VMs that are stored at site A have an affinity to run on the hosts at site A and a similar setup for VMs at site B. I also have separate SAN storage for Veeam repositories at both site A and site B. This storage is not presented to VMware (not on the HCL). There are currently about 100 VMs and 25TB of data. I'm trying to setup Veeam so that if one of the data centers were to go down, I could restore essential machines to the other data center. Here is my deployment thoughts and I was hoping to get some feedback / ideas.

The Veeam server itself would be a VM. The database would sit on a separate SQL server (VM). Each site would have a physical proxy server running Server 2016 with a ReFS repository on the repository SAN storage at that site. VMs that are housed at site A will be backed up to a repository at site B and vice versa for site B.

First, does this scenario make sense? Does it fit my design criteria? Is there a better design? What happens if the VM that is the Veeam server is running at the data center that goes down?

TIA,

Rick

foggy
Veeam Software
Posts: 18789
Liked: 1650 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Deployment Advice

Post by foggy » Mar 29, 2017 3:12 pm

Hi Rick. Basically, your design answers your requirements. In case the site with the Veeam B&R instance dies, you will be able to fire up another Veeam B&R, import Veeam B&R configuration (you're going to back it up, right?) and perform necessary restores. However, for faster recovery, you could set up two instances (one per site) making cross backups (or replication, for even faster automatic failover) from another site (pull scenario). Also, keeping some short retention of local backups for operational restores is always recommended.

rlewin
Novice
Posts: 4
Liked: 1 time
Joined: Mar 16, 2015 3:28 pm
Full Name: Rick Lewin
Contact:

Re: Deployment Advice

Post by rlewin » Mar 29, 2017 8:39 pm

I hadn't considered running two servers but it totally makes sense. I came up with a slight variation of this idea. What if I presented the SAN that is going to be used for the repositories to VMware and virtualize the entire thing: virtual Veeam servers and virtual proxies? My ESXi hosts use so little of the CPU that it shouldn't be and issue.

foggy
Veeam Software
Posts: 18789
Liked: 1650 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Deployment Advice

Post by foggy » Mar 30, 2017 11:28 am

Virtual Veeam B&R servers and virtual proxies are totally possible, but storing backups inside a VM is not recommended.

rlewin
Novice
Posts: 4
Liked: 1 time
Joined: Mar 16, 2015 3:28 pm
Full Name: Rick Lewin
Contact:

Re: Deployment Advice

Post by rlewin » Mar 30, 2017 3:43 pm

Thanks again for the advice.

DaveWatkins
Expert
Posts: 355
Liked: 95 times
Joined: Dec 13, 2015 11:33 pm
Contact:

Re: Deployment Advice

Post by DaveWatkins » Apr 02, 2017 8:50 pm

You could also replicate the B&R server VM from site to site so if the worst does happen, you can just power up the replica

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 23 guests