Fundamental Disk Mirror Question

From: Paul Kavanagh (pkavanagh_at_ntlworld.com)
Date: 05/04/04


Date: Tue, 4 May 2004 22:36:43 +0100

I have a Windows 2000 Small Business Server (SP2) which has 2 identical IDE
hard drives which are configured as a mirror set. Each drive is 40GB in size
and the server is configured with a single 40GB C: partition.

I have to do some work to the server and this requires applying SP4 and all
latest updates.

Although I have a good tape backup, I would like to have the "safety net" of
a cloned disk of the complete working system. I know it's obvious that I
already have a cloned disk in the 2nd drive of the mirror set, but what's
the best procedure for me to follow? Should I remove the second drive
(without breaking the mirror in Disk Administrator), boot the server and
apply all patches on the single disk? Will the server even boot in this
config? Will it not look for the second drive?

If it does boot, I apply all patches and things go "belly up" (God forbid!)
can I boot from the 2nd drive with minimal fuss?

I've tried using Symantec GHOST 2002 to clone the mirror set (following
special requirements on symantec site), but it got 25% through the clone
operation and then reported "not enough space on drive d:" (there was!), I
then had no option but to power off the server as I couldn't abort the
operation.

I realise this is a very fundamental question but this server is a live
production unit and I really can't afford the time to rebuild it!!!

Thanks in advance for any help offered,

Paul.



Relevant Pages

  • Fundamental Disk Mirror Question
    ... I have a Windows 2000 Small Business Server which has 2 identical IDE ... hard drives which are configured as a mirror set. ...
    (microsoft.public.win2000.file_system)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Keep in mind that I have seen OEM drivers up there so given that you've blown that image away, I can't say for certain that the 'critical' was 100% pushed by Microsoft. ... External USB is no replacement for local drives. ... LOL I show my naivety here when I say that I showed great diligence in my blind application of any MS suggested resolution to "Critical Errors" on my Small Business Server Monitor Report. ... When I got the first BSOD, I booted from the orginal CD and chose to only restore the System files. ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... information to login to my server remotely to look around--hoping he could ... External USB is no replacement for local drives. ... stored on) and chose to only restore the System files. ... The "Cases" drive was actually a shared folder on an external ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... During the restore, the server rebooted without confirmation. ... The "Cases" drive was actually a shared folder on an external ... I mirrored the two drives ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Before installing this server, my users were accustomed to storing all of ... The "Cases" drive was actually a shared folder on an external ... I mirrored the two drives ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)