[dba-Tech] Ghosting an old HD to a New HD

I did a similar thing about a year ago. I had an 80gb drive and a 30gb
drive. I swapped the 30 for a 120, and ghosted the 80 onto it. Then I
partition magic'ed the drive up to 120 instead of the copied 80gb
partitions, and put the 80 in as a d drive... Worked fine for me, using
win2k.


Jon

-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: 05 March 2006 00:08
To: 'Discussion of Hardware and Software issues'
Subject: [dba-Tech] Ghosting an old HD to a New HD

My main squeeze has twin 80 GB drives. Today I bought a 250 GB drive. I want
to burn the image of c:\ to the new drive, then swap them, reboot and be
back where I was a few minutes ago with everything working correctly.
I have an ancient version of Ghost. The current setup is NTFS everywhere.
The ancient version alleges to support NTFS but if memory serves there was a
change a few years back in the NTFS structure; so I am a teensy bit nervous
that the old version won't support the changed structure.
My plan thus far is this (dictated by the complete absence of free space
anywhere): unplug HD #2 (d:\), replace it with the big new drive, run Ghost
or Partition Magic and copy everything from c:\ to the new drive, then swap
the new drive for the old drive c:\, reboot and experience joy.
Before I do anything, I request some feedback -- an assurance this will
work, a better approach, whatever. I am NOT a hardware guy. I prefer to
confine my perspective to the subtleties of SQL etc. The current box has
twin 80 GB disks, both of which have about 6 GB free. Ideally, I would like
to move everything from the existing c:\ to the new disk, then do the same
with everything on the d:\ disk (but I expect that to be more complex, since
numerous pointers will be looking for d:\ not c:\). On Step Two I don't care
to do it immediately, since it will continue to work as is, assuming that I
correctly image existing drive c:\ to the new drive, then remove the old
drive and plonk in the new one.
Holes in logic?
Superior strategies?
More optimized solution?
All advice gratefully accepted.
(I also have a CD burner and a DVD burner connected. Perhaps I should unhook
one of these rather than d:\ and go about it that way.)?
TIA,
Arthur

_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com
--
This email has been verified as Virus free Virus Protection and more
available at http://www.plus.net