Error Message

[DTrace] the ArchiveTask:

EV~I       |Event ID: 41470 An error occurred while archiving to the following archive from the following path: |ArchiveID|Volume Path|14BF10596F30BA843B066A4ABE2EFA4F11110000evserver1|\\cap1.ev.local\G$\DriveG_Files|This archive is associated with the following volume:|VolumeID|Volume Path|145435D185A83E648A2890C85C44C3B5D1011000evserver1|\\FSA_Fileserver.ev.local\G$|The folder will be processed for archiving when the archiving task runs on the associated volume.

1. When creating a CAP, the DNS record and the computer object are automatically created (Windows 2008 R2).

   

2. There is a computer object and a DNS record, it is possible to add the CAP as a Target in EV.
3. If the CAP and the real File Server are added in EV (or more than 1 CAP for the same File Server), it is possible to add the same share as a volume several times (once per EV FSA Target)

     
 
When running the archiving task for \\CAP1, the following errors are logged in the Dtrace and the EV Event log if the Volume has been processed before under \\FSA_Fileserver:
 
EV~I       |Event ID: 40983 Starting to process task: File System Archiving Task.
EV~I       |Event ID: 41470 An error occurred while archiving to the following archive from the following path: |ArchiveID|Volume Path|14BF10596F30BA843B066A4ABE2EFA4F11110000evserver1|\\cap1.ev.local\G$\DriveG_Files|This archive is associated with the following volume:|VolumeID|Volume Path|145435D185A83E648A2890C85C44C3B5D1011000evserver1|\\FSA_Fileserver.ev.local\G$|The folder will be processed for archiving when the archiving task runs on the associated volume.

This result is by design: The Volume is not processed under a different FSA Target to prevent inconsistencies in the Enterprise Vault databases.

Note: It is strongly recommended to avoid mixed targets. If Enterprise Vault manages the content of a Volume it is not necessary to add another target using an additional CAP using the same shared storage content.

The same share is configured as a Volume under two different Enterprise Vault (EV) File System Archiving (FSA) Targets. This shared Volume only archives under the first FSA target.

Here is an example of the above scenario:

1. A Windows File Server and a Client Access Point (CAP) for the same File Server
2. Several CAPs pointing to the same Windows File Server

When the FSA Archiving Task reaches the second Volume associated with the different FSA Target an error is logged and the Volume is skipped.