Hi Steve I would be very grateful to see the document he is using for a successful TSM restore in ASR mode of windows 2003 for HS20 8843's.
At least, from my multiple attempts, the HS20's with this particular broadcom network card integrated in them is NOT being seen by windows in ASR mode...I have used the Micorosoft devcon.exe DOS utility to look at both the devices and the drivers in Windows 2003 during the DOS session where TSM asks if you want to start the restore from network or from local-backup, and there are no NIC drivers getting installed with a native Windows 2003 standard CD. Ipconfig /all just returns "Windows IP" and ROUTE PRINT returns the 127.0.0.1 address. I also checked BIOS settings of the Broadcom's to see if there is a "compatible" mode for the card to behave more like a "standard" ethernet NIC, but there is no such setting. Devcon does see the ethernet PCI devices, though, so that tells me that Windows 2003 native CD drivers just do not know how to install for them? I have perused the IBM Serverguide CD for this blade, and it has the updated broadcom drivers in them but now I am stuck as to how to integrate them with the actual ASR strategy. Even if I could figure out which script in the ASR process to insert the right device-driver-load-instructions...I am still faced with this now not being ASR (i.e. automated) I mean, I can do a server-guide install of vanilla windows and then install Tivoli client, configure the Tivoli client, then restore with Tivoli while making sure the backed-up registry and other system objects overwrite the vanilla ones. In fact, that is what I am testing right now. But with 14 servers per chassis and three chassis full...well, it would not be preferable to have to have a big long manual process that has to be repeated 42 times in a disaster recovery situation. :( It would seem much more beneficial to have 2 CD's and 1 floppy disk to restore each server with a simple set of instructions that anyone in IT could follow? -Jim Hatfield IT Manager Kings Daughters Medical Center [EMAIL PROTECTED] -----Original Message----- From: Steven Harris To: [email protected] Sent: 6/16/06 1:47 AM Subject: Re: [ADSM-L] TSM-ASR and BladeCenter Jim One of my colleagues swears that he has done this sucessfully. He suggests that DHCP is a prerequisite and not having this may be the source of your problem. Steve Harris AIX and TSM Admin AndersenIT, Brisbane Australia www.andersenit.com.au > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Jim Hatfield > Sent: Friday, 16 June 2006 6:31 AM > To: [email protected] > Subject: [ADSM-L] TSM-ASR and BladeCenter > > > Hello Group, > > Has anyone successfully ASR restored an IBM bladecenter > server blade? I am all the way to starting the first restore > after the Tivoli client has already been silently installed, > but network services have not started and I can find no > literature on IBM or MS sites? > > Thankfully, there is a DOS window open to do some > troubleshooting and I am starting that (hence, ipconfig shows > no interfaces but 127.0.0.1), but I am wondering if anyone > else has gone here before? > > I am using the "Using Microsoft Windows Automated System > Recovery (ASR) to Recover Windows XP and Windows 2003 Systems > with the IBM Tivoli Storage Manager Backup-Archive Client for > Windows" Tivoli Field Guide. > > Or is there a better mouse-trap for ASR in BladeCenter? > > Thank You, > > -Jim Hatfield > Frustrated IT Admin > Kings Daughters Medical Center > [EMAIL PROTECTED] > > --------------------------------------------------------------- > This e-mail and any attachments may contain confidential and > privileged information. If you are not the intended > recipient, please notify the sender immediately by return > e-mail, delete this e-mail and destroy any copies. Any > dissemination or use of this information by a person other > than the intended recipient is unauthorized and may be illegal. > > > --------------------------------------------------------------- This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal.
