It’s now very straightforward you only need to choose the timespan for which the backups should be kept.įurther reading Backup Retention Policy and Scheduling Best Practices Improved GUI We’ve simplified the mechanics of the retention policy step.
The new backup format allows you to make a record of backup processes to track operations and use these records for easier troubleshooting in the event that there are issues with backups. Also, in this version, there is no need to encrypt filenames, as all files are combined in archives. In the new backup format, you can use emojis, hexadecimal numbers, etc. Previous versions of CloudBerry Backup didn’t support certain characters.
#Cloudberry backup encryption full
Synthetic Full BackupĪnother key feature of the new backup format is that synthetic full backup will be available for all supported backup types (file-level, IBB, VMware), allowing you to leverage AWS, Microsoft Azure, Backblaze B2, and Wasabi cloud storage.įurther reading Synthetic Full Backup File Backup In CloudBerry Backup 7.0, backup plans are included in backup data. Previously, CloudBerry Backup enabled users to store backup configurations as a backup plan on a separate basis. This protects you from losing data (for example, when some of the files in your backup storage get corrupted, or when you replace your local NAS device storing the backup files). In the new backup format, we make sure that all files required for that restore point exist in backup storage. In previous versions of CloudBerry Backup, consistency checks could be run either manually or according to a schedule.
#Cloudberry backup encryption verification
If the checkbox is activated, it means that restore verification has passed. You can check the result of this operation on the backup storage tab. It works as follows: as soon as a backup is completed, an agent runs a temporary virtual machine to check machine resilience and ensure that this backup can be used as a restore point. Now, this can be done as soon as the backup has finished. Restore VerificationĪnother great feature of the new backup format is restore verification. Note that upload resume is now available for all backup types. Now, if a backup fails, data that has already been uploaded can be used on the next run. In previous versions of CloudBerry Backup, data had to be re-uploaded in the event that the backup was interrupted, and upload resume was available for IBB and file-level backups only. Deduplication is done directly on the client side, reducing both the amount of data sent to storage and the time needed for upload. The new backup format allows backup of deduplicated data to storage. It reduces incremental backup time significantly - for instance, from 1 hour to 5 minutes. The CloudBerry Backup 7.0 enhances the scanning process of image-based backups to speed up the backup process.
Note, to make use of the new backup format, you should create new backup plans. Keep reading to learn more about the new backup format’s features. This format supports compression, encryption, and additionally client-side deduplication. The new backup format is structured as a monolith block that combines all source files, machines, and volumes. It allows to speed up backup and recovery processes, deduplicate files, and so much more! Read on to learn more. It introduces a number of critical changes and updates with the most important of them all - the entirely new backup format. Here at MSP360, we are proud to announce the major release of the CloudBerry Backup version 7.0.
0 kommentar(er)
