I am currently working on some Disaster Recovery procedures and am attempting to utilise the Veritas Intelligent Disaster Recovery software that my client is currently using.
In this instance it is impossible to build IDR bootable media for every server (there are hundreds, and after the project nobody will keep them up to date). We have elected to use their standard server SOE win2k build and run the IDR wizard from it.
I am having massive problems getting the IDR restore wizard to recognise the external tape drive we are using. The unit is a brand new HP/Compaq SDLT320 drive. So far I have tried the Backup Exec 8.6 IDR stuff as well as the 9.0 version. Using both versions it accepts the .DR file, says that it has replaced some system files and then reboots. After reboot, 8.6 complains that it can't find any devices to restore from and 9.0 says something to the same effect. Both just keep rebooting to allow attachment of a tape drive.
Now, I have tried the process both with AND without the actual compaq device drivers manually installed. With them installed I can see the drive in ntbackup and have also restored data before so I don't think the hardware is at fault.
If I manually install the driver then both versions disable it after a reboot or two (which I kind of expect because IDR has its own drivers that it installs). Both versions also disable the "removable storage" service just before the first reboot.
What the hell is going on? If I reinstall the driver after IDR disables it, and force the Removable Storage service to start then I *can* eventually get the process to kind of work and at least get data off the tape.
This shouldn't be this hard should it? Is it all because we've decided to use a standard 2k build rather than using the IDR bootable media?
Any tips would be appreciated
In this instance it is impossible to build IDR bootable media for every server (there are hundreds, and after the project nobody will keep them up to date). We have elected to use their standard server SOE win2k build and run the IDR wizard from it.
I am having massive problems getting the IDR restore wizard to recognise the external tape drive we are using. The unit is a brand new HP/Compaq SDLT320 drive. So far I have tried the Backup Exec 8.6 IDR stuff as well as the 9.0 version. Using both versions it accepts the .DR file, says that it has replaced some system files and then reboots. After reboot, 8.6 complains that it can't find any devices to restore from and 9.0 says something to the same effect. Both just keep rebooting to allow attachment of a tape drive.
Now, I have tried the process both with AND without the actual compaq device drivers manually installed. With them installed I can see the drive in ntbackup and have also restored data before so I don't think the hardware is at fault.
If I manually install the driver then both versions disable it after a reboot or two (which I kind of expect because IDR has its own drivers that it installs). Both versions also disable the "removable storage" service just before the first reboot.
What the hell is going on? If I reinstall the driver after IDR disables it, and force the Removable Storage service to start then I *can* eventually get the process to kind of work and at least get data off the tape.
This shouldn't be this hard should it? Is it all because we've decided to use a standard 2k build rather than using the IDR bootable media?
Any tips would be appreciated