GENERAL ERROR: Storage Delete Error. Event ID 6761 with description" Clip CDF is not found in pool"
|Article:TECH138907|||||Created: 2010-09-01|||||Updated: 2010-09-03|||||Article URL http://www.symantec.com/docs/TECH138907|
The "Storage Delete" function logs errors regarding opening clips for data that is eligible for deletion.
Event ID: 6761 Error opening EMC Centera C-Clip |Function call: NetworkPacket.checkControl(2) <HPPReadBlobTransaction.readBytes(HPPImportData&)<HPPReadBlobTransaction.run()<ClusterCloud::readBlob (FPBasicGenericStream*,**********************,,0,-1,-1,0)<FPClip::Open(pool, *****************, 1)<FPClip_Open (-,************************) |Status: FP_CLIP_NOT_FOUND_ERR (-10021) |Reason: Clip CDF is not found in the pool (transid='XXXXXXX/111/READ_CLIP') |Pool Address: xxx.xxx.xxx.xxx?\\XXXXXXX\c$\Program Files (x86)\ Enterprise Vault\PEAFiles\XX_XX.pea |
Enterprise Vault 8 SP3
Rarely, this situation could occur if the deletion process for the item concerned did not complete successfully on a previous Storage Delete run. The reasons for this not completing could be network issues, servers going offline or any other issues in the environment that could interrupt the deletion process. The item concerned is removed from Storage (Centera) however the saveset record is not removed from the relevant Enterprise Vault tables in SQL.
Workaround: Confirm that the data as per the Event Log does no longer exist on Storage (Centera). Enterprise Vault ships with a utility named EVSVR that can help determine and confirm what records exist in the Enterprise Vault Databases, that has no associated data on Storage (Centera). The option for this is "Verify" - "Archive Objects" - "Verify that the
CAB, Saveset, SISPart file or CLIP exists" in EVSVR. To delete the orphaned records from the Enterprise Vault SQL database you the "Repair" - "DeleteSurplusReferences" option. As this tool makes changes to the Enterprise Vault SQL. See EVSVR documentation contained within the Enterprise Vault Utilities Guide for more details on running this utility.
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 being considered by Symantec Corporation to be addressed in the next major revision of the product. There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com/
Article URL http://www.symantec.com/docs/TECH138907