- 4-VM Hosts (1tb total RAM, 20c/host)
- 170tb Compellent SC8000 3-Tier array
- Dell DR4100 (not currently used for Veeam)
- Veeam B&R Enterprise
Currently I have three backup jobs:
- Job 1 - 43VMs at 12tb total -- daily Forward Incremental w/weekly Synthetics
- Job 2 - 22 VMs at 19tb total (mainly databases) -- 6-hour Reverse Incremental
- Job 3 - 5 VMS at 1tb total -- daily Forward Incremental
All use High compression and WAN Target for storage optimzation to get as much dedupe as possible; my OS break down is about 90% 2012r2, 10% 2008r2 so I realize some substantial dedupe savings per job.
We moved from vRanger to Veeam in a bit of a rush, so our vRanger data is/was on a DR4100 (36tb raw), so I have this setup for Veeam:
- Host 1 - VeeamCore Server/Repository-1 (for Job 2 and 3) that also acts as a Proxy for that host
- Host 2 - Proxy and Repository-2 (for job 1 data) - two different servers
- Host 3 - Proxy
- Host 4 - Proxy
The Repositories are using RDM to my spindle tier on my Compellent - the 1st and 2nd are all SSD - and all servers are running 2016 Datacenter, utilizing ReFS for the repository drives. Full 2x10gb networking per host for data, and 2x10gb for iscsi. 80gb to Top of Rack (backup vlan is separate from host IPs so I THINK it goes to ToR during backups, not positive)
Performance thus far isn't bad, my Veeam systems just use a fair amount of CPU/RAM on my virtual hosts; each Proxy is 6c/5gb RAM and the Repo/Proxy/Veeam core is 8c/22gb, with another 4c/6gb to the 2nd Repo. I run 2016 Datacenter-Core for all but the main veeam server which helps a ton not having a full OS installed (but I'll give vRanger props for having virtual appliance proxies that can be provisioned from the vRanger client to your hosts)
Storage wise I'm not using all that much; with my current retention set of around three months, I'm actually only using 20tb for all 3 jobs, as ReFS and 9.5 is amaaaazing.
We've hit retention limit with the DR4100 so I can repurpose it fully and wipe it for Veeam, instead of hammering my SAN and iscsi network by running backups from/to itself (we're very well aware it's not best practice, but we had plenty of storage on the SC8000)
My question(s) is around best practices for larger environments on physical vs virtual, and whether it's best to dedicate a host to Veeam. My thoughts are these:
- Keep current Veeam architecture but move the Repositories onto CIFS share(s) on the DR4100 and leverage its dedupe/compression & Replication (I have an identical DR4100)
- Keep current Veeam Architecture and install 2016 on DR4100 hardware and use DAS or Storage Spaces to provide backup repository.
- Repurpose DR4100 hardware as a 5th host in my cluster and run a single Repo/Proxy off it, offloading all compute/storage from my production environment and leveraging the DAS 36tb - the DR4100 has Xeon procs and something like 48gb RAM, as it's basically an R720dx with a custom OS installation
I've gone over the user guides but there's very little information out there on sizing Veeam and what these best practices might be.
I'd love the communities input on this, or even pointing me at any documentation I have't seen that should answer this. I've only seen a few people use the DR4100's and there isn't much in terms of what i might expect on dedupe/compression using veeam. For vRanger and their RDS format, I was seeing ingest rates of 1GB/s and savings of 13x (90%) which was ridiculous. Unfortunately, vRanger itself is junk, and the DR4100 / vRanger combo had nearly constant issues with properly cleaning up dedupe data and applying retention policies, as vRanger actually used the DR4100 OS to handle the file management. It was horrible, to be honest. WHEN it worked, it was very nice. But it broke nearly every 2-3 months in some fashion.