Re: Setting up Raid 1

Thanks for all the help. I appreciate it. I thought if one hard drive
failed, you can boot from the second hard drive, because it is a mirror of
the other. That was my understanding. If you use a hardware raid controller
and one drive fails, the other drive won't be affected or the data should be
in tact?

Thanks for the advice on the new domain. It is a small business around 25
employees. Our final in the class includes setting up a new Domain and that
should help me learn from my mistakes and help me when I do it for real. My
supervisor wanted the in house IT department (the 2 of us) to set it up, but
there is a help desk number we can call if we encouter problems. I wanted
him to take this server 2003 class with me, thought it would of been very
helpful.

"Hank Arnold" wrote:

Basic problem with software RAID is, as mtstream noted, it's prone to
catastrophic failures that will result in total loss of data. We had a
so-called expert consultant set up a 3 drive array as a software RAID 5
(there was no RAID adapter). One of the drives failed. THE ENTIRE ARRAY
WAS LOST!!! We fortunately had a tape backup, but it was a long 12 hours
later that we had it back up...

It's **ALWAYS** best to have hardware RAID. This way, a drive failure
will almost never result in data loss and the drive can be replaced (and
rebuilt) with almost no disruption to the users (other than things
slowing down).

Whether the RAID adapter is built in or an add-on depends on the way it
is manufactured. If the RAID hardware is provided by the manufacturer,
it's going to already be enabled in the BIOS.... The arrays may already
be configured if that was an option. We ordered a Dell 2900 server with
2 drives and the integrated RAID adapter configured as RAID 1. It
arrived already configured.

Good luck with your courses. I would recommend you folks seriously
consider hiring a consultant to at least work out the setup and
structure of your new domain, if not help with the actual
implementation/setup. There are lots of decisions that are made early
that will come back to haunt you if not done right the first time. It
will help teach you the right way to do things. It will be money well spent.

Regards,
Hank Arnold

UWRFREPORTER04 wrote:
I was able to figure it out today. It was rather simple to do. It wasn't my
decision, it was the IS manager, I'm an assistant in college.

It's not being used for anything critical. It's a small (flat) hp server.
It's going to be used for the software of a new security system and that's
all it's going to be used for. We also perform regular back ups.

So for future knowledge it's always best to use a hardware raid controller
because the motherboard is less likely to fail than the OS? Is a hardware
raid typically installed on the motherboard (if you order a server with it)
or do you need to install it yourself? I understand it needs to be set up in
the BIOS.

Sorry for knowing so little, I just started my Win Server 2003 class and my
superivsor knows very little about it. I'm learning as I go and shortly we
are going to set up another new domain for the new location we are moving in
to using win server 2003, and for good or bad, it's going to be on me to know
what I'm doing to set up a small network.

"mtstream" wrote:

I second the "run away". Software RAID can be done but shouldn't. It's
dependant upon the OS so any prblems there and the whole thing is gone (not
to mention the additional overhead). SATA drives also have a very low mean
time to failure rating compared to SCSI or SAS so they are boarderline
quality for servers (depends on what you're using the server for). Sounds
like someone sold you a clone "server". If it's a mission critical box
you're asking for trouble.

"Hank Arnold" wrote:

Argh!!! Run, don't walk away!!! Software RAID is basically useless....

Regards,
Hank Arnold

UWRFREPORTER04 wrote:
I actually found out from another member of the IT staff that it is a
software raid and that it's a feature built into Server 2003.

If anyone has a good link or site to go to that gives good instructions of
how to set this up, it would be helpful.

I think where we had problems is we converted both hard drives into dynamic
and only one is suppose to be converted. Thats' the little bit I understand.


Before doing anything else I suggest you find out exactly what you have on
the server- is it hardware RAID, if so, what is the controller model, how is
it configured, etc. Normally with hardware RAID the RAID configuration needs
to be done before OS installation , using the BIOS, then loading the drivers
via F6 as Cleve mentioned.




.

Relevant Pages

  • Re: HP proliant ML115 G5 on debian lenny
    ... dardrives to do RAID 1 backup for several other servers. ... simple backup server, any drive over 1 GB will hold all the ... system onto a 6 GB partition on one of the drives. ...
    (Debian-User)
  • Re: New Install of SBS 2003?
    ... What if I went with a raid 1 on two drives ... localy and have them install the sofware at my local computer guru's ... I do believe in overengineering ones' server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating to Raid
    ... >>> a RAID Mirroring environment. ... >>It is unclear whether you want to migrate the two existing 200GB drives into ... >uses FC4 as a file server, one uses SUSE as a web server, and one is ... >planning on upgrading to Win 2003 SBS from their existing NT4 setup. ...
    (alt.os.linux.suse)
  • Slow Performance on HP DL380 G4 SmartArray 6i Controller
    ... Hi all, I'm very new to SCSI and server hardware in general, so please ... as we only have the one SCSI RAID HBA in the system then I beleive the ... or the drives or cables attached to it. ...
    (comp.periphs.scsi)
  • Re: Need to migrate system drive from Raid 0 to Raid 1 - HP Smart Array 6400 ML-370 Ghost?
    ... I apologize - you are correct - I am looking to go from Raid 0 to ... I am actually using Windows Server 2003 Standard Edition - ... So you don't think any raid info from the 0 array would be on the ... other logical drives corrected to be Raid 0+1 for the mail store and logs ...
    (microsoft.public.windows.server.sbs)