replicating user shares

Goal: have all users shares backed up to a second file server. Have this
done at least daily. If server 1 fails, users can be instructed to work off
another server.

robocopy e:\shares \\server2\e$\shares /MIR /E /SEC /B /MON:1

Currently we run robocopy as a service once an hour to mirror the shares
folder to another. Problem is that we want something to email us if
something fails to backup. Sometimes the service password changes and on
reboot, the service fails. Is there a good way to verify what I'm currently
doing, or is there something built-in to WS2003 I should be taking advantage
of. Thanks.


STFW

Is there a good way to verify what I'm currently
> doing, or is there something built-in to WS2003 I should be taking
> advantage
> of. Thanks.


You should be able to "update" your Win 2k3 SP1 servers to R2. There may be
no charge to do this either.

See:
http://www.microsoft.com/windowsserv...tsnewinr2.mspx

What you are looking for is information on the new features in DFSR that
come with R2.
You can set up a replication group to replicate content to another server,
using namespaces, if one server goes down you can seamlessly access the
second location.

hth
DDS
"STFW" <(E-Mail Removed)> wrote in message
news0948393-9435-4E34-AC89-(E-Mail Removed)...
> Goal: have all users shares backed up to a second file server. Have this
> done at least daily. If server 1 fails, users can be instructed to work
> off
> another server.
>
> robocopy e:\shares \\server2\e$\shares /MIR /E /SEC /B /MON:1
>
> Currently we run robocopy as a service once an hour to mirror the shares
> folder to another. Problem is that we want something to email us if
> something fails to backup. Sometimes the service password changes and on
> reboot, the service fails. Is there a good way to verify what I'm
> currently
> doing, or is there something built-in to WS2003 I should be taking
> advantage
> of. Thanks.