Re: server crashed - recovering from backup
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Tue, 1 Jul 2008 17:12:01 +1000
I _HOPE_ that you in fact have RAID1 (which is mirroring, rather than RAID0
which is striping).
Given both HDDs from a RAID1 pair I would probably set one aside (as my
fallback) and simply connect the other to the new system. I KID YOU NOT!
it's _likely_ to work.
The 'secrets' are to _ONLY_ start in Directory Services Restore Mode (we are
not actually going to restore anything) _NOT_ 'SAFE MODE', and if she BSOD's
on startup it is (again) _likely_ that a 'repair install' will get the
system operational. The DSRM startup, if it gets past BSOD, will allow
hardware changes to be detected and support for the changed devices to be
recognised by the system. Keep restarting in DSRM until such time as no
further hardware changes are detected and pay _particular_ attention to
networking. You DO NOT want to restart normally until the 'internal' NIC is
recognised.
This is your friend:
To view a list of previously attached (nonpresent) devices
At the command prompt, type:
Devmgmt.msc set DEVMGR_SHOW_NONPRESENT_DEVICES=1
In Device Manager, on the View menu, select Show hidden devices.
Remove any old devices, _IF_ you get this far, which is likely.
The major factors which impact the success rate of this are:
ENSURE you only start in DSRM.
PATIENCE. Sometimes the detection of the hardware changes takes time, 10
minutes is not unusual. Just let the system detect changes and load drivers.
Then, let it sit there a bit, and restart again (in DSRM). More devices may
be recognised. Do not start normally until s restart in DSRM has not
detected further change.
HDD subsystem. You are _most likely_ to succeed if the RAID controller is
movable between systems. This doesn't mean to say that 'disparate'
controllers won't work.
HAL. Our old mate HAL can be a bit of a problem. If the HAL from the old
system is not 'optimal' for the new but is 'acceptable' it is quite likely
that you will get up and running.
Both HAL and HDD subsystem can _probably_ be updated by a 'repair install',
if necessary. Patience comes at a price. The need to _only use_ DSRM is
tantamount, miss that option and you not only may be waiting a _long_ time
to be able to log on but it is likely to muck up the 'bindings' of various
services.
<vcsekhar@xxxxxxxxx> wrote in message
news:095a4f7a-bace-42c0-a9de-9a61e8c1d952@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I agree that it would be the easy thing to do, however, a similer one
(original netburst xeon 3.0GHz - single core) is not sold anymore.
In any case the server seemed to be slow responding to requests from
the clients when connected to OWA and exchange, so it would be a good
time to replace it with a much faster CPU now (I can get a xeon quad
core server for less than what i paid for my original server now).
But I am guessing that this is something that would be useful to many
other people in the same situation as I am in now. Typically a Small
business network has a server crash out of warrenty they would try to
replace it with a new one with a new warranty. So thats why I really
need to recover my settings and configuration from the backup, I have
already recoverd the business data from the old machine.
Thanks
chandrasekhar
On Jul 1, 4:52 am, Duncan McC <h...@xxxxxxx> wrote:
In article <be9638cd-ace9-4d66-b765-771b469db455
@p39g2000prm.googlegroups.com>, vcsek...@xxxxxxxxx says...
I have a simple RAID 0 (Mirror), like I said, the HDD's are fine and I
was able to recover all my Data from the drive.
The problem is now that I have to get a new server and I need to
restore all my Active Directory, ISA, Exchange and SQL Server
information
to the new server.
I have a full backup on an external HDD, but the restore documentation
says that it can only be restored to the original server or to
an exact duplicate of the original server with the same SCSI
controller and CPU and HDD partitions.
This is extremely annoying as this limitation is not there even in the
XP destop OS as you can recover to any computer running XP.
I was considering getting a HP or a Dell server, but they have
different RAID and SCSI controllers so the HDD may not be directly
readable by the new computers (not sure about this as I do not have
much experience with SCSI drives.)
Why don't you replace it with an similar IBM? They are generally very
very good, IMO anyway.
So you've had a bad experience, I don't think that a one-off like you've
had is good reason to dismiss IBM's outright.
It would make the restore a bit easier methinks?
--
Duncan- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- Re: server crashed - recovering from backup
- From: vcsekhar
- Re: server crashed - recovering from backup
- References:
- Re: server crashed - recovering from backup
- From: Duncan McC
- Re: server crashed - recovering from backup
- From: vcsekhar
- Re: server crashed - recovering from backup
- Prev by Date: RE: Remote SBS connection
- Next by Date: Re: Vista, Outlook 2007 & Profiles
- Previous by thread: Re: server crashed - recovering from backup
- Next by thread: Re: server crashed - recovering from backup
- Index(es):
Relevant Pages
|
