Limitations and conditions for restores that use SharePoint Granular Recovery Technology (GRT)
The following limitations and conditions exist for jobs using Granular Recovery Technology (GRT):
The feature is limited to certain versions of SharePoint Server and Windows Server. See the Software Compatibility List (CL) and the Application/Database Agent Compatibility List.
This feature only supports full and user-directed backups. NetBackup lets you create a complete policy for disaster recovery, with all the various types of schedules. However, you cannot restore individual items from an incremental backup.
NetBackup does not support Granular Recovery Technology (GRT) with Microsoft SharePoint Server backups in a multi-tenant SharePoint environment.
Backups must be made to a disk storage unit, not to tape, and restores that use GRT must be made from a disk storage unit. You can manually duplicate the backup image to disk, but you cannot restore from the tape copy.
See Disk storage units supported with SharePoint Granular Recovery Technology (GRT).
Backups with GRT do not support any content databases that exist on multiple servers in a farm.
Granular Recovery with Remote BLOB Storage providers is not supported; however, you can backup and restore the entire farm or databases. Refer to the following TechNote.
When you perform a granular recovery of documents, pictures, or list items that are part of a workflow, the state of these items is not preserved.
NetBackup does not support backups and restores with GRT if you use a third-party document management software to manage your SharePoint documents. For example, NextDocs.
Granular recovery of the Central Administration website and the Shared Services Administration website is not supported.
(SharePoint 2016) If you edit the title of a list item, SharePoint creates a new version for those list items. When you select all list item versions for restore, NetBackup creates a new list item for only those versions whose title is different than the original list item title. As a workaround, restore the list.
(SharePoint 2016) If the list item version you selected for restore has a different title than the original list item title and the is also enabled, the restore job fails with an error message. As a workaround, restore the list.
(SharePoint 2016) When you use Granular Recovery Technology (GRT) to restore ghosted or uncustomized aspx pages from any template, the restore job is successful, but the restored pages appear with the default content when it was created. This issue is not seen if the aspx pages are uploaded to SharePoint. Such pages are treated as customized pages.
To work around this issue, restore the SharePoint web application content database. See Redirecting the restore of a SharePoint Server Web application content database to an alternate SQL instance.
(SharePoint 2013 and later) For backups that use GRT, a redirected restore to a file system is not supported.
(SharePoint 2013 and later) The Restore GRT Basic Meeting Workspace shows errors when you restore even though the restore completed.
(SharePoint 2013) The following site templates are not supported with SharePoint restores that use GRT:
Product Catalog
Community Site
(SharePoint 2010 and 2013) If you perform a restore with Granular Recovery Technology (GRT), any SharePoint user ratings and tags are synchronized to the current settings of the user rating and tags in the respective metadata databases.
(SharePoint 2010 and 2013) Dependent items of blog posts (including comments and images) are not restored with restores that use Granular Recovery Technology (GRT).
(SharePoint 2010 and 2013) When you restore a list item from a localized subsite, the job is reported as successful. However the list item fails to appear in the SharePoint user interface. To work around this issue, restore the item to a file system and upload the item to SharePoint.