If Event Import is unable to import an event (for example, because a policy engine fails to process an imported event), the event is saved as an EVF file to a folder specified by the SQL.FailedEVFDirectory parameter.
But if Event Import is then unable to generate an EVF file, it will instead save the failed event as an EVL file. For example, this could potentially happen if the primary CMS stores its event data in a third party object storage solution (such as EMC Centera or NetApp SnapLock) and that object store is temporarily unavailable at the time the import job runs.
EVLs are ‘event link’ files that point to the associated e‑mail events on the primary CMS. You can open EVLs on any machine running the Data Management console to see the associated event. This allows you to identify which event failed to be imported and diagnose the reason for the import failure.
Note: For details about EVL files, see the Data Management console online help; search the index for EVL files.
|
Copyright © 2014 CA.
All rights reserved.
|
|