AVVI backups completes with exception "V-79-57344-38725 - One or more virtual disks contain volumes that do not support Granular Recovery Technology (GRT). Granular restores cannot be performed for these volumes"

Problem

GRT enabled backup of Virtual machine completes with following exceptions and no data is seen for restore.

Error Message

GRT backup of virtual machine completes with following exception in the job log:

V-79-57344-38725 - One or more virtual disks contain volumes that do not support Granular Recovery Technology (GRT). Granular restores cannot be performed for these volumes.


Following error is recorded in beremote logs from Media server:
=============================================================================
[4052] 2013-09-25T17:06:30.027 [fsys\shared] - VDDK-Log: Partition:Invalid sector magic number.
[4052] 2013-09-25T17:06:30.027 [fsys\shared] - VDDK-Log: Disk number 1 has
been skipped because of errors while reading partition table
[4052] 2013-09-25T17:06:32.913 [fsys\shared] - VDDK-Log: Partition:Invalid sector magic number.
[4052] 2013-09-25T17:06:32.913 [fsys\shared] - VDDK-Log: Disk number 1 has
been skipped because of errors while reading dynamic disks header or LDM
database is corrupted
[4052] 2013-09-25T17:06:32.929 [fsys\shared] - VDDK-Log: Partition:Invalid sector magic number.
[1544] 2013-09-25T17:06:32.929 [engidrapi] - CDiskLayoutImplementation::SetAutoMount: Enabling AUTOMOUNT
[4052] 2013-09-25T17:06:34.988 [fsys\shared] - VDDK-Log: Unable to GetVolumeMountPoints - Error code b0.
[1544] 2013-09-25T17:06:34.988 [mounter] - 'VMDKRemoteImage::GetVolumeMountPoints() ' numGuestMountPoints == 0
[1544] 2013-09-25T17:06:34.988 [mounter] - 'VMDKRemoteImage::GetVolumeMountPoints() ' Mount point: '\\.\vstor2-mntapi10-
shared-8492D932007E000000000000EC000000\' Drive Letter:
.
.
.
[1544] 2013-09-25T17:06:39.512 [mounter] - Cannot find boot configuration file.
Searching for the registry hive file in the first volume of each disk
 [1544] 2013-09-25T17:06:39.512 [mounter] - Info: Cannot find the registry hive
file: \WINDOWS\system32\config\system 0 0x0
 [1544] 2013-09-25T17:06:39.512 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8492D932007E000000000000EC000000\\WINDOWS\system32\config\system 0 0x0
 [1544] 2013-09-25T17:06:39.512 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8592D932007E000000000000ED000000\\WINDOWS\system32\config\system 0 0x0
 [1544] 2013-09-25T17:06:39.512 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
9A6C17D9007E000000000000EE000000\\WINDOWS\system32\config\system 0 0x0
 [1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
DE5FC372007E000000000000EF000000\\WINDOWS\system32\config\system 0 0x0
 [1544] 2013-09-25T17:06:39.527 [mounter] - Cannot find boot configuration
file. Searching for the registry hive file in any volume of each disk
 [1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \WINDOWS\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8492D932007E000000000000EC000000\\WINDOWS\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8592D932007E000000000000ED000000\\WINDOWS\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
9A6C17D9007E000000000000EE000000\\WINDOWS\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
DE5FC372007E000000000000EF000000\\WINDOWS\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Cannot find a valid boot
configuration file under WINDOWS directory. Searching for a WINNT directory
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8492D932007E000000000000EC000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8592D932007E000000000000ED000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
9A6C17D9007E000000000000EE000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
DE5FC372007E000000000000EF000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Cannot find boot configuration
file. Searching for the registry hive file in any volume of each disk
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8492D932007E000000000000EC000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
8592D932007E000000000000ED000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
9A6C17D9007E000000000000EE000000\\WINNT\system32\config\system 0 0x0
[1544] 2013-09-25T17:06:39.527 [mounter] - Info: Cannot find the registry hive
file: \\?\GLOBALROOT\Device\vstor2-mntapi10-shared-
DE5FC372007E000000000000EF000000\\WINNT\system32\config\system 0 0x0
.
.
.
[1544] 2013-09-25T17:06:39.527 [mounter] - VDiskMounter::MountAllDisks:
ignoring volume at offset 16384 because it doesn't have a volume device (is it
mounted?)
[1544] 2013-09-25T17:06:39.527 [mounter] - VDiskMounter::MountAllDisks: no
drive letter or volume GUID found, volume ignored
[1544] 2013-09-25T17:06:39.527 [mounter] - VDiskMounter::MountAllDisks: no
drive letter or volume GUID found, volume ignored
[1544] 2013-09-25T17:06:39.527 [mounter] - VDiskMounter::MountAllDisks: no
drive letter or volume GUID found, volume ignored
[1544] 2013-09-25T17:06:39.527 [mounter] - VDiskMounter::MountAllDisks: no
drive letter or volume GUID found, volume ignored
[1544] 2013-09-25T17:06:39.527 [mounter] - Mount of all disks succeeded
[1544] 2013-09-25T17:06:39.527 [fsys\ntfs\img_pdi] + img_pdi_attach.cpp (675):
[1544] 2013-09-25T17:06:39.527 [fsys\ntfs\img_pdi] | Error mounting disk(s): E_IMG_FS_NO_GRT_VOLUMES_FOUND (0xe0009745).
[1544] 2013-09-25T17:06:39.527 [mounter] - CommonMounter::~CommonMounter called
 =============================================================================

Solution

Workaround:

Perform a Remote Agent based backup of VM.

 

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue 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 Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see
www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

 

Applies To

BE 2012 with SP2

ESX 5.0

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)