Some mail items with invalid dates cannot be archived on a Hitachi Content Platform partition
Article ID: 100031370
Updated On:
Description
Error Message
The following Event is logged in the EV Event Log:Type : Warning
Date : 10/6/2015
Time : 3:40:24 PM
Event : 29061
Source : Enterprise Vault
Category : Storage Archive
User : N/A
Computer : EVServer.Domain.local
Description:
A problem was encountered while trying to process a saveset in the storage queue.
The saveset will be requeued and one more attempt will be made to process it later.
Details: The device does not recognize the command. (0x80070016)
Storage Queue Location: D:\StorageQueue
Storage Queue Batch File: D:\StorageQueue\EVStorageQueue_17D26F333828B104C841EB4B5A29F1F931210000vault_20150929192311_03998.EVSQ
Transaction Id: C250433AC51A628CDE5C389DCD2BEE31
Vault Store Entry Id: 17D26F333828B104C841EB4B5A29F1F931210000vault
For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3598&error=V-437-29061
A Dtrace of StorageArchive shows:
ConnectionManager::Set_Curl_Operation method https://HCP_Partition.Domain.local/rest/PTN2 /1D1B6D21E0BAAD42844F535EDE5FDD8D/2015/Oct/06/1c969d20-bf75-47d2-9471-a174c9c89d69/12_52_23/01771?retention=1760-08-29T14:16:58-0000 Reason = 400 : Bad Request - opr_PUT
Cause
EV attempts to write the item to storage along with the date that it will be eligible for expiry. This date is calculated by evaluating the number of days represented by the Retention Category currently assigned to the item and adding this number to the item's expiry basis date. In the above situation, this results in an expiry date that is still implausibly far in the past.
For example, the item's Modified Date is August 29 1753. The Retention Category currently assigned to the item has a Retention Period of 7 years. This puts the item's expiry date sometime in 1760, and this value is passed to the storage device alongside the item when EV stores it.
Hitachi Support has confirmed that their API Streamer will not allow any items to be written to the storage device with any dates older than 1971. This results in the 400 response from the storage device when EV attempts to store the item.
For example, the item's Modified Date is August 29 1753. The Retention Category currently assigned to the item has a Retention Period of 7 years. This puts the item's expiry date sometime in 1760, and this value is passed to the storage device alongside the item when EV stores it.
Hitachi Support has confirmed that their API Streamer will not allow any items to be written to the storage device with any dates older than 1971. This results in the 400 response from the storage device when EV attempts to store the item.
Resolution
The only known workaround to this issue is to switch the expiry basis for items to Archived Date rather than Modified Date. This should prevent EV from calculating and submitting to the HCP any expiry dates that are in the past.
The expiry basis can be configured on the Storage Expiry tab of the EV Site's Properties page.
The expiry basis can be configured on the Storage Expiry tab of the EV Site's Properties page.
Issue/Introduction
Certain types of unsolicited mail may be manipulated to show a Modified Date property that is implausibly far in the past (e.g., August 29, 1753).
If both of the following conditions apply, then Enterprise Vault (EV) will not be able to archive such items.
If both of the following conditions apply, then Enterprise Vault (EV) will not be able to archive such items.
- The open partition of the Vault Store is on a Hitachi Content Platform storage device
- The EV site is set to base expiry on the Modified Date of the item
Was this article helpful?
Yes
No
Powered by
