Discussions specific to the VMware vSphere hypervisor
Post Reply
micahvm
Novice
Posts: 4
Liked: never
Joined: Dec 20, 2012 4:43 pm
Full Name: Micah Van Maanen
Contact:

Switching from AppAssure to Veeam

Post by micahvm » Mar 05, 2013 4:48 pm

We are switching from AppAssure to Veeam and I would like to get everyone's thoughts on how we should implement our backup plan.

We have:
2 Dell R710 Servers running ESXi 5.1 (SD Cards) connected to a Dell Equallogic PS4000XV
25 VMs using 3.4 TB of disk space
Promise VessRAID iSCSI SAN for backups (5 TB available)

The two Dell servers are sized so that each can run the entire environment. But I don't have an ideal solution in place for dealing with a dead/corrupted SAN.

So my thoughts are this:
  • Install Veeam in a virtual machine or two
  • Install 4 - 3 TB Hard drives (RAID 10) in one of our ESXi hosts
  • Run the replication jobs to this DAS nightly
  • Run the backup jobs to the Promise SAN, we have a few VMs that I would like to backup hourly
  • Replicate the backup jobs to our remote site which is connected via fiber
If I go this route, should I have a separate proxy VM for the backup or replication jobs? Which backup type should I use? Any other recommendations?

Yuki
Veeam ProPartner
Posts: 252
Liked: 26 times
Joined: Apr 05, 2011 11:44 pm
Contact:

Re: Switching from AppAssure to Veeam

Post by Yuki » Mar 05, 2013 9:43 pm 2 people like this post

Hardware wise you should be ok.

The only solution to running your production systems if SAN dies - is to have another storage system (local, DAS, SAN, NAS). You could run from backups, but that will be slow. Here is how i would setup your systems:

- Virtual Veeam server with 4-8 vCPU and about 8GB RAM
- Install NL SAS drives in RAID 10 and configure
- schedule replication from SAN to local storage on server hourly (if your systems are fast enough, if not - then 2 hours or whatever schedule fits your environment)
- schedule daily backup to Promise (reverse incremental) and maybe a second to remote site via fiber. If you want to run only one job - then forward incremental to promise with active full on a weekend and rsync to remote site.

You want another proxy at remote site if you are replicating your systems to a server there (another virtual host) or if you have NAS for storage...

micahvm
Novice
Posts: 4
Liked: never
Joined: Dec 20, 2012 4:43 pm
Full Name: Micah Van Maanen
Contact:

Re: Switching from AppAssure to Veeam

Post by micahvm » Mar 06, 2013 3:01 pm

Yuki,
Thanks for the reply. That's exactly what I was looking for.

yizhar
Service Provider
Posts: 179
Liked: 48 times
Joined: Sep 03, 2012 5:28 am
Full Name: Yizhar Hurwitz
Contact:

Re: Switching from AppAssure to Veeam

Post by yizhar » Mar 10, 2013 9:45 pm

HI.

I recommend a physical backup server instead of virtual.
You can use additional virutal proxy server but better have the backup system on a standalone host that you can have immediate access to in case of problem with production system (storage, san netwrok, vm hosts).

Installing DAS disks on the esxi hosts in such environment is always a good idea IMHO, and you can use them in several ways for backup,
testing, and other uses.
I would go with RAID 5 in favor of capacity vs performance.

Regarding replica of the backup - how did you plan to achieve it?
If possible, I suggest running backup job directly over the Fiber, instead of replication the backup.
Create different backup jobs for local and remote backups.

Yizhar

Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests