If an Agent for VMware Virtual Infrastructure (AVVI) file system Granular Recovery Technology (GRT) enabled backup of a Virtual Machine (VM) with an Extended Partition containing at least 3 Logical drives is performed, the backup job logs will not show that the 3rd Logical Drive was part of the backup of the virtual system. Additionally the GRT Restore selections will not show any selections for the affected drive.
As an example, a VM is created using two .VMDK files. The first .VMDK file contains a Primary Partition to hold the C: drive of the VM. The second .VMDK file contains an Extended Partition that has been split into 3 Logical Drives (J: N: & E:) If E: is the 3rd Logical Drive in the Extended partition then the Backup Set Detail Information section in the Backup Job Log will report an entry similar to:
Media Label: IMG000129
GRT backup set folder: F:\B2D\IMG000129
Transport mode 'nbd' was used for the disk 'SERVER01.vmdk'
Transport mode 'nbd' was used for the disk 'SERVER01_1.vmdk'
Backup Exec has discovered and protected 'C:' on virtual machine '\\SERVER01.DOMAIN.local'.
Backup Exec has discovered and protected 'J:' on virtual machine '\\SERVER01.DOMAIN.local'.
Backup Exec has discovered and protected 'N:' on virtual machine '\\SERVER01.DOMAIN.local'.
As can be seen in the above text the E: drive is not even mentioned.
NOTE: Testing has shown that the missing logical drive is backed up and can be restored if recovering the complete VM.
A hotfix is now available for this issue in the current version(s) of the product(s) mentioned at the end of this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.
This issue occurs with Backup Exec 2010 R2 and Backup Exec 2010 R3