Link raw device mappings to the LUNs on the storage array

When a LUN is presented to a physical Windows server it’s more easy to link the LUN to the mounted disk within the operation system.
You can simply open the Disk Management tool (diskmgmt.msc) and click on the properties of the disk itself (not the partition!).
On the general tab, you can find the LUN number in the Location section.

In our case some LUNs are directly presented to a virtual machine running Windows 2008R2 (Raw Device Mappings). The disks itself are used within a virtual cluster configuration.
The customer asked me to identify the disk within the virtual machine together with the disk on the storage array (HP EVA 8400).
If you think this should be an easy task, think twice! The procedure below will be able to assist you in this matter.
Continue reading

Registry change after installing Backup Exec 2010/2012 on a Hyper-V 2008R2 node

Installation of Symantec Backup Exec 2012 is fully supported on Windows 2008R2 Hyper-V nodes as described in the Software Compatibility List. However after rebooting the node, Hyper-V throws the following errors. Important to note is that the cluster itself is online without any warnings or errors as described in this post. The errors are visible after live migrating a virtual machine to the impacted target host or when you attempt to start a virtual machine on the impacted node.

‘VM Name’ failed to start.

Microsoft Emulated IDE Controller (Instance ID {########-####-####-####-############}): Failed to Power on with Error: ‘A device attached to the system is not functioning.’

Failed to open attachment ‘Drive Letter:\path\Virtual Hard drivers\VMNAME_########-####-####-####-############.vhd’. Error: ‘A device attached to the system is not functioning’

Failed to open attachment ‘Drive Letter:\path\Virtual Hard drivers\VMNAME_########-####-####-####-############.vhd’. Error: ‘A device attached to the system is not functioning’

and

‘VM Name’’ Microsoft Emulated IDE Controller (Instance ID {########-####-####-####-############}): Failed to Power on with Error: ‘A device attached to the system is not functioning.’ (0x8007001F) (Virtual Machine ID: ########-####-####-####-############)

Some research resulted in the following conclusion:

  1. In the Kernel Mode the following components exist:
    • Fsdepends.sys: File System Dependency Manager Mini Filter Driver
    • Vhdmp.sys: VHD Miniport Driver
    • vdrvroot.sys: Virtual Drive Root Enumerator
  2. The VirtDisk.dll uses the above mentioned components for starting the VDS VHD API’s.
  3. And those are used for the Virtual Disk Service which is configured with a manual startup type…

.
Continue reading

How to restore share information by using Backup Exec 2012

Some time ago, someone contacted me regarding configuration data he lost during cluster disk migrations. Apparently he performed a wrong action whereby all the share information was lost. It should be quiet easy to recreate them, but the customer had no documentation or whatsoever about it.

So there was only one solution… trying to restore the system state of the server to another location. During this process we came across with the issue that share information of a cluster is not stored in the “normal” location.

Continue reading