Storage strategy suggestions wanted

I need some fault tolerance. A few weeks ago, my domain had a sole W2k3 DC,
which failed taking down the domain. I've added a W2k DC so that the domain
stays running if either DCs fail. This is set up with the W2k3 machine
having the FSMO roles, both DCs storing the global catalog, both running
DNS, WINS, and DHCP (split scope). However, the W2k3 machine died again on
Thursday. Although the domain stayed up I still couldn't work over the
Easter period, which showed me that I need to go further.

I'm using roaming profiles with the profiles and user home directories
mapped to appropriate folders on the W2k3 machine. The W2k3 machine has
other shares that I need to keep available if either of the DCs fail.

Is there a way to have a "domain storage pool" that will always be
transparently available provided that one of the DCs is running? If not,
any other suggestions gratfully received.

TIA,

--
Geoff

At the high end you would want to do clustering with shared disk storage.
Low end you would want to engage DFS and FRS so the profiles are copied
between the servers.

=?Utf-8?B?Sm9zaHVhIEJvbHRvbg==?=
<(E-Mail Removed)> wrote in
news:77EB3C3B-4AED-4DFB-8294-(E-Mail Removed):

> At the high end you would want to do clustering with shared disk
> storage. Low end you would want to engage DFS and FRS so the profiles
> are copied between the servers.
>

Thanks for that. FWIW, I had to ask Google to define both DFS and FRS,
which should give some indication of my experience! Is there an easy "how-
to" somewhere for DFS/FRS? I've had a quick look at the MS site - but what
I found seems to be 2003 R2 specific.

Thanks again,

--
Geoff