ADSM-L

Re: TSM Bmr ??

2005-11-29 13:09:45
Subject: Re: TSM Bmr ??
From: Leigh Reed <L.Reed AT MDX.AC DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 29 Nov 2005 18:04:19 +0000
I agree with everything that has been said so far and the performance
posting regarding Christie BMR was impressive. However, I'm not sure
whether I'd want to shell out the cost per server, however good the
results/efficiency.

While TSM is not strictly designed to BMR Windows systems back to
different hardware, I have used it successfully, on many occasions, to
accomplish this.

The IBM technote, previously mentioned does contain most of what is
required, but for me, when restoring to dis-similar hardware, I would
always take a copy (to floppy) of the following files, pre-restore.

W2K
C:\%systemroot%\system32\hal.dll
C:\%systemroot%\system32\kernel32.dll
C:\%systemroot%\system32\ntdll.dll
C:\%systemroot%\system32\ntkrnlpa.exe
C:\%systemroot%\system32\ntoskrnl.exe
C:\%systemroot%\system32\win32k.sys
C:\%systemroot%\system32\winsrv.dll

W2K3
C:\%systemroot%\system32\hal.dll
C:\%systemroot%\system32\ntkrnlpa.exe
C:\%systemroot%\system32\ntoskrnl.exe

If after the full TSM restore process (as detailed in IBM technote), the
machine reboots to a blue screen, then you can use the MS Recovery
Console to copy the system files back to the system root from the
floppy.

Very rarely with some RAID controllers that have additional
functionality (failover, redundancy), I have had to disable certain
devices/services from booting (again from MS Recovery Console). This has
had to be a fairly intuitive process and I would imagine not scriptable
in s/w, unless on a case by case basis.

The only other point to note is that certain levels of past TSM clients
have a bug in them where they incorrectly merge the registry thus
overwriting the disk controller driver and not obeying the "keys not to
restore".

See IC38716

You will still have to re-install the NIC drivers, or drivers for other
PCI cards/peripherals, but you would hope that the hardware supplier
would have these readily available.

JMEW

Leigh





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: 28 November 2005 21:53
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Bmr ??

do you have the link for cristies bmr, and how much
is it

tim

----- Original Message -----
From: "Barnhart, Troy" <TBarnhart AT RCRH DOT ORG>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, November 28, 2005 4:17 PM
Subject: Re: TSM Bmr ??


I'm a big fan of the Cristie's BMR for Windows and RedHat Linux.

They are pretty slick.  I can restore a box from scratch in under 10
minutes.

My only caveat for "dislike hardware" restores is using newer hardware.
i.e. their driver support for older hardware.

We had problems getting older drivers to work correctly - such as old
"HP
LH3 Netservers."

But, with our newer IBM xSeries - very smooth...

Regards,
Troy

Troy Barnhart, Sr. Systems Programmer,
tbarnhart AT rcrh DOT org
Rapid City Regional Hospital,
Rapid City, South Dakota, 57701
ph: 605-719-8068 / fax: 605-719-4206


----- Original Message -----
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, November 28, 2005 4:02 PM
Subject: Re: TSM Bmr ??


What I meant was, to a different TYPE machine, i.e., disklike hardware,
not just a different machine.

The Christie Bare Metal add-on product supports restoring Windows to
unlike hardware.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: Monday, November 28, 2005 4:04 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Bmr ??


you said that windows does not support restoring a registry to
a different machine, but isnt that what happens when i follow
the instructions in the "Disaster Recovery Strategies with TSM"
pdf.

is tsm ever going to support restoring to dislike hardware ?

tim
----- Original Message -----
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, November 28, 2005 3:40 PM
Subject: Re: TSM Bmr ??


http://support.microsoft.com/default.aspx?scid=kb;en-us;249694

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: Monday, November 28, 2005 3:37 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Bmr ??


is there documentation that describes the differences
between "the same machine after a hard drive
failure" and  "restoring to different hardware at a hot site"

i am attempting the later

tim
----- Original Message -----
From: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Monday, November 28, 2005 3:26 PM
Subject: Re: TSM Bmr ??


IT's not a TSM issue, it's a Windows issue.
Microsoft does not support restoring a registry to a different machine.

That being said, they used to have a procedure in the knowledge base
that you can try.
Check there.

How you test BMR, depends on what you are trying to do.
You need different procedures for different possible disasters;

Procedures needed to restore back to the same machine after a hard drive
failure, are simpler than the case where you are restoring to different
hardware at a hot site.




-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: Monday, November 28, 2005 3:25 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM Bmr ??


Is there still a requirement to restore a TSM client to the same server
hardware type. Can the restored
server be somewhat different.

How does everyone else test the TSM BMR procedures.

Tm Brown
Systems Specialist
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbrown AT cenhud DOT com
Phone: 845-486-5643
Fax: 845-486-5921
.

***Note: The information contained in this message, including any
attachments, may be privileged, confidential, and protected from
disclosure.
If the reader of this message is not the intended recipient, or an
employee
or agent responsible for delivering this message to the intended
recipient,
you are hereby notified that any dissemination, distribution or copying
of
this communication is strictly prohibited. If you have received this
communication in error, please notify the Sender immediately by a "reply
to
sender only" message and destroy all electronic or paper copies of the
communication, including any attachments.

<Prev in Thread] Current Thread [Next in Thread>