Backup drive no longer available, need advice on how Windows Server Backup will respond
Posted on 2011-10-05
We have a VMWare environment (3 ESX 4.0 hosts connected to an EqualLogic SAN via iSCSI) that hosts our Windows servers. One of those servers is Windows 2008 with Exchange 2010 installed. On the advice of a consultant who helped set up the environment just over a year ago, we purchased an Iomega NAS device to serve as a destination for backups. After installing the NAS in the environment, we set up an iSCSI target on it and added it as storage to the ESX host systems, then mapped it to the Exchange server as an RDM, and then set it up for use by Windows Server Backup for scheduled backups of the Exchange data and log files. Last Thursday the NAS device spontaneously failed and after working with Iomega support for three days, the NAS is not recoverable. I contacted VMWare support on Monday re: the functionality of the server and how to remove the RDM and maintain the ability to reboot the server normally. I was told that I will need to shut down the server, edit the server settings and remove the RDM to the Iomega NAS, and then the server should be able to boot back up normally.
My question is, can anyone give me some insight as to how the backup program will react when I do this? Currently, when I open the backup program it will not completely open as it is searching for the backup destination, and therefore cannot load the backup history, etc. Is there a way to force the backup program to open without being able to connect to the currently configured backup destination, so that I can cancel the scheduled backups and complete a single backup of the Exchange data and logs before removing the RDM from the server? If not, will the backup progam continue to not be able to load after removing the RDM, or will it then see that the backup destination is not available and then be able to open so that I can resume using it? Any and all help is greatly appreciated!
Thanks very much,