This week had the misfortune to have two mirrored disks in a SBS2000 server
fail thus rendering the server u/s. I had another W2K server configured as a
domain controller to authenticate users however the main issue was that I
didnt have a backup for the dhcp server so clients could not get the correct
IP address allocation.

Any ideas on how to set this up would be appreciated.

For those who have not ventured down the SBS recovery route yet, I restored
the server from tape using backup Exec 8.5 and the procedure listed on the
veritas web site for manual recovery. I already had this to hand in my
disaster recovery procedures. The only issue that was not listed was the SFN
problem (again I was aware and had supporting documentation to hand) which I
resolved by re-installing affected applications + patches. Only one day down
time wasnt too bad!

Re: Backup dhcp server & SBS recovery by Mark

Mark
Thu Nov 27 12:12:22 CST 2003

Just don't cross scopes. Server 1 - 192.168.1.10-100 and Server2
192.168.1.101-200

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com



"Scott Tacon" <scott.tacon@bcs.org.uk> wrote in message
news:OhjifBQtDHA.980@TK2MSFTNGP10.phx.gbl...
> This week had the misfortune to have two mirrored disks in a SBS2000
server
> fail thus rendering the server u/s. I had another W2K server configured as
a
> domain controller to authenticate users however the main issue was that I
> didnt have a backup for the dhcp server so clients could not get the
correct
> IP address allocation.
>
> Any ideas on how to set this up would be appreciated.
>
> For those who have not ventured down the SBS recovery route yet, I
restored
> the server from tape using backup Exec 8.5 and the procedure listed on the
> veritas web site for manual recovery. I already had this to hand in my
> disaster recovery procedures. The only issue that was not listed was the
SFN
> problem (again I was aware and had supporting documentation to hand) which
I
> resolved by re-installing affected applications + patches. Only one day
down
> time wasnt too bad!
>
>
>