![]() Here’s how it works:ĭue to this architecture, it is necessary to schedule full backups periodically. Thus, if you configure CloudBerry Backup to keep 3 versions of a file, the backup will only start purging data beginning with the fourth full version of the file. In CloudBerry Backup, a single incremental block is considered a version. You can also enable and manage default retention policies directly from the Backup Wizard.Ī block-level backup feature allows you to upload only the parts of files that have changed since the last backup, instead of uploading whole files.įurther reading Block-Level Backup Explained If your retention policy can be standardized and you want it to be enabled for all backup plans by default, go to Tools - Options - Retention Policy. Note that the default retention policy applies to backup plans in the legacy backup format only We recommend using this option in conjunction with the parameter Delay purge for (described above), just to add extra protection Create Default Retention Policy ![]() ![]() This option helps free up storage space and simplifies the management of large backup datasets. ![]() If a file was deleted from the dataset, it will be deleted from your cloud backup storage location automatically during the next run of the CloudBerry Backup. This option allows CloudBerry Backup to purge unnecessary files from the backup storage. It’s another safety lock for your backup strategyįurther reading Delay Purge – What Is It and Should I Use It? Delete Files That Have Been Deleted Locally Use the Delay purge for option to give yourself extra time to review files that are scheduled to be purged. You can do so by simply choosing Keep number of versions and setting the desired number of copies. For example, information on a website might be rarely updated, but you still want to track its history to prevent data loss or a sudden malware attack. It is especially convenient for data that is rarely updated. This setting is useful when you need to configure a policy without a specific date. This option allows you to set a limit on the number of versions of a file that you retain. It acts as a safety lock and prevents the loss of the last version of your data, even if that version is out-of-date according to the policy settings Keep Number of Versions You can check the box Always keep the last version. This parameter of the retention policy settings allows you to delete all file versions that were created before a certain date (day, week, month and year can be chosen), based on the initial backup or last modification date of your files. Please note that the retention policy feature also applies to MSP360 Managed Backup. To get a clear understanding of those choices, select any backup plan, click Edit Backup Plan, and enable Advanced Backup Mode to configure custom retention policy settings on the corresponding step of the backup plan wizard. ![]() All user files are accompanied by a list of their previous versions in the backup system.Īll of the Retention Policy options are available in the backup plan settings you choose. We track each version of each file that was created and give you full control over it. You can create several versions of a file during its lifespan accordingly to your security settings. In CloudBerry Backup, we call each copy of a single file a version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |