1. Support
  2. Knowledge base
  3. 100020293

Important Update: Cohesity Products Knowledge Base Articles

All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.

Event ID 6510: Archive operation canceled because Saveset file is missing

Article: 100020293
Last Published: 2015-04-01
Ratings: 0 0
Product(s): Enterprise Vault

Problem

Errors are reported after an Enterprise Vault (EV) Vault Store Partition location has been changed and Saveset files have been moved to the new location.

When an Enterprise Vault (EV) Vault Store is configured to "Remove Safety copies: After Backup" the WatchFile table of the Vault Store database is used to track Saveset files in Vault Store Partitions that need to be backed up.  The records in the WatchFile table contain the path and file name for Saveset files (.DVS files). Changing the Vault Store Partition location and moving Saveset files to the new location while there are associated records in the WatchFile table will cause Event ID 6510 errors to be reported because the path referenced in the WatchFile table is not dynamically updated.  Refer to the 'Related Documents' section of this article for more information on changing Vault Store Partition locations.

Error Message

Archive operation canceled because Saveset file is missing.
[Vault Store: First Partition]
[Vault ID: 43T6Y5DEEB3CC0408395AABB97A970611110000ACMEVAULT]
[Saveset Filename: E:\Enterprise Vault Stores\ZKO\2003\04\18\00\313000000000000~200304180015030000~0.DVS]
[Transaction ID: 5921E4E294894B97BA52B
 

Event ID 6510: "Archive operation canceled because Saveset file is missing"
V-437-6510

Solution

Solution 1:
When the only change made to the Vault Store Partition location is the drive letter, the following query can be used to update the records in the WatchFile table for Enterprise Vault 9.0.0 and earlier.

Warning:  This Procedure should NOT be run against Enterprise Vault version 9.0.1 and later.
Warning: This procedure involves making changes to the Vault Store SQL database and should be carried out by person(s) familiar with Microsoft SQL Server. Please ensure that a valid FULL backup of the Vault Store database exists prior to making these changes.

USE EVVaultstoreDB
Update WatchFile
SET Itemname = 'X' + right(Itemname, len(Itemname)-1)

*Note: Replace 'EVVaultstoreDB' with the actual name of the Vault Store database.  Use the actual drive letter for new Vault Store Partition location, in place of X.


Solution 2:
When the records in the WatchFile table cannot be updated the following steps can be performed to cancel archiving and clear the records from the table.

1. Confirm that all Saveset files were moved to the new Vault Store Partition location.
2. Stop the Enterprise Vault Storage and Task Controller Services.
3.Purge the following MSMQ's:
EV Exchange Mailbox Task Queues (A2-A5)
EV Exchange Journaling Task Queues (J2-J4)
All Enterprise Vault Admin Queues
Refer to the 'Related Documents' section of this article for more information on purging MSMQ's
4. Change the Policy setting "Pending shortcut timeout" to a number corresponding to the days since the Vault Store Partition location was changed.  For example, if the partition location was changed 2 days ago, set the value to 2.  Refer to the 'Related Documents' section of this article for more information on the Pending shortcut timeout policy setting.
5. Start the Enterprise Vault Storage and Task Controller Services.
6. Change the Policy setting "Pending shortcut timeout" back to its original value.
 

 

Was this content helpful?

Article Languages