About troubleshooting SharePoint restore operations
Note the following when you perform restores:
NetBackup does not prevent you from restoring placeholders.
NetBackup lets you restore any object that can hold a document, even it does not contain a document.
The following issues also exist for SharePoint:
For a SharePoint survey list, after a restore the "Time Created" value reflects the value at the time of the granular restore. This behavior is by design.
If you restore a deleted report, the report ID is incremented upon restore. If you want to maintain the original report ID value, restore the entire report container.
In SharePoint 2016 and later, if you select the entire report container for restore, the report IDs post restore are not from the original set and new IDs are created.
NetBackup does not start a GRT restore job from a UNIX NetBackup primary server. Initiate the restore job from the SharePoint client under which the backup is cataloged.
If you use a SQL Server local RBS provider and want to take a SharePoint data backup, then you must create a file system policy for file-level backups of SharePoint databases on the SQL Server.
You can use this backup for database level restores (full and differential)
When you restore a web application a new application pool is created for each restore. The original application also remains and can be deleted.
See Figure: New application pool after a web application restore.
