I think you will lose enough time for installing TSM, because you route the
traffic
trough Node A (should have 2 NIC's with independent networks attached) and
therefore you lose performance.
Regards,
Stefan Holzwarth
> -----Ursprüngliche Nachricht-----
> Von: Loon, E.J. van - SPLXM [mailto:Eric-van.Loon AT KLM DOT NL]
> Gesendet am: Mittwoch, 29. November 2000 16:18
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: NT Backup/recovery
>
> Hi Stefan!
> Because our method saves time. You don't have to install TSM
> on the crashed
> node which also takes up a couple of minutes (atleast a
> reboot because of
> the installation of the Microsoft Installer).
> Kindest regards,
> Eric van Loon
>
> -----Original Message-----
> From: Stefan Holzwarth [mailto:stefan.holzwarth AT ZENTRALE.ADAC DOT DE]
> Sent: Wednesday, November 29, 2000 16:09
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: AW: NT Backup/recovery
>
>
> Why you don't install a new instance of adsm
> (c:\winnt.tmp\adsm.tmp) on the
> crash'd node
> and restore direct from that node.
> Copy registry should also be possible. Only boot.ini must be modified.
> Regards,
> Stefan Holzwarth
>
> > -----Ursprüngliche Nachricht-----
> > Von: Loon, E.J. van - SPLXM [mailto:Eric-van.Loon AT KLM DOT NL]
> > Gesendet am: Mittwoch, 29. November 2000 13:02
> > An: ADSM-L AT VM.MARIST DOT EDU
> > Betreff: Re: NT Backup/recovery
> >
> > Hi Eric!
> > Assuming your hardware is identical to the one before the
> > crash, ours works
> > like this:
> > We are using a dedicated client (lets call it node A for now)
> > through which
> > recovery is done.
> > 1) Allow on all your managed NT machines access to the backup
> > data for node
> > A. Use the User Access List option to do this.
> > 2) Install NT on the crashed server in a temporary directory, e.g.
> > c:\winnt.tmp. Create a generic administrative account on this
> > machine and
> > again add node A to the User Access List.
> > 3) Start TSM on node A and use the Access Another User option
> > to access the
> > crashed nodes backup data.
> > 4) Start a restore of this data and select the complete C
> > drive for the
> > restore. Select the option "restore to original location" in
> > the restore
> > panel. Node A will now restore the data directly to the
> > crashed node (it
> > uses the administrative share \\machinename\c$ to do this).
> > 5) After the restore, log on to the crashed node, copy all
> > the registry
> > files from c:\adsm.sys to c:\winnt\system32\config and change
> > the Windows
> > directory from \WINNT.TMP to \WINNT in the c:\boot.ini and
> reboot the
> > crashed node.
> > 6) As soon as it's up and running you can delete the
> > C:\WINNT.TMP directory.
> > That's it!
> > There is a Microsoft article on how to restore NT to
> > different hardware
> > (http://support.microsoft.com/support/kb/articles/q139/8/22.as
> p) but we
> haven't tested it yet.
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
> -----Original Message-----
> From: Eric Tang [mailto:tangeric AT HK1.IBM DOT COM]
> Sent: Wednesday, November 29, 2000 03:44
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: NT Backup/recovery
>
>
> Hi All,
>
> For NT 4.0, I have tested the Bare Metal Restore on a testing
> PC and the
> procedures is fine.
> However, it seems unrealistic to have a NT repair partition
> in particular
> for a NT with only one harddisk.
> Just wan to know how you cater for NT system recovery in a
> TSM environment.
> Do you run additional backup utilities? If so, what is your
> procedures.
> Thanks in advance.
>
> Regards,
> Eric Tang
>
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the
> addressee, you
> are notified that no part of the e-mail or any attachment may
> be disclosed,
> copied or distributed, and that any other action related to
> this e-mail or
> attachment is strictly prohibited, and may be unlawful. If
> you have received
> this e-mail by error, please notify the sender immediately by
> return e-mail,
> and delete this message. Koninklijke Luchtvaart Maatschappij
> NV (KLM), its
> subsidiaries and/or its employees shall not be liable for the
> incorrect or
> incomplete transmission of this e-mail or any attachments,
> nor responsible
> for any delay in receipt.
> **********************************************************************
>
|
