Phase 5 – Testing and Tuning
So running the Veeam job, we can see that we are only writing backup data to a local SMB share so, in theory, it should complete successfully just like any other normal job.
We can monitor the status of CloudSync from the Synology management interface, unfortunately, the status/progress information offered in CloudSync appears to be quite limited. The status/progress appears to be either, in-progress or completed.
Below is the incomplete summary, note: no progress or detail regarding the amount of data remaining to be uploaded.
We can, however, see a history of completed files.
For those interested, this is how it looks when it is up to date.
I recommend configuring scheduling to avoid syncing during backup job operations.
The first test of the backup job resulted in the Synology Cloud Sync uploading files that were still being written to by Veeam, this is an issue because these have been uploaded before Veeam has finished with them, meaning the file is likely incomplete or corrupt. Because of this we need to schedule CloudSync not to upload until after the backup job is completed.
Some parameters we can look at to improve the performance would be the Part Size, as covered earlier in this article, we can increase the size on reliable links to improve performance. However, this should be set low if your link experiences frequent disconnects to avoid having to upload large amounts of data from scratch again.
Traffic throttling can also be configured by defining the max upload and download rate in KB/s.
Browsing files in B2
Browsing and retrieving files is as simple as you would expect with your typical object storage service, files can be browsed via the web interface and file versioning can be easily accessed.
Creating snapshots of files and folders in B2 adds an extra level of protection against ransomware. In the example below, I have selected the folder created by Veeam for the backup job and initiated a B2 snapshot. I’ve searched high and low through the web interface but I couldn’t find a way to schedule the snaphots, I’m confident they can be triggered through scripts leveraging the APIs though.
What is cool though is that snapshots can be retrieved using several options, either by download, USB Flash Drive or even a USB Hard Drive. It’s always useful to have extra options for recovery large amounts of data especially if WAN links are slow.
File Lifecycle Management
Because of the way Backblaze B2 works, when a file is uploaded more than once to the same bucket, Backblaze B2 automatically creates a version of the file. Due to the way Veeam works, we will find that the backup job .VBM files are created quite often, you will often see the .VBM reach any arbitrary version controls you have in place well before your incremental or full backup files reach the version limit.
We have tested and tuned your buckets, congratulations, on to the summary.