....snip...Why wasn't the file overwritten? (obviously because WFP replaced it, but tsm has to take this into account I
No, it doesn't. The TSM support for the System Object restore doesn't play nicely with Windows File Protection in Win2K . Tivoli actually issued a warning about that in March. You need to restore the WFP catalog BEFORE you restore the system object. GO to www.ibm.com and search on the string "modified instructions for complete restores", it has instructions. Even that doesn't always fix all the problems. In my testing it fixed SOME but not ALL of the WFP issues noted in the event log after restoring the System Object. With the TSM 5+ clients, it appears that the result you get when doing a complete restore of Win2K depends entirely on how close the Win2K system you install matches the system you are trying to restore, in terms of service packs and patches. On the finally-some-good-news front, we have been testing TSM+ASR restores of WinXP and Win2003, and so far I'm really pleased with the process. Then again, I dread what happens when we get the next XP service pack... Wanda Prather "I/O, I/O, It's all about I/O" -(me) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Adam Tuliper Sent: Thursday, September 30, 2004 3:42 PM To: [EMAIL PROTECTED] Subject: INACCESSIBLE_BOOT_DEVICE and Windows File Protection A Win2k system of ours had to be rebuilt because of a bad stripe entry in the bad stripe table. We did a base install of win2k (however looking back realized we didnt install any sp's on our base installation of windows, and the one that was being restored had SP3). We restored the files first, and then the system objects. Upon a reboot after restoring the system objects we received inaccessible_boot_device. We repeated this process trying the base install with the same version raid driver that was in backup. Before the reboot once the system object restore finished, I checked the event log and noticed (among other entries) that windows file protection was not allowing ipsraidn.sys to be overwritten with version 4.5.000 from backup, but was keeping the 3.0 driver that was there. 4.5 I know is what we needed. After going to a recovery console and replacing this driver with one from backup, our system finally booted. Why wasn't the file overwritten? (obviously because WFP replaced it, but tsm has to take this into account I would imagine, so what did I do wrong?) Thanks, Adam --------------------------------------------------------------------- Web mail provided by NuNet, Inc. The Premier National provider. http://www.nni.com/
