ADSM-L

Re: Win2003 Full system restore

2006-09-07 07:55:59
Subject: Re: Win2003 Full system restore
From: Tim Brown <tbrown AT CENHUD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 7 Sep 2006 07:54:22 -0400
I was able to succsessfully get this to work with ASR, the server did come
up on the newer hardware. I have some minor application issues but at least
it
booted successfully.

Tim 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
Cell: 845-235-4255


----- Original Message -----
From: "Gideon Brown" <GideonB AT COURT.GOV DOT IL>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thursday, September 07, 2006 5:31 AM
Subject: Re: Win2003 Full system restore


Hi!

Can anyone refer to restoring a Win2003 server to a different hardware?


Gideon Brown
Sytem Administrator
03-5319085,052-8395641
gideonb AT court.gov DOT il

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mark Stapleton
Sent: Tuesday, September 05, 2006 7:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Win2003 Full system restore

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/05/2006
10:09:14 AM:
For 2003, you need to be running at least client 5.2.3, or it isn't
going to work.
TSM 5.3.2 is better.

Look in the client manual under "ASR".
Works like a champ.

...except if having a DHCP server on the desired network segment is a
problem. ASR restore will NOT work without one, and that's an issue in
many server rooms.

You can do a complete system rebuild without the ASR process. Basically
(and this is just a skeleton):

1. Install the Windows OS, including the service pack present at the
time of the failure. (You don't have to worry about the hotfixes and
patches.) Get the network card going.
2. Install the TSM client used at the time of failure. Configure it
properly.
3. Restore all non-systemdisk (usually C:) drives with TSM.
4. Restore the C: drive. DO NOT REBOOT EVEN IF ASKED TO.
5. Restore the systemservices. DO NOT REBOOT EVEN IF ASKED TO.
6. Restore the systemstate.
7. NOW, reboot the system.

You should be back in business.

Please, please drill this process. You should practice disaster recovery
before you HAVE to.

--
Mark Stapleton (mark.stapleton AT usbank DOT com) US Bank MR Backup and
Recovery Management
------------------------------------------------------------------------
------
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications
privacy laws, and is also confidential and proprietary in nature. If you
are not the intended recipient, please be advised that you are legally
prohibited from retaining, using, copying, distributing, or otherwise
disclosing this information in any manner. Instead, please reply to the
sender that you have received this communication in error, and then
immediately delete it. Thank you in advance for your cooperation.
========================================================================
======

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.clearswift.com
**********************************************************************

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