We are planning to have an offsite backup disk as well at one of our remote location.
Which option is good:
Option 1:
Buy 2 identical NAS devices.
Use 1st one as onsite Veeam backup target
Use 2nd one as offsite Veeam backup target
Use the built in RSync feature of the NAS devices to copy backup files from onsite => offsite
Option 2:
Buy 2 identical NAS devices.
Use 1st one as onsite Veeam backup target
Use 2nd one as offsite Veeam backup target
Buy Veeam Enterprise Plus edition and use the WAN accelerator feature, so it can copy
backup files from onsite to offsite location
-
- Enthusiast
- Posts: 31
- Liked: never
- Joined: Jul 25, 2014 6:03 pm
- Full Name: V
- Contact:
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: NAS device RSync Vs. Veeam WAN acceleration
As always, it depends. In this case, mostly on your backup sizes and WAN bandwidth. Rsync is great for small files, but it really does not scale at all (simply was not build to handle large files). We've actually tested an enhanced variation of its algorithm for our WAN acceleration, but dropped it eventually. And bandwidth-wise, it will use a few times more than Veeam with WAN acceleration enabled. But again, both issues are irrelevant if you have small backup files and fat WAN pipe.
One other gotcha to keep in mind is that RSync will replicate corrupted data as well as it replicates good data (which is not the case with Backup Copy jobs). So if you go RSync route, be sure to schedule Backup Validator in the target site.
Also, schedule it very carefully not to overlap with backups or restores, because it's not integrated and is unaware of other Veeam activities (and neither Veeam expects anything to lock its backup files). Conflicts may cause job failures, data corruptions and so on. For example, Backup Copy jobs suspend when other jobs or activities need to access the copied backup files, then resume automatically.
Hope this helps.
One other gotcha to keep in mind is that RSync will replicate corrupted data as well as it replicates good data (which is not the case with Backup Copy jobs). So if you go RSync route, be sure to schedule Backup Validator in the target site.
Also, schedule it very carefully not to overlap with backups or restores, because it's not integrated and is unaware of other Veeam activities (and neither Veeam expects anything to lock its backup files). Conflicts may cause job failures, data corruptions and so on. For example, Backup Copy jobs suspend when other jobs or activities need to access the copied backup files, then resume automatically.
Hope this helps.
Who is online
Users browsing this forum: No registered users and 42 guests