Enterprise Vault Event 41008 - Troubleshooting Digest
Article ID: 100012604
Updated On:
Description
IMPORTANT: Do not edit this content in Information Manager
Internal Notes
The content of this document is referenced in Veritas Quick Assist. Do not make changes to this article. If you would like changes to be made to this content, use the Information Manager feedback feature. Alternatively, you can send e-mail to the owner or the Enterprise Vault Knowledge Management team.
These Event IDs might be caused by these issues as well:
NOTE: These KM Articles are internal ONLY and cannot be sent to the customer.
| Description of the issue | Article # |
| Event ID 41008 is occurring stating savesets have not been backed up even though the WatchFile and JournalArchive tables show otherwise | 100007350 |
| Event ID 41008 is occurring when using a Hitachi Content Platform (HCP) storage device. | TECH174675 |
Resolution
Note: It is imperative the Enterprise Vault is regularly backed up. For more information on the Best Practices for Enterprise Vault Backup, see 100006827.
These Event IDs might be generated under several scenarios. Click on any of the articles in the list below for links to available solutions:
| Description of the issue | Article # |
| How to use a trigger file (IgnoreArchiveBitTrigger.txt or PartitionSecuredNotification.xml) for devices that do not support the Archive bit | 100016637 |
| Event 41008 is being generated when Vault Store is set to Remove safety copies "Immediately After Archive" | 100022359 |
| Event 41008 is being generated when there are a few items in the WatchFile table of the vault store database. | 100019373 |
| Event 41008 is being generated when using Backup Exec Remote Agent for Windows Servers (RAWS) | 100007852 |
| Event 41008 is being generated when using NetBackup Agent for Enterprise Vault while Vault Store partition backup is set to use 'Archive Bit' and backups have been successful. | 100008316 |
Issue/Introduction
.
Was this article helpful?
Yes
No
Powered by
