Error Message

At then end of the expiry run the informational report will show much less than expected being deleted. 

For example: 

Type :                Information
Event :              7085
Source :            Enterprise Vault
Category :        Storage Delete
Computer :        evserver1.ev.local
Description: Storage Expiry Report
Vault Store Name: jrnlvaultstore01
Vault Store Id: 1FB16196F0DDB5948BB56449DF9C0C9081210000ev01

Number of vaults processed: 8
Number of vaults enabled for expiry: 8
Total number of expired items deleted: 643
Total number of items that could not be deleted: 0
Items marked with sent/received date based retention categories have been deleted:
(none)
Items marked with archived date based retention categories have been deleted:
Journal (90 days) : 643 items.

Items marked with fixed date based retention categories have been deleted:
(null)

Start Time: 10/29/2020 4:30 AM
End Time: 10/29/2020 4:44 AM

Event ID 6605 will acknowledge all items failed to be expired:

Type :              Error
Event :             6605
Source :           Enterprise Vault
Category :        Storage Delete
Computer :        evserver1.ev.local
Description:
Failed to process all expired items in Vault.

The maximum allowed number of saveset errors has been exceeded while processing savesets for automatic expiry.  Enterprise Vault has abandoned expiry for this archive but will try again when automatic expiry reruns.     For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.1.0.0&build=12.1.2.1531&error=V-437-29108  (0xc00471b4)

Vault Name: Journal Archive SMTP
Vault Id: 10A3E2836F54D0A499BFE6EEAE67EE47B1110000ev01

V-437-6605
 

The following events will specify specific items and clid id's that failed to expire:

Type :           Error
Event :          6761
Source :         Enterprise Vault
Category :        Storage Delete
Computer :        evserver1.ev.local
Description: Error opening EMC Centera C-Clip

Function call: Cluster.readBlob

Status: FP_ACCESSNODE_ERR (-10103)

Reason: No Access Node can be found

Pool Address: 192.168.240.1,192.168.240.2?\\ev01\c$\pea\PEA\ev-merged.pea

V-437-6761

Type :          Error
Event :         6883
Source :        Enterprise Vault
Category :        Storage Delete
Computer :        evserver1.ev.local
Description:  Unable to complete deletion request
Reason:             Error opening EMC Centera C-Clip   Function call: #1   Status: #2 (#3)   Reason: #4   Pool Address: #5     For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.1.0.0&build=12.1.2.1531&error=V-437-6761  (0xc0041a69)

Vault:              Journal Archive SMTP
Vault Id:           10A3E2836F54D0A499BFE6EEAE67EE47B1110000ev01
Item Id:            201705094341282~201705091446060000~Z~91385CAE859411046E856BF95D83FAD1
Reference:          DIFCS/cd
Extended Item Info: (null)

Supplementary Info:
0FASKJTU39055e1H71OHJ590Q05             

V-437-6883

Important to note that subsequent runs of storage expiry will not error out on the same items again. Inspection and searches of the archive will show that items that previously errored with event ID 6883 are no longer in the archive and have been deleted. However, new items will show in the event logs. 

This issue can be due to intermittent or slow network connections to the Centera device configure in the partition. 

Use of CenteraPing.exe taking longer than 1 second to access the device can be an indicator of slow network performance to the device. 

Please see the following for using CenteraPing: 

https://www.veritas.com/content/support/en_US/doc/115426612-142076551-0/v8823856-142076551

Resolve any slow network performance issues between the EV server and the configured Centera device.