Backup of Deduplication Storage folder via shadow copy components to tape fails with "A failure occurred reading an object"
Error in Job Log:
V-79-57344-65247 - A failure occurred reading an object.
Exec Deduplication Storage\Storage" is a corrupt file. This file cannot verify.
Error in the SGMON debug Log:
PVLSVR: [10/15/13 09:53:13]  10/15/13 09:53:13.274
PvlEntityDatabase::UpdateEntity() : SUCCESS!
BEREMOTE: [10/15/13 09:53:13]  2013-10-15T09:53:13.319
[fsys\shadow] - Status FS_STREAM_CORRUPT (0xE000FE36) for Component
Storage in SHADOW::ReadComponent
BENGINE: [10/15/13 09:53:13]  2013-10-15T09:53:13.347
[server] - BackupJob::Failed was called for BSD '\\Servername\Shadow?Copy?Components'
BENGINE: [10/15/13 09:53:13]  2013-10-15T09:53:13.355
[server] - BackupJob::Failed was called for BSD '\\ServerName\Shadow?Copy?Components'
BEREMOTE: [10/15/13 09:53:15]  2013-10-15T09:53:14.640
[fsys\shadow] - Informational: Closing Component 'Storage'
BEREMOTE: [10/15/13 09:53:15]  2013-10-15T09:53:14.655
[fsys\shadow] - Informational: calling
IVssBackupComponents::SetBackupSucceeded with status
'FS_READING_OBJECT_FAILURE (0xE000FEDF)' for Component 'Deduplication Storage'
CauseThe VSS Snapshot may get deleted due to high IO when Deduplication Storage folder starts to process queue. It may happen that some backups are also running during the time when Deduplication Folder is being backed up and can add to the I/O load on the system.
Best Practices while Backing up a Deduplication Folder via Shadow Copy Components :
•Reduce the system or I/O load and retry the operation, or schedule other operations during the least busy periods.
While backing up the Deduplication Storage Folder if there are backups running to it and queue processing starts to run on Dedupe folder, it will increase the IO Load. To reduce I/O backup Jobs targeted
to Deduplication Storage Folder can be run at a different time when the backup of Deduplication Storage Folder is not running.
•If necessary, refer Microsoft documentation to move the shadow copy storage area (also called the "diff area") to a volume with more storage capacity.
If the above 2 recommendations do not help, please contact Technical Support.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section 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.