SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sun, 28 Aug 2005 18:05:11 PDT7
From:	J R FOX <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: HDD cloning / migration

Content Type: text/plain

--- Peter Skye wrote:

> I'm not trying to tell you how to do your job, but
> resizing a partition
> can be a high blood pressure experience if you get
> any kind of failure
> while it's running. Aren't you better off by
> copying/cloning the
> partition, deleting the old partition and recreating
> it in the desired
> size, and then XCOPYing the files from the
> copy/clone to the new
> partition?

No, not really Peter. I don't think you're following
what I planned to do. Nothing will happen to the
source drive -- it will be kept just the way it is
until I'm certain that it is no longer needed, perhaps
much longer than that. All operations will be
performed on the freshly cloned larger drive. This is
akin to working on a copy of a file, rather than on
the original, just on a much larger scale. If the
copy gets mucked up, you still have the original, and
can try again *on another copy*, probably in a
different way. (Hopefully any failure is clear in the
early going, so not too much time or effort will have
been invested. In this case, that means booting each
Target boot partition, and running a representative
selection of app.s. Also, DFSEE has gotten quite good
about reporting things not right with the drive
setup.) And I do use a UPS.

Jordan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================

Return to [ 28 | August | 2005 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.