We use paid Veeam B&R v12.x (VUL/Essentials) to back up NetApp ONTAP SMB/NFS to a local repo and are evaluating off-site immutable copies via SOBR + S3/Wasabi/Azure (Object Lock) vs Cloud Connect (VCSP). What’s your real-world take on job layout (per-share vs per-volume), snapshots, NAS proxies, performance and €/TB/month, plus restore/ACL fidelity, cross-protocol restores, and immutability/lifecycle gotchas? Any proven tuning or pitfalls to avoid?
+21Don't do much NAS backup myself but here a few links to help with things one of them being Wasabi too.
https://helpcenter.veeam.com/docs/backup/vsphere/unstructured_data_backup.html?ver=120
https://docs.wasabi.com/docs/how-do-i-use-veeam-v12-nas-backup-with-wasabi
+3Immutability/lifecycle gotchas - do not enable lifecycle on the repository side - Veeam doesn’t support it, it can lead to data corruption.
When it comes to SOBR - capacity and archive tiers are not supported for NAS jobs, so the way to offload if to specify a secondary destination in the main job, or archival in the main backup job as well. With secondary destination you will have an identical copy, with archival, only older versions of the files will be offloaded.
Per-share, per volume - here, I guess, it will depend on the storage vendor, if the share is huge, it might be needed to be split into several jobs.
Snapshots and nas proxies shouldn’t affect much cloud jobs, so to use the same approach as on-prem, I think.
Performance should be slow for most cloud options, unless a dedicated link is provided. But I think it should be fine to restore some files, and not an entire share.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.