Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Windows Small Business Server > SBS 2003 recovery from NTBackup to new RAID volume and partitionfollowing Blue Screen

Reply
Thread Tools Display Modes

SBS 2003 recovery from NTBackup to new RAID volume and partitionfollowing Blue Screen

 
 
MarcusN
Guest
Posts: n/a

 
      03-23-2011
I had a blue screen event on my SBS 2003 R2 server. When the server
reboots it is highly unstable and a lot of services won't start (e.g.
ISA, Exchange, SQL).

I have full C partition (OS location), system state, Exchange MDBDATA
and SQL backup conducted by NTBackup for the days before the blue
screen.

The C partition is on a RAID5 volume (CVOL) which has a SMART error
and bad stripes. This is what I have done.

1) I have created a new RAID5 volume (DVOL) of the same size as CVOL
on new disks.

2) I booted the server in safe mode and, using server management
console, created a new D partition on the DVOL volume. I formatted it.

3) I have rebooted the server in DSRM safe mode and used NTBackup to
recover the C partition to the new D partition, and system state from
the NTBackup from two days before the blue screen.

4) I rebooted the server, entered the RAID array control utility (Ctrl-
A as it's an Adaptec array) and promoted DVOL ahead of CVOL in the
boot order, restarting the server when the change was accepted.

Problem. The server doesn't boot into SBS 2003 R2. I just get a
blinking cursor. F8 to select the boot options such as safe mode
doesn't work. I have to power down and reverse point (4) to get an OS
load.

Question 1. What am I doing wrong?

Question 2. How do I create a complete restore of the OS partition and
system state but to a new Volume so that I can avoid the SMART error
and bad stripes that plague the original Volume?

Question 3. Is there anything specific I need to do so that I can
eventually recover Exchange and all my SQL data bases?
 
Reply With Quote
 
 
 
 
Amt37
Guest
Posts: n/a

 
      04-08-2011
Hello all,

As I have about the same problem with no solution, I would be really
interested in an answer to this question.

I have to migrate an SBS 2003 Server from the current machine that doesn't
have enough space on de RAID 5 Array to the same machine witrh new disks.
Any help on the full process would be apreciated.

Thanks
JeanPi


"MarcusN" a écrit dans le message de groupe de discussion :
ab6b5b2c-bdf7-451e-9c94-3a03eaae13e1...oglegroups.com...

I had a blue screen event on my SBS 2003 R2 server. When the server
reboots it is highly unstable and a lot of services won't start (e.g.
ISA, Exchange, SQL).

I have full C partition (OS location), system state, Exchange MDBDATA
and SQL backup conducted by NTBackup for the days before the blue
screen.

The C partition is on a RAID5 volume (CVOL) which has a SMART error
and bad stripes. This is what I have done.

1) I have created a new RAID5 volume (DVOL) of the same size as CVOL
on new disks.

2) I booted the server in safe mode and, using server management
console, created a new D partition on the DVOL volume. I formatted it.

3) I have rebooted the server in DSRM safe mode and used NTBackup to
recover the C partition to the new D partition, and system state from
the NTBackup from two days before the blue screen.

4) I rebooted the server, entered the RAID array control utility (Ctrl-
A as it's an Adaptec array) and promoted DVOL ahead of CVOL in the
boot order, restarting the server when the change was accepted.

Problem. The server doesn't boot into SBS 2003 R2. I just get a
blinking cursor. F8 to select the boot options such as safe mode
doesn't work. I have to power down and reverse point (4) to get an OS
load.

Question 1. What am I doing wrong?

Question 2. How do I create a complete restore of the OS partition and
system state but to a new Volume so that I can avoid the SMART error
and bad stripes that plague the original Volume?

Question 3. Is there anything specific I need to do so that I can
eventually recover Exchange and all my SQL data bases?

 
Reply With Quote
 
Charlie Russel-MVP
Guest
Posts: n/a

 
      04-09-2011
The simplest (and best) solution, IMO, is to do a Swing Migration
(www.sbsmigration.com) onto a temporary machine, and then back to the
original machine with the new hard disks.

--
Charlie.
http://blogs.msmvps.com/Russel


"Amt37" <> wrote in message
news:4d9f40fe$0$20787$...
> Hello all,
>
> As I have about the same problem with no solution, I would be really
> interested in an answer to this question.
>
> I have to migrate an SBS 2003 Server from the current machine that doesn't
> have enough space on de RAID 5 Array to the same machine witrh new disks.
> Any help on the full process would be apreciated.
>
> Thanks
> JeanPi
>
>
> "MarcusN" a écrit dans le message de groupe de discussion :
> ab6b5b2c-bdf7-451e-9c94-3a03eaae13e1...oglegroups.com...
>
> I had a blue screen event on my SBS 2003 R2 server. When the server
> reboots it is highly unstable and a lot of services won't start (e.g.
> ISA, Exchange, SQL).
>
> I have full C partition (OS location), system state, Exchange MDBDATA
> and SQL backup conducted by NTBackup for the days before the blue
> screen.
>
> The C partition is on a RAID5 volume (CVOL) which has a SMART error
> and bad stripes. This is what I have done.
>
> 1) I have created a new RAID5 volume (DVOL) of the same size as CVOL
> on new disks.
>
> 2) I booted the server in safe mode and, using server management
> console, created a new D partition on the DVOL volume. I formatted it.
>
> 3) I have rebooted the server in DSRM safe mode and used NTBackup to
> recover the C partition to the new D partition, and system state from
> the NTBackup from two days before the blue screen.
>
> 4) I rebooted the server, entered the RAID array control utility (Ctrl-
> A as it's an Adaptec array) and promoted DVOL ahead of CVOL in the
> boot order, restarting the server when the change was accepted.
>
> Problem. The server doesn't boot into SBS 2003 R2. I just get a
> blinking cursor. F8 to select the boot options such as safe mode
> doesn't work. I have to power down and reverse point (4) to get an OS
> load.
>
> Question 1. What am I doing wrong?
>
> Question 2. How do I create a complete restore of the OS partition and
> system state but to a new Volume so that I can avoid the SMART error
> and bad stripes that plague the original Volume?
>
> Question 3. Is there anything specific I need to do so that I can
> eventually recover Exchange and all my SQL data bases?


 
Reply With Quote
 
Amt37
Guest
Posts: n/a

 
      04-11-2011
Hi Charlie,

Thank you for the information.
Unfortunately, I gave the price to the customer and I'm sure he will not
agree for extra cost.
Also, we are in France and I did'nt check if this solution is available in
this language.

On an other hand, what happens if the server has a big crash problem and we
have to change it?
In this case, we have to rebuild the same domain and then use the backup
is'nt it?
In my case, the data are allready on an other disk.
I suppose that I only need the System State and the Exchange information.
Where can I find all the instructions to do this ?
I need to be sure in advance of the result.

Thanks in advance for your good help

JeanPi

"Charlie Russel-MVP" a écrit dans le message de groupe de discussion :
inpvga$qoh$...

The simplest (and best) solution, IMO, is to do a Swing Migration
(www.sbsmigration.com) onto a temporary machine, and then back to the
original machine with the new hard disks.

--
Charlie.
http://blogs.msmvps.com/Russel


"Amt37" <> wrote in message
news:4d9f40fe$0$20787$...
> Hello all,
>
> As I have about the same problem with no solution, I would be really
> interested in an answer to this question.
>
> I have to migrate an SBS 2003 Server from the current machine that doesn't
> have enough space on de RAID 5 Array to the same machine witrh new disks.
> Any help on the full process would be apreciated.
>
> Thanks
> JeanPi
>
>
> "MarcusN" a écrit dans le message de groupe de discussion :
> ab6b5b2c-bdf7-451e-9c94-3a03eaae13e1...oglegroups.com...
>
> I had a blue screen event on my SBS 2003 R2 server. When the server
> reboots it is highly unstable and a lot of services won't start (e.g.
> ISA, Exchange, SQL).
>
> I have full C partition (OS location), system state, Exchange MDBDATA
> and SQL backup conducted by NTBackup for the days before the blue
> screen.
>
> The C partition is on a RAID5 volume (CVOL) which has a SMART error
> and bad stripes. This is what I have done.
>
> 1) I have created a new RAID5 volume (DVOL) of the same size as CVOL
> on new disks.
>
> 2) I booted the server in safe mode and, using server management
> console, created a new D partition on the DVOL volume. I formatted it.
>
> 3) I have rebooted the server in DSRM safe mode and used NTBackup to
> recover the C partition to the new D partition, and system state from
> the NTBackup from two days before the blue screen.
>
> 4) I rebooted the server, entered the RAID array control utility (Ctrl-
> A as it's an Adaptec array) and promoted DVOL ahead of CVOL in the
> boot order, restarting the server when the change was accepted.
>
> Problem. The server doesn't boot into SBS 2003 R2. I just get a
> blinking cursor. F8 to select the boot options such as safe mode
> doesn't work. I have to power down and reverse point (4) to get an OS
> load.
>
> Question 1. What am I doing wrong?
>
> Question 2. How do I create a complete restore of the OS partition and
> system state but to a new Volume so that I can avoid the SMART error
> and bad stripes that plague the original Volume?
>
> Question 3. Is there anything specific I need to do so that I can
> eventually recover Exchange and all my SQL data bases?


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off




1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59