iSCSI drive mapped as raw lun now not available to Windows Backup - Please Help
Posted on 2011-09-30
I am in dire need of some help. In setting up our VMWare environment a year ago, a consultant recommended implementing an Iomega NAS device for backups. Specifically, an iSCSI target was set up on the NAS device with a capacity of 250 GB, and it was added as storage on our three VMWare servers. Then in our Exchange 2010 server, it was added as a raw mapped lun, and dedicated to use by the Windows Server Backup program for backing up our Exchange data and log files. Recently the NAS device experienced an error on one of the drives. In spite of being set to use parity, it did not continue operating with the three remaining drives. It is now unavilable for use by the Windows backup program, and when I open the Windows Backup program on the server it essentially does not load due to not being able to find the backup destination. My question is, is it possible to somehow force the backup program to open so I can then cancel the scheduled backups? Ultimately, I would like to cancel the backups to this drive and remove it completely from the Exchange server. I realize that I currently cannot reboot the Exchange server, as it most likely will not boot up with the unavailable drive still mapped to the server. If I were to remove the drive from the server in its VMWare settings, would that allow the server to boot up, and then the backup program would simply "see" that the drive is gone and then open, or would that cause the server to not be able to boot up. In other words, if I cannot get the NAS device back online (I am waiting on Iomega's tier 3 support, although I was told they would call back in 24 - 48 hrs!!), how do I make the necessary changes to my Exchange server so that I can reboot it when needed and feel confident that it will boot back up? Any and all help is greatly appreciated!