Items stored on Hitachi Content Platform cannot be retrieved by StorageCrawler for indexing

Problem

When using a partition on a Hitachi Content Platform (HCP) storage device, the root path is a configurable setting that specifies the location of the partition directory on the device. If the value configured for the root path exceeds 37 characters, then items stored to it will be unretrievable by Enterprise Vault.

Error Message

This manifests itself most obviously and immediately by errors from the StorageCrawler process as it attempts to supply the items for indexing.

Event Type: Error
Event Category: Storage Crawler 
Event ID: 28944
Description: The 3rd party storage system application 'Hitachi Content Platform (HCP) Streamer' has logged the following message:

CStreamerObject::Read method failed
Reason = 0x80070002
ConnectionManager::Set_Curl_Operation method http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice
/94618370CEA1E545AFDF5186F1604A8E/2012/May/03/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28
Reason = 404 : Not Found - opr_GETConnectionManager::Set_Curl_Operation method http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice
/94618370CEA1E545AFDF5186F1604A8E/2012/May/03/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28
Reason = 404 : Not Found - opr_GET



Event Type: Error
Event Category: Storage Crawler 
Event ID: 7083
Description: Retrieval of saveset failed.
Archive Id: 17309ED17DCB9B746931C1521D361D5061110000EVMBX01 Transaction Id: F0ECD449CD75B30B7FDCD645018E5691 Extended information: The system cannot find the file specified. (0x80070002) Internal Ref: Vault/RI
V-437-7083

As a result of the high number of failed items, indexes may be marked as failed.

Cause

This is caused by a character limit on a SQL column used by Enterprise Vault to store the URL to the savesets' storage location on the HCP. A root path longer than 37 characters will cause the URL to the item to exceed the column's limit, and the URL will be written truncated. The items are stored properly on the device, but when Enterprise Vault attempts to read their location, the truncated URL is invalid and the item appears unavailable.
 

Example of a properly formed URL:
http://HCPStorage.mydomain.com/rest/ShortRootPathName
/94618370CEA1E545AFDF5186F1604A8E/2012/May/03
/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28_21/00001

Example of a truncated URL:
http://HCPStorage.mydomain.com/rest/VeryLongRootPathNameForHitachiTestDevice
/94618370CEA1E545AFDF5186F1604A8E/2012/May/03
/7fd197f7-f12c-44ab-8653-0752c49f8b01/23_28

(The examples above are shown with artificial line breaks inserted for readability.)

Workaround

A workaround for this issue is to configure the HCP partition with a short root path (under 37 characters). This will prevent new items from being archived with the overlong URL and being truncated in the database.

If items have already been archived with the truncated URLs, then it is necessary to correct the erroneous entries. Please contact Enterprise Vault Technical Support to assist with this procedure.

Solution

This issue has been addressed in Enterprise Vault 9.0.5 and 10.0.3 and higher