We’ve decided to repurpose one of our large Synology boxes (RS3617xs+) and put some big drives to get us adequate storage space. On the bottom layer, the Synology FS will be BTRFS. We will create an iSCSI LUN on said FS, XYZ TB in size, mounted to a Linux VM formatted XFS for both immutability and fast block cloning for synthetic fulls.
My question here how do I make sure I’m getting THE BEST compression and deduplication ratios out there from the Veeam side. I assume also “per-vm” repos fit in here as well? If not doing “per-vm” repos, more blocks will be deduped in this scenario than in a “per-vm” repo. This is so we get the best “usage” from our storage and lasts us for some time.
Then there’s this article: Data Compression and Deduplication - User Guide for VMware vSphere (veeam.com)
Another question, does data compression happen after deduplication?
Data Compression
For backup jobs - I assume the default “Optimal” would fit most scenarios. The more compression, the more resources are needed for the job and the longer restores would take.
For backup copy - The article recommends “Auto” which again I assume would fit most scenarios.
Deduplication
The article explains to have Veeam Data Movers on both source and target sides. Assumption, the data movers are the Veeam proxies? We only have two proxies in our local datacenter and two more, one each in our remote datacenters. Will this setup suffice? One of the remote sites, we’re transferring data over wireless links which essentially would be like moving it over WAN.
Since the device we’re storing data to is a NAS (not a SAN or DAS or local storage) even though we’re presenting the iSCSI LUN as a disk to the Linux VM, we would choose 512KB block over 1MB (default?) therefore giving us smaller output files.
Let me know what you think about my above statement. Also if there’s anything you would do differently or recommend in addition to above.
Thanks as always.