Error Message

RequeueStorageQueueFailedItems

Failed to requeue item:

       File:           S:\EVStorageQueue\Failed Items\EVStorageQueue_16D9B399746C65541B5ACD9A6932B91121210000SiteName_20190329032050_10226_20771B7D9CD99576D2E3025243E8D3C1.DVS
      Archive Id:     (null)
      Transaction Id: (null)
      Error:          %1 already exists.  (0x80030050)

GNI

EV:L CLogFile::Write - [ ERROR: Failed to read file into Saveset2 object. Error: %1 already exists.  (0x80030050) ]

The error status reported can be misleading as it reports generic error statuses.

When attempting to decipher the error condition based on the returned error statuses it is important to break down the different sections of the reported statuses.

With the error reported when executing the Repair option RequeueStorageQueueFailedItems, although the error code (0x80030050) is followed by '%1 already exists', looking at the other reported fields, the main status is 'Failed to requeue item', and the additional metadata shows:

Archive Id:     (null)
Transaction Id: (null)

These combined statuses suggest that the metadata information in the content could not be read.

Looking at what is returned when using GNI (GetNativeItem), the error statuses returned when exporting the original content from the DVS shows the same error ' %1 already exists.  (0x80030050), but the main returned status is 'Failed to read file into Saveset2 object.' 

Here it can be concluded that the content cannot be read, again suggesting that the content may be in a corrupt state.

Using internal tools to open the affected DVS file it is possible to see that the file content is filled with zeroes, where a 'healthy' DVS file shows binary data. 

Healthy DVS

Corrupt DVS

In the event items in the Storage Queue FailedItems folder are found to be corrupt and cannot be reprocessed or ingested, please contact Veritas Technical Support for assistance.

Note: In order to prevent any possibility of Data Loss it is very important to configure the Safety Copies using the recommended settings. The Enterprise Vault Installing and Configuring guide describes the Safety Copies settings in detail.

When configuring the Vault Store Safety Copies option within the VAC (Vault Administration Console), if the setting 'No, remove immediately after archiving' is selected, a Warning is shown highlighting the risks when using this option.

With FSA (File System Archiving), if the Safety Copies option is set with the value to remove the safety copy Immediately after archiving, the original item will be deleted and/or replaced by a shortcut, depending on the Policy configuration. If there are issues processing the archived content from the Storage Queue and ingesting into the Storage Partition, there is a risk of data loss as the original items would no longer exist.

The archived content added to Storage Queue files will be retried in case ingestion into Storage fails, however after a number of retries the content will be moved into the FailedItems folder.

EVSVR provides an option to reprocess content from the FailedItems folder, however, if the content is in a corrupt state the Storage processing will not be able to ingest the items and the original content has to be restored from a Backup.