Re: Need to setup RAID in new hardware upgrade SBS2003
- From: Bazzar <Bazzar@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 22 Mar 2009 17:02:04 -0700
Thanks Larry
I already moved the system to a new motherboard with an embedded Intel RAID
controller a couple of months ago. I did it by backing off all drivers then
moved to the new board. Then fed the new drivers. I then cleaned up all ghost
drivers and various other files relating to the old drivers for everything no
longer required and cleaned up the registry as much as possible, manually and
with cleaning software. It worked a treat as I wasn't installing the RAID - I
did try but couldn't without wiping the drives first. It is quite stable now.
I did look at Storage Craft and Acronnis. But it all required a fresh
install of the OS to get the RAID on the new board based on the Intel RAID
process. Apart from the RAID issue my transfer to the new board was fine, as
above. It worked.
You wouldn't think RAID1 would be hard to move to since it just mirrors an
existing drive, unlike striped RAID. But it is what it is, unfortunately.
I made it a single drive for now since I couldn't afford the delay as I
explained before. They are all new hard drives, two for the RAID and one for
image backups. But I'm only using one for now plus one for image backups. I
could try the SATAII RAID PCI card as there are slots available. You seem to
think that will work by allowing a post install of RAID1? I assume I can't
then go to the Intel embedded RAID? That does require wiping the drives to
install and Intel can't think of way around it.
Any more thoughts?
Thanks again
Barry
"Larry Struckmeyer [SBS-MVP]" wrote:
If you use a new controller, whether on board or discrete, you will need to.
install the drivers or the system will not boot. With a discrete
controller, you can insert the controller in the existing system (assuming a
functioning and available slot) and Windows will ask for, or already have,
the drivers. Once the drivers are in place you can install the new drives
on the controller (or even use the old drive if it allows for after the fact
mirroring) and use either an image or the MS approved method of backup and
restore.
I have even been known to use an intermediate discrete controller, say a PCI
SATA to get my installation from board 1 to board 2. When Windows boots on
the controller it knows about it will find all the new hardware and you can
then feed it drivers for the new hardware. At that point you can move the
image to the new controller and the new hard drives.
The path you are suggesting, of building the base Windows installation on
the new on board controller and then blasting back an image to a new set of
drives on a new mobo, will, I am afraid, overwrite the newly installed base
installation and leave you with the original copy of Windows (SBS) from the
old system board that did not include the drivers.
Storage Craft and Acronnis, and maybe others, offer Hardware Independent
Restore products that allow you to feed the drivers for the new hardware as
you are restoring the image.
I think what you are trying to do involves either that path, or a swing
migration, which would get you to the same place with less cost, and with a
cleaner system as this method does not bring over the old registry or any of
the failed software installs, uninstalls, temp files or any of the other
garbage that may be carried in a "previously owned" system, to borrow a
metaphor from the automobile industry.
www.sbs-migration.com
--
Larry
Please post the resolution to your
issue so that others may benefit.
"Bazzar" <Bazzar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:059BF8AF-E296-4AF0-BA9C-4A55FF120C3F@xxxxxxxxxxxxxxxx
Thanks Larry, much appreciated. I am considering the third option of two
fresh drives, installing RAID as I install Windows SBS 2003 then halt the
install at the first reboot then load on the image. As I said the image is
a
fully accessible and operational image, just stick it in and it runs. I
would
then be able to use the image to continue if the attempt fails, as you
suggest as well. That was my plan and I was asking for either an opinion
of
its likely hood of success or an alternative. The system used to be on
RAID.
The old and new are Intel boards but different on board RAID systems so I
couldn't just move it across so since then it has run as a single drive
system. I have talked to Intel engineers and they don't have a solution
although they are considering my proposal to develop one for the future.
I guess I just go to it and try this concept. I am concerned that writing
the image across will destroy the RAID drivers and links to the OS etc. Do
you think that would happen or would the image load on and not interfere?
It
will load the OS and root directory etc if I only copy it across and it
should not touch the boot sector etc. If I use the Paragon Disk Copy I
suspect it may dig deeper. Any thoughts or comments on this? I appreciate
your input.
cheers
Barry
"Larry Struckmeyer [SBS-MVP]" wrote:
Hi:
I am assuming here that we are discussing a single controller which can
be
either single drives or RAID. The thing is, they use different drivers.
The first pass at establishing RAID1 where the OS is already installed is
to
install the driver. If you don't, the system will not restart once the
controller is changed to RAID.
The next most likely is to look to the hardware. Many, but not all, RAID
controllers will allow you to install the second drive after the os is
setup, and then mirror them. In this case, I would ask the hardware
manufacture.
The next most likely is to make an image, remove the known good drive,
install two clean drives, mirror them, and restore the image. If the
driver
for the RAID functionality of the controller is installed, the system
should
boot. If nothing works, you can put the system back like it was while
you
create Plan B.
If you are wanting to purchase a new, or a discrete controller and use
the
existing installation, you will need guidance from the manufacture.
--
Larry
Please post the resolution to your
issue so that others may benefit.
"Bazzar" <Bazzar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:70008AA0-F4BF-4EB8-AC90-6293C00147BC@xxxxxxxxxxxxxxxx
I recently upgraded the server motherboard and CPU to newer gear. It was
RAID1 but in changing I had to keep the installation as some software
would
take weeks to get the vendors organised with new security codes etc to
reinstall. The client can not afford to have that software down that
long.
It now runs on a single hard drive with an image every two days for now
incase of failure. I want to make it RAID1 again. I could do a full
reinstall
but as I said that is not acceptable. I need help with a method to do
this. I
have thought to make an image then install SBS2003 up to the first
restart
then install the image. Trouble is the image is a fully working image
that
will over write everything already installed. It is Paragon Disk Copy
8.
It
creates a fully working image. I have seen suggestions about using MS
Backup
somehow.
Can anyone give me any suggestions? Using Disk Copy or MS Backup or
anything
that will allow me to setup RAID1 and then install the current setup
without
a full reinstall. Can anyone comment on the partial install and using
the
image in some way? I am stuck.
Signed - Mr Desperate!!
- References:
- Need to setup RAID in new hardware upgrade SBS2003
- From: Bazzar
- Re: Need to setup RAID in new hardware upgrade SBS2003
- From: Larry Struckmeyer [SBS-MVP]
- Re: Need to setup RAID in new hardware upgrade SBS2003
- From: Bazzar
- Re: Need to setup RAID in new hardware upgrade SBS2003
- From: Larry Struckmeyer [SBS-MVP]
- Need to setup RAID in new hardware upgrade SBS2003
- Prev by Date: Re: Hyperv backup with windows server backup
- Next by Date: Re: SBS 2008 Protection - Microsoft or Trend?
- Previous by thread: Re: Need to setup RAID in new hardware upgrade SBS2003
- Next by thread: Re: Need to setup RAID in new hardware upgrade SBS2003
- Index(es):
Relevant Pages
|
