Retrieval of items from a Hitachi Content Platform device fails when the custom metadata is not present
Article ID: 100012035
Updated On:
Description
Error Message
The following can be seen in a Dtrace of the EVSVR process when attempting to perform a DumpSaveset of an item:
Hitachi Content Platform (HCP) Streamer: ConnectionManager::Set_Curl_Operation method https://HCP.namespace.domain.com/rest/evstorage/Partition1/622945B2F0A42B459441AEC79677B857/2012/Nov/27/fd14660c-3950-424a-a3b0-39af2406a5e4/22_22_22/00001 Reason = 200 : OK - opr_GET
Hitachi Content Platform (HCP) Streamer: ConnectionManager::Set_Curl_Operation method https://HCP.namespace.domain.com/rest/evstorage/Partition1/622945B2F0A42B459441AEC79677B857/2012/Nov/27/fd14660c-3950-424a-a3b0-39af2406a5e4/22_22_22/00001?type=custom-metadata Reason = 204 : NO Content - opr_GET_BUF
Cause
EV stores custom metadata to the HCP along with the item content, and this metadata is required for item retrieval.
When migrating data from one HCP device to another, it is important to ensure that both the item content and the custom metadata are migrated. Not all migration methods and tools will migrate the custom metadata along with the item content.
Resolution
If the custom metadata was left behind in a migration, it is necessary to contact Hitachi support or the vendor responsible for the migration in order to have the custom metadata migrated to the new HCP.
Issue/Introduction
