At this current time the cause is unknown. currently under investigation is the impact of:

• Available memory in the Backup Exec server
• Specification of CPU in the Backup Exec server
• Amount of individual items/files stored within the Sharepoint content database
• Security policies/restrictions within Sharepoint

WORKAROUND:
Restore the whole of the content database, as a redirect restore, to another SQL instance and then extract the data directly - see https://www.veritas.com/docs/000017640 for more detail on this process.


Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.
 
This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see https://www.veritas.com.
 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
 
NOTE:
Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.

After running Granular Recovery Technology (GRT) enabled backups of Sharepoint data, if a restore of some of the GRT data is attempted then the restore operation can be seen to take a considerable amount of time depending on how many individual items (files) were being restored.

Issue was reported against Sharepoint 2013 but may affect other versions