Meaning when we leverage B2 using Cloud Sync, we should find that backup files avoid any versioning, this includes. This results in essentially a unique file for each restore point for each job created by that Veeam BnR server. When a Veeam backup job runs, it creates a backup file based on the following properties, %JOBNAME%,%DATE%,%TIME%. ‘Days Till Delete’ defines how long to keep that file version until it is deleted.‘Days Till Hide’ defines how long to keep file versions that are not the current version.U sing the B2 lifecycle settings we can define our online retention outside of Veeam for how long we wish to keep our backup files in the bucket regardless if they have been overwritten or deleted from the Veeam repository. These ‘hidden’ files are simply the older version of a file that has been replaced by a newer copy. File versions are be automatically hidden whenever a newer file with the same name is uploaded. Using the B2 lifecycle rule, we can define how long we wish to keep file versions that are not the current version. You can tell if the same file has been uploaded multiple times a (2) or any other number closely follows at the end of the file name when browsing files via the B2 web interface. By default, each Backblaze B2 bucket will keep all versions of all files forever, this is not a bad strategy but you may end up paying for storing backup data outside your retention requirements.īecause of the way Backblaze B2 works, when the same file is uploaded more than once to the same bucket, Backblaze B2 automatically keep both versions of the file but will “hide” any older versions from the B2 Web GUI.
0 kommentar(er)
