VMware Cloud Community
DigitalVoodoo
Enthusiast
Enthusiast

LUN ID and VCB problem

Since VCB 1.0.2 supposedly supports SAN multipathing, I installed the IBM RDAC software on my VCB proxy server. After rebooting, my local C: drive shows as disk 0, followed by all my SAN LUNs. Since my SAN LUN 0 is now no longer disk 0 within Windows, VCB fails when trying to backup a VM.

I've pulled the fibre connection, rebooted the server, ran diskpart - automount scrub, rebooted again, and it still places the local disk as disk 0, ahead of the SAN LUNs. I had everything running perfectly without the RDAC driver and VCB 1.0.1 previous to this. Does anyone know how I can get the SAN LUNs to be listed before the local disk, like it was before?

0 Kudos
2 Replies
masaki
Virtuoso
Virtuoso

Try entering Computer Management and then Disk Management then set your LUN 0 as active partition.

Let me know

0 Kudos
DigitalVoodoo
Enthusiast
Enthusiast

I resolved the issue by removing the IBM RDAC driver, after which my LUNs were presented first and VCB functioned correctly.

0 Kudos