@NashBrydges said in Leveraging Veeam Cloud Tier - Backups To Wasabi:

@wrx7m said in Leveraging Veeam Cloud Tier - Backups To Wasabi:

I upload Veeam backups to Wasabi (and before that, S3) outside of Veeam. I pull down the backups and import them back into Veeam, via the import feature.

I would like to see how well it works when everything is natively done in Veeam. If that is even possible.

How do you upload your backups to Wasabi? Are you using a 3rd party tool?

Yeah. I use a file compare tool called, BeyondCompare that runs on a windows task schedule.

Veeam DOES recommended avoiding low end NAS devices, and recommends SAN over NAS because Veeam wants block protocols. These parts are true and we don't need to watch videos as they are available in writing from @Rick-Vanover - we even have the author of the best practices here in the community!

https://www.veeam.com/blog/vmware-backup-repository-configuration-best-practices.html

0_1501712220659_Screenshot from 2017-08-02 17-16-46.png

The keys here are "low end" which is an issue around support. The misleading bit is that NAS means server, so low end servers are every bit affected in the same ways. The QNAP, Synology, ReadyNAS and other such devices are not actually NAS but Unified Storage, SAN as much as NAS. That Veeam recommends SAN instead of NAS is a protocol choice, it does not make those devices any less applicable. We should not be calling them NAS, as that is misleading, they are equally both.

If we really look at the guidance and consider what it could mean, the only real concern is "low end" and low end is always of some concern. Why spend so much on Veeam and Windows licensing and then get cheap on the hardware? You want solid storage hardware and solid support. But nothing here is telling us that there is anything wrong at all with these kinds of devices and certainly the issue is not some kind of corruption caused by the fact that they are in this product category.