Re: Upgrading RAID 1 Hot Swap Drives on an HP Server



I might suggest leaving the existing RAID1 72 GB as the system partition and
moving all the data files to the new 146 GB Raid1.

The steps are similar, you will have to resize the existing, but the results
vary markedly from breaking the new drives into two partitions.

72 + 146 GB....That ought to hold them for a while.

And if you really wish to be creative, you could break these down more, so
that your exchange db and WSUS, among others might be on their own
partition.

--
Larry

"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F4BD9FA0-AA3C-4468-BEB4-A846F785060F@xxxxxxxxxxxxxxxx
plug in the new drives, create a mirror using the HP tools. Now, launch
Acronis and tell it to "clone" the exisiting drive onto the new one. It
will ask you if it should expand the existing partitions or keep them the
same - expand proportionately. Once it's done, it will tell you to
reboot, disconnecting the old drives. Go into the BIOS setting on the HP
RAID controller on bootup, and point it to the new mirror as the boot
device. (I _think_ that's where HP does it. Been a while since I had to do
that.) I'd unplug the existing drives temporarily, until the system is up
and booted. Now, let it boot up onto the new drives. The old ones can be
re-purposed as desired.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Norm Hughes" <ex-engineerNOSPAM@xxxxxxxxxxx> wrote in message
news:%23H3pJ9IWIHA.4684@xxxxxxxxxxxxxxxxxxxxxxx
It's been a while since I've had to do this, so I'm looking for any
advice which will save me time (and what's left of my hair.) Client has
a HP350 G4 running RAID 1 Hot Swap SCSI 72Gb drives, partitoned into C:
and D: .
The drives are becoming worryingly full (despite deleting and archiving
to other media.) They want to replace them with 146Gb types, retaining
the same partition proportions. The HP has room to install the new
drives along with the existing drives, and Acronis and Shadowcraft tools
are available.

Opinons as to the most efficient way to do this?

Thanks in advance for all responses.
Norm Hughes




.



Relevant Pages

  • Re: Dual Boot Instructions
    ... the PHYSICAL DISK number, ... Partition and Boot Volume as well as other things. ... You should, at any one time, see ONE System Partition and ONE Boot Volume - ... for the typical two floppy drives and assigning Drive C: ...
    (microsoft.public.windows.vista.hardware_devices)
  • Re: dodgy installation - no os found
    ... You could run a benchmark test on the drives and see if the SCSI drive has a good read/write speed. ... caused the system partition to become flaged inactive and I wonder how the WINNT folder being on partition 3 is being enumerated as "C", and even stranger how the active partition is enumerated as "D". ... Turns out the instalation was on partition 3 so did that but then still didn't boot. ... Added the disk to another pc and running disk manager I saw that the system partition was not active. ...
    (microsoft.public.win2000.general)
  • Re: Dual Boot Instructions
    ... If "drive" means a single partition or logical drive, then the negatives you've heard are very true. ... But if "drive" means a physical hard disk drive, then I'm in big trouble because I have SIX versions of Windows installed on my 1 TB Disk 1, my second HDD! ... The name stuck when we added hard disk drives, ...
    (microsoft.public.windows.vista.hardware_devices)
  • Re: BootIt NG high level steps - best approach??
    ... backup boot strategy. ... As far as BING, I should tell you I've been using this software ... make managing your bootable options and partition management so much easier. ... drives) and the DATA partition on a mirrored array. ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: involuntary logical drive in extended partition
    ... the boot device in the BIOS. ... This Root on the bootable drive is the System Partition - up to now, ... But if additional drives are connected before Setup, the new rules can take us by surprise. ...
    (microsoft.public.windowsxp.general)