Full backups appear to run normally, but if the next backup in the cycle is an Incremental or Differential, the above error occurs AFTER the Incremental or Differential appears to complete. Upon inspection of the Repository location via Windows Explorer, the actual archive file for the Full backups may or may not show as 0 (zero) bytes in size. The vmconfig.metadata file and the manifest.metadata file are present, however, indicating the Full backup completed, yet no data is shown as being archived. The "My Repository" screen in vRanger, however, shows the archive sizes correctly.
At the end of the Incremental/Differential backup, a back-end tool in the vRanger install directory (default is c:\program files\Quest Software\vRanger) needs to run against the Differential\Incremental to verify it backed up the proper "deltas" (changes) from the full backup. This process is failing because an on-access (heuristic) virus-scanning engine is "blocking" the back-end tools from running, hence throwing the error message. The anti-virus product determines (incorrectly), that the back-end tools vRanger is trying to invoke are some sort of malware, and are not allowing their execution.
1) "White-list" (exclude) the vRanger install directory from the on-access scan (it still may be scanned via the normal "on-demand" scans that run periodically on the machine).
This behavior has been seen in the following anti-virus products that perform on-access scanning; others may also cause the problem:
Symantec Endpoint Protection
SOPHOS Anti-Virus
ESENT Anti-Virus
