We use Veeam in a Hyper-V environment, writing backups to local storage and sending copy jobs to the cloud. We also have replication to a disaster recovery site. I'd like to make better use of our older Veeam host hardware by adding another layer of backup protection, following the 3-2-1 approach. The concern is that if the Veeam server or repository has a hardware or disk failure, new backup and replication jobs stop. We recently lost about a week of protection because of drive corruption on the Veeam server. What would you recommend: a second backup product, another repository, or a different architecture? Our servers are business-critical and change frequently, so losing a week of data would be unacceptable. We currently test backups monthly.
2 Answers
If you specifically want a second vendor, products such as Acronis, Datto, or a managed disaster-recovery service can provide an independent path. Use separate storage and schedules, and verify that the product supports Hyper-V, immutable retention, and test boot or recovery. I’d choose this only if you have a clearly defined gap that Veeam cannot cover, rather than simply duplicating every job.
Before adding software, identify whether the real issue is repository availability, the backup server, or the backup chain. A second product can mean two management systems, separate support contracts, and possible contention for snapshots or changed-block tracking. Weekly restore verification and regular recovery tests may provide more value than installing a competing tool.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures