Error Message

Job log shows as Backup Exec has discovered and protected Volume GUID instead of the drive letter.

Backup Exec has discovered and protected 'VOLUME{82C9235B-0F63-11EE-A2F5-00155D02B11B}' on virtual machine 'conputer name'.
Backup Exec has discovered and protected 'VOLUME{82C9235E-0F63-11EE-A2F5-00155D02B11B}' on virtual machine 'computer name'.
Backup Exec has discovered and protected 'VOLUME{82C9236F-0F63-11EE-A2F5-00155D02B11B}' on virtual machine 'computer name'.

Consolidate full job fails with the following error when GRT is enabled.

Final error: 0xe0009773 - Backup Exec failed to validate the consolidate full backup set as one or more virtual machine volumes could not be found. This could be because the virtual disk is corrupted. Run a full backup from the source.
Final error category: Resource Errors

V-79-57344-38771

Consolidate full job fails with the following error when GRT is disabled.

Final error: 0x3 - The system cannot find the path specified.
Final error category: Other Errors

V-79-57344-38773 - Backup Exec failed to validate the consolidate full backup set as one or more virtual disks could not be mounted for virtual machine 'VRTSRV::\\clustername.domain\Hyper-V?HA?VM\vmname'.
Unable to open the item VRTSRV::\\clustername.domain\Hyper-V?HA?VM\vmname\C:\ClusterStorage\Volume1\disk-path\disk0.vhdx - skipped.
 

Backup Exec is unable to mount the guest volume to the Backup Exec server because the volume GUID is duplicated between the Backup Exec server and the VM.

The volume GUID for each server or VM can be found with the mountvol command.

C:\Users\Administrator>mountvol

 (omission)

Possible values for VolumeName along with current mount points are:

    \\?\Volume{f22b528e-85e8-4926-8bf4-4b9c93415d80}\
        *** NO MOUNT POINTS ***

    \\?\Volume{af42126d-a19c-4ae8-ac07-9484cd0ac00d}\
        C:\

    \\?\Volume{69df76b9-3bfa-49c9-a106-18881a4a6090}\
        E:\

    \\?\Volume{d4685b1d-695d-4a31-aade-bb800756232b}\
        *** NO MOUNT POINTS ***

    \\?\Volume{ee7378ee-d941-11ed-a2ea-806e6f6e6963}\
        D:\
 

Workaround:

a) If the backup data is NOT stored on a local disk within the Backup Exec server, initialize the local disks and volumes, and perform a fresh install of the Backup Exec Server OS, then perform a fresh install of the Backup Exec.

Note 1: Initializing the disks would generate new volume GUID.

Note 2: If the backup data of Backup Exec server itself is stored in a NAS or tape, SDR (Simplified Disaster Recovery) can be used to initialize the local disks and volumes of Backup Exec server.

b) Use SDR to initialize the VM's disks and recover the VM.

Note 3: It is needed to take a backup using the remote agent with SDR enabled once.

Note 4: Remote SDR can be performed from any backup storage.

c) Use the remote agent backup instead of the virtual agent backup.

 

There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. While this issue may be resolved in a future major revision of the software at a later time, it is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.

Some or all drive letters are not detected with GRT (Granular Recovery Technology) enabled virtual machine backup jobs when the Backup Exec server and the virtual machine are deployed from the same image or template. Consolidate Full backup job of Forever Incremental backups fails due to check mount point even if GRT is disabled. Full, incremental, or differential jobs are completed without any error. Server details view in Backup and Restore tab shows many volume GUIDs without drive letters. (Figure 1) Figure 1.

Restoring files/folders wizard also shows many volume GUIDs without drive letters. (Figure 2) Figure 2.

ETrack: 4114576