Meaning lots of new files that would need to be synced, this is something we are trying to avoid.īy avoiding unnecessary full backup files it will help us minimise our storage bill and importantly ease congestion on the WAN link. With a backup job, we would need to consider that reverse incremental should not be used, leveraging reverse incremental would result in a new full backup file being created each time the backup runs, it also creates a new reverse incremental file for the previous restore point. With the above in mind, we need to decide whether we should configure backup job (primary backup target) or a backup copy job (secondary backup target). Veeam features such as Storage-Level Corruption Guard and Defrag/Compacting the full backup file should be avoided as this results in a new full backup file being created. The Synology CloudSync package is not aware of when the Veeam backup files are being created/modified by Veeam, this can result in files being uploaded before Veeam has finished, this happens a lot with.This is in contrast to other solutions such as Microsoft StorSimple which leverages a ‘volume-container’ global block-level dedupe which means even if Veeam sends multiple full backups files to a backup repository, the StorSimple will only upload changed/unique blocks due to its block-level dedupe capability.
0 Comments
Leave a Reply. |