This article outlines the side-effects of having antivirus scanning active in the Staging Area during migration.
It is recommended to exclude virus scanner activity from Staging Area during migration.
In virus scanners there are usually options to:
- Exclude files/folders
- Exclude processes from ‘in memory scanning’
‘In memory scanning’ is not available in all antivirus scanners. In those that do in memory scanning, following processes might be excluded:
- EV processes (if the source is EV)
- Archive Shuttle processes on that EV source server
If an antivirus scanning is active the following may be observed:
- Significantly slower export
- Significantly slower import
There may also be the specific errors during:
- Files being locked errors
- Denied access to the export folder of Staging Area. See an example below:
2015-11-30 22:56:25Z|1215| 25|ERROR| Process|Other Error occured Void WinIOError(Int32, System.String) Access to the path '\\HostName\StagingAreaFolder\5e555bc6-9121-4d5d-9352-99bf1e82eea6\79f8ac9b-8668-468b-9854-2cf66799124d\46\6a8e1c79-b2e6-486c-9eb9-602e44cb77b0' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
- Item not found errors. This kind of errors can cause the re-export of ‘missing’ files (can be overwritten in the System Configuration).
- Hash failures/Chain of Custody errors. The antivirus product may change the files on disk, which leads to hash checking failures during the import (which leads to items being re-exported).