Backups will fail on a content database, indicating an access denied error. If Granular Recovery Technology (GRT) is disabled, the backups will complete successfully.
Completed status: Failed
Final error: 0xe0001602 - Access is denied (SharePoint backup).
Final error category: Security Errors
For additional information regarding this error refer to link V-79-57344-5634
From an SGMon log with "Job Engine, RAWS and Agent Browser" enabled on the media server:
BEREMOTE: [03/20/14 11:46:59]  2014-03-20T11:46:59.213 [fsys\spsv2\spsv2grb - Initialization failed
BEREMOTE: [03/20/14 11:46:59]  2014-03-20T11:46:59.218 [ndmp\loops] - BACKUP_LP_ENV::AttachToDLE() failed to attach to (null). Reason
BEREMOTE: [03/20/14 11:46:59]  2014-03-20T11:46:59.218 [ndmp\loops] - LP_ENV::MsgError: error 0xe0008488 processing object <Unknown>
Data within particular content databases causes an unexpected condition in the GRT indexing process, and returns the access denied error.
Within the SharePoint Backup definition, disable Granular Recovery Technology (GRT).
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. 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 Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.
This issue has been observed within SharePoint 2010 SP1 environments with SQL 2012 backend.