synthetic full backup<\/a>\u201d feature for image-based backup. Based on our test result we can save up to 90% of public traffic by reusing the existing data in the S3 Cloud as a data source for new backups. This option is available due to an internal copy command (AWS API) and smart comparison mechanisms. We\u2019ve developed an intelligent approach of comparing data blocks from the source computer with existing revisions and data blocks in the cloud storage. If identical blocks are found, we perform an internal copy process (within a Cloud). Lastly, internal cloud block management provides 20x times faster performance, which guarantees 20x times faster full backups.<\/p>\nIf you\u2019re using synthetic backup with Amazon S3 Standard-IA storage class, bear in mind one proviso regarding the pricing policy. When you initiate the second full back-up, the principal part of those files will be copied within the cloud itself. And you will be charged accordingly \u2014 $0.01\/GB.<\/p>\n
Note: Synthetic full is currently only available for Amazon S3 storage<\/p>\n
Force Full Backup<\/h2>\n
In the previous version changing the encryption options in the backup plan (setting\/revoking\/changing encryption password) may cause problems. Let\u2019s say you have a number of files backed up. Then you modify some files, change the encryption options and run backup again. What encryption option do you need now to restore all files? Actually, you will need to run the restore process twice to get all of them. Essentially, if you use a new encryption password, it will restore files changed since the last backup only. To restore the rest of files, you will need to use your old encryption password. First, it is inconvenient to run the restore process twice. Second, you may have a hard time recalling your old encryption password.<\/p>\n
Therefore, we are happy to introduce the \u201cForce Full Backup\u201d feature, which will help you avoid these problems. Now when you change the encryption options, the following pop-up window will appear asking if you want to backup all your files selected in the backup plan using your new encryption password;<\/p>\n
![\"screenshot_6\"](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2016\/10\/Screenshot_6.png\")
<\/p>\n
By clicking the \u201cYes\u201d all files in the backup plan will be backed up again with new encryption password. The restore job with new password will decrypt and restore all files. So you don\u2019t need to run restore twice. Now you have an option to restore all files by running a single restore job with a new password using this feature. No need to remember your old encryption password either.<\/p>\n
<>Pause \/ Resume Backup<\/strong><\/h2>\n
In the previous version there was no option to pause\/ resume backup. You could only stop a backup plan and run it again . When you start the plan you had to wait for the process to scan all files again and identify new and modified files. This process may be lengthy depending on the number of files.<\/p>\n
In this release we\u2019ve added an option to put backup and restore plans on pause and resume them without file system rescanning. Now you don\u2019t have to waste your time and wait for the rescan process to complete.<\/p>\n
![\"screenshot_8\"](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2016\/10\/Screenshot_8.png\")
<\/p>\n
\n
Featured Product<\/h2>\n
You can try MSP360 Backup 5.2 with all new features absolutely for free! Just go ahead and download 15-days fully functional trial version of MSP360 Backup and check if our backup solution meets your needs and requirements.<\/p>\n","protected":false},"excerpt":{"rendered":"
The new MSP360 Backup 5.2 has been released! We\u2019ve added the following features: Item-level recovery for Microsoft Exchange Azure VM restore using temporary instance Synthetic full backup Force full backup option Pause and resume backup and restore plans Let\u2019s take a look at these new features.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[877,894,882],"tags":[],"class_list":["post-15641","post","type-post","status-publish","format-standard","hentry","category-blog-articles","category-msp360-backup","category-msp360-news"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/15641","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/comments?post=15641"}],"version-history":[{"count":1,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/15641\/revisions"}],"predecessor-version":[{"id":56814,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/15641\/revisions\/56814"}],"wp:attachment":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/media?parent=15641"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/categories?post=15641"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/tags?post=15641"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Exchange](\"https:\/\/www.msp360.com\/resources\/wp-content\/uploads\/2016\/10\/Screenshot_21.png\")
<\/p>\n