Veeam Design

[kevinbugg1982]

We have recently had a near miss with our backup copy data due to a raid issue which got me thinking about the overall design of our veeam setup.

We have a production environment running on Cisco Hyperflex which hosts approx 17TB data which we backup fully each day to a local repository using reverse incremental. The local repository can handle 17.5tb but with Veeam compression etc we can handle about 8-10 restore points / daily's before space becomes tight. We then use Backup Copy to send that data to another office which then has 32 retentions and 12 monthlys. We then take that device offline and retain for 7 years (required) then start again with a new device. Our recent near miss meant that we nearly lost our last 12 months worth of data.

Problem no.1 - Our Hyperflex / local backup currently runs at 1gb due to an issue that is being investigated. If run over 10gb it saturates the network and makes the production vm's unresponsive. - resolvable
Problem no.2 - We can lose up to 1 years worth of data / recovery if the backup copy device has an issue either through veeam corruption or device failure - concerned but resolvable im sure

We have 2 sites each connected either via a 200mb mpls or 1gb P2P so data transmission shouldnt be an issue or locations to copy data too. My concerns are data volumes and corruption / device failure.

How would others design the topology and configure veeam to work optimal to ensure data protection is there but not going over the top.

Any design gurus out there are welcome to assist! or do you agree with our design

Thanks in advance
Kev

[foggy]

Hi Kevin, just a couple of thoughts, since overall your setup looks good. First, consider introducing a third copy of backups, and second, use periodic health checks to ensure backup validity.