SCOUG-HELP Mailing List Archives

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

Date:	Sun, 28 Jul 2002 22:59:21 PST7
From:	"Info2SYNass.NET" <Info@SYNass.NET >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: Drive Image Backups to HDD

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Hello
are you "xcopy"ing from your active partition to another HDD ???

If yes, that's not a good way because the active system does use
many files
so they cannot been copied ;-(

My suggestion is booting from floppies or from a logical
maintenance partition
and then do the xcopy from the specific primary system partition
to the other but
removable HDD !!!

As for me I do not like additional system files or environments
in other partitions
than the active system partition ;-)

I do have an external small SCSI case with an old 1.2GB HDD.
With a full XCOPY version of my [PROD] system I have the
possibility to restore
from that XCOPY backup or I can (top emergency only) start my
system with this
SCSI drive replacing the standard HDD1 ;-))

Like Jordan says: Good to have (my addition: working) Backup
Redundancies !

Regards, svobi

pskye@peterskye.com on 28.07.2002 19.43.01
Please respond to scoug-help@scoug.com
To: scoug-help@scoug.com
cc:
Subject: SCOUG-Help: Re: Drive Image Backups to HDD

Ray Davison wrote:
>
> Regarding saving backups to a hard drive.

I also back up to hard drive; I tried a number of tape
drives over the years but never was happy with them.
(Too many tape errors.)

My backups are quite simple: XCOPY with no compression.
I then run XCOMP to compare the copied files -- for some
reason there are usually a few errors and I have a
little .cmd that lets me recopy the bad files.

http://www.geocities.com/SiliconValley/Pines/7885/Download/XComp2v
310.zip

I backup all machines every day. It takes about 7 hours.
I keep two archives and alternate between them.

I'm not sure what causes the XCOPY failures. There are
about 10 files which always fail, and usually there are
two or three others. The failures are *always* on either
b3 or b4 which indicates a bad cable or connector, but
I've reseated everything *and* it's curious that the
exact same files fail each time (they happen to be my
archive of OS2*.INI files). The failures are always on
just one byte and always either b3 or b4.

I haven't yet logged which byte in the 10 files fails.
If it's the same byte each time, I'll start suspecting
the chipset. Another possibility is flakey memory (in
the old days there could be certain bit patterns which
caused adjacent bits to "flip" -- memory tests were
written so they looked for this problem).

- Peter

************************************************************
*** >>> Say NO to HTML in Mail and News <<< ***
*** ++++++++++++++++++++++++++++++++++++++++++++++++ ***
*** >>> AGAINST TERROR +++ AGAINST WAR <<< ***
************************************************************

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

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
"rollin@scoug.com".

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

Return to [ 28 | July | 2002 ]

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.