Error Message

Backup Exec Job Log:

0xe00095b4 - Incremental\\Differential backup methods are not supported for this VM. The backup job failed, since the option 'to fall back to a full backup' was not selected.

Backup Exec Beremote Debug Log Hyper-V host (C:\Program Files\Veritas\Backup Exec\RAWS\Logs\)

BEREMOTE:  [fsys\vrtsrv]        - VirtualServer::AttachToDLE: file 'C:\Program Files\Veritas\Backup Exec\RAWS\Data\Hyper-V\Temp\D7EB7853-391F-4F09-B180-380B60B0EB86\ED4C6831-864E-41CF-B49D-37BB48AE2D56\FingerPrint0001.db' is not accessible for reading - err: 2 2
BEREMOTE:  [fsys\vrtsrv]        - VirtualServer::AttachToDLE: file 'C:\Program Files\Veritas\Backup Exec\RAWS\Data\Hyper-V\Temp\D7EB7853-391F-4F09-B180-380B60B0EB86\ED4C6831-864E-41CF-B49D-37BB48AE2D56\FullBackupInProgress.txt' exists.  This means the previous FULL backup failed to complete
BEREMOTE:  [fsys\vrtsrv]        - VirtualServer::AttachToDLE: A config change was detected, based on the fallback option setting the incr/diff falls back to a full backup.
.
 

Fingerprint related files are generated during a full backup which assist Backup Exec to perform incremental backup.  The Fingerprint files are left behind or orphaned on the Hyper- v host causing the incremental to run as full or fail depending on the job settings selected.

Backup Exec Virtual Machine Job Options. Use Resillent Change Tracking wherever applicable (Disabled).

If "Use the full backup method for virtual machines that do not support incremental or differential backups" is selected and job fails the incremental condition then it runs as a full. If deselected and incremental condition fails then the job fails to backup any data.



The below is the temporary fingerprint folder repository on the HyperV server. The files left behind in the HyperV GUID\VM GUID folder should automatically delete as the information in these files are moved to the Backup Exec media server Install Path\Data\Hyper-V folder after a successful backup.

If they remain on Hyper-V server after the backup the virtual machine incremental job can run as a Full.

Note: Hyper-V VM List file located in Program Files\Veritas\Backup Exec\RAWS\Data folder can provide the information about the Virtual Machine name and its GUID.

When the issue is encountered locate the Virtual Machine VM GUID folder. 

Before the next Full backup remove the file entries from the Hyper-V server and rename the VM GUID folder on the Backup Exec server.

Hyper-V Host (Default location - C:\Program Files\Veritas\Backup Exec\Data\Hyper-V\Temp\)

Backup Exec Server (Default Location - C:\Program Files\Veritas\Backup Exec\Data\Hyper-V)

Note: After the full or incremental backup, the files on Hyper V fingerprint VMGUID folder are moved and merged into fingerprint related files stored on Backup Exec server in C:\Program Files\Veritas\Backup Exec\Data\Hyper-V folder.

The VM GUID folder on Hyper V server should be empty after the backup.

If a full or any of the incremental failed in a particular manner which results in those files left over or orphaned on the Hyper-V server, then the problem can be encountered.

Technical support can be contacted if the problem persists i.e. after the full or incremental backup, files on Hyper V RAWS\Data\Hyper-V\HyperV-GUID\VM-GUID folder is still being left behind resulting in incremental running as full.