This article describes the process for performing restores in Backupify/Datto SaaS Protection 2.0 for Office 365 and defines which account types can be used as the target of a restore.
- Backupify/Datto SaaS Protection 2.0 for Office 365
When restoring items, you can select a specific item (Figure 1) or multiple items (Figure 2) and restore them by clicking the Restore button.
You can also search through snapshots for specific users and select items from various points in time.
To change the snapshot date, click the date under Snapshot to the left of the search box and select an available date and time to search that specific snapshot instead (Figure 3).
After initiating a restore, you will see a prompt where you may select whether you would like to restore all the items in the snapshot or just the selected ones.
- Restoring a full snapshot is useful if a user deletes the entire contents of their mailbox, or in the event of a ransomware attack.
By default, the data will restore to the original owner's account, but you may choose any other user to restore to if you wish.
You can only restore to other accounts that are part of the same Office 365 tenant and which have been seated in Backupify/Datto SaaS Protection 2.0.
When the content restores, Backupify/Datto SaaS Protection will create a folder which uses the following naming convention: (Backupify Restore 2019-03-05 11;27;35). The folder will have the time and date of the restore, along with the name of the service. The reason we add a timestamp is so that current content doesn't get overwritten by restored items.
Restore Status Dashboard
You can check on the status of your restores for a particular service under the Restores tab. This view also acts as a complete audit log of your restores, since Backupify will never clear out this information.
In some cases our restore jobs experience issues, and we are not able to restore some of your records. Typically these are caused by transient issues communicating with Microsoft's APIs, internal Microsoft exceptions, or processing errors on the Backupify side.