G'day fellow Community "Hub-sters"! On the Weekly Recap a couple weeks ago,
After thinking about what he said for a bit, I thought it would be fun, and thought-provoking, to provide a bit of a twist to his suggestion. What twist did I think of? To not (initially) share what my environment looks like, but rather provide what resources I have in my environment, then ask you, the Community, how you would best implement Veeam using those resources. From a high-level, I'll share capital and operational items. Then based off what's already in place (can't add other OP/CAP expenditures), you can provide a high-level design. This is just for fun only…so have fun with it. 😊
After a few days or so, I'll share how I've implemented Veeam with the same resources
Physical Environment
- 2 datacenters, DC1 (main site) and DC2 (DR site)
Virtual Environment:
- vSphere virtual environment; 1 vCenter Server
- 2 vSphere Datacenter Sites, DC1 and DC2
- Mixture of Windows and Ubuntu Linux VMs
Compute
- Newer hardware hosts for production; legacy hardware hosts for DR
Network:
- Layer 2 Gigabit fiber connection between sites
- Isolated Gigabit fiber connection between sites solely used for storage traffic
SLAs
- Core services – AD services, DNS, DHCP, vCenter
- Critical data – less than 1hr
- Important data – less than 4hrs
- Secondary data – 24-48hrs
Storage:
- 4 total Hybrid Flash Nimble arrays
- iSCSI protocol
- No available Cloud storage solutions
Backup Resources:
- Veeam B&R Enterprise Plus licensing
- 1 newer DELL R740 physical server
- 2 legacy HP DL380p physical servers
There you go. How would you implement Veeam given the resources above? I created this in the Discussion Board because I hope many great design discussions/comments will come from this - best practices, gotchas, things forgotten, etc.