Drive Letter Mount Points on the VCB Proxy Don't Match Drive Letters Seen from NT4 Virtual Machines (1389121)
I'm using VMware Consolidated Backup to perform file-level backups of NT4 virtual machines that have more than one virtual disk. I've noticed that the drive letter mount points on the VCB proxy do not match the drive letters seen from within the virtual machine.
By default, VMware Consolidated Backup detects drive letter assignments for virtual machines and creates corresponding mount points on the VCB proxy. For example, the file system mounted on drive E in the virtual machine shows up under C:\mnt\vm37.company.com\letters\E.
For NT4 virtual machines with more than one virtual disk, the mount points and drive letters might not match. For example, the file system mounted on drive D in the virtual machine might be mapped to C:\mnt\vm37.company.com\J.
To fix this problem:
Log onto the virtual machine and start the Windows Disk Manager.
Select a volume and change the drive letter assignment for this volume.
For example, select the volume with letter F: and remap it to drive letter X:.
After making this modification, you can change the volume's drive letter back to the original value, if needed.
Quit the Windows Disk Manager.
Windows NT adds information about the virtual machine drive letter assignment to the registry. Consolidated Backup can now correctly map the drive letters on the VCB proxy.