I wouldn't put the Exchange logs on the C: , if something goes awry with the 
backup not deleting them you could run out of disc space for the OS and make 
the whole machine unbootable. BTDT
John W. Cook
Systems Administrator
Partnership For Strong Families
 Sent to you from my Blackberry in the Cloud

----- Original Message -----
From: Kurt Buff <[email protected]>
To: NT System Admin Issues <[email protected]>
Sent: Sat Oct 17 13:02:07 2009
Subject: Re: New partition

What data lives on the E: drive currently? The answer to that is kinda
crucial to my proposal.

I would, myself, do the following, which is close to what you are
considering, but a bit simpler - you might not even have to reboot
with this procedure after installing the new disks and letting the
RAID build:

1) Install the two new drives, format them and let the new RAID1 disk
get its drive letter

2) Shut down and disable the  Exchange and (if used) SQL services

3) Copy the Exchange and SQL databases to the new disk

4) Give the current E: drive a different letter.

5) Give the new RAID1 disk the E: drive letter

6) You're essentially done. However, if you'd like to recover the
space of the old E: partition, you can, if you wish, delete that old
E: partition that is the neighbor of the C: partition on physical
disk, boot from a gparted live cd and resize the C: drive. At that
point, if the log files for Exchange/SQL aren't already on the C:
drive, I'd consider moving them there.

I don't believe you can extend an OS partition from within the booted
OS - assuming you're running Win2k3. I don't know about Win2k8. Thus
the suggestion for gparted


Kurt

On Sat, Oct 17, 2009 at 04:53, Gavin Wilby <[email protected]> wrote:
> Hi,
>
> I just want to run this past you guys to make sure that what i want to do
> today is clear in my head and I havent forgotton anyhting.
>
> I have a SBS2003 server that has a hardwared mirrored drive on it.
>
> The drive is split into a 20GB partition (c:) for the system to live on and
> a 50GB partition (e:) for data, and Exchange databases to live on.
>
> Im introducing two new disks as a 72GB mirror to the server. This is to be
> the new data store. so what i propose is.
>
>
> Unmount the Exchange stores.
> Stop any services that are using any files on the e: drive.
> Make a note of any shares and permissions.
> Copy all the data from the old e: drive to the new drive (lets just say its
> called z:)
> When thats done and verified, change the drive letters around so the old e:
> becomes x:, and the old z: becomes the new e:
> Remount the exchange stores.
> replace and shares and permissions.
> Once all checked wipe the x: drive and then extend the c: drive into the new
> space.
>
> I have two known good backups of the server, but can anyone see any issues
> with this process?
> --
> Gavin Wilby,
> Twitter: http://twitter.com/gavin_wilby
> GSXR Blog: http://www.stoof.co.uk
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
 Consider the environment. Please don't print this e-mail unless you really 
need to.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to