Consider the following when restoring SharePoint environments:
| • | Free space equivalent to twice the size of the backup is required on the local share for restore processing. If adequate space is not available, the restore fails. |
| • | Restores are performed to the original farm only. |
| • | Full catastrophic farm recovery can only be performed for SharePoint 2013 and 2010 deployments where the installation type is single server. For full farm (all SharePoint releases) or single server farm (SharePoint 2016) installations, you must recover items instead. To check your installation type, see To determine the installation type for SharePoint 2013 and 2010 deployments. |
| • | Granular recovery of farm items is supported on both single-server and multi-server farms through the use of a Windows or another third-party tool. Granular recovery can be performed from full backups only. |
| • | For a restore to succeed, all nodes in the farm must be online and available. |
| • | Only one restore or backup operation per farm can run at any given time. |
| • | For a given farm, any backups initiated while a restore is in progress will fail. Once the restore completes, backups can be run for the farm. |
| • | For a given farm, any restores initiated while a backup is in progress will fail. Once the backup completes, restores can be run for the farm. |
| • | For granular, item-level restores, the backup is unfolded to a local system share. From here you can restore items using a Windows or third-party tool. When you are finished restoring, you must tear down the share. Subsequent backup or restore operations for the given farm will fail until the restore share has been torn down. |