Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!n8emr!cmhgate!f200.n226.z1.FIDONET.ORG!ADAM.FRIX
From: ADAM.FRIX@f200.n226.z1.FIDONET.ORG (ADAM FRIX)
Newsgroups: comp.sys.mac
Subject: Backup Utility Recommendations...
Message-ID: <40084.25CD0F92@cmhgate.FIDONET.ORG>
Date: 4 Feb 90 06:28:23 GMT
Sender: ufgate@cmhgate.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:226/200 - Aurora Borealis, Gahanna Oh
Lines: 58

In a message of 01/24/90, Richard C. Long wrote:
 
> In article <1990Jan23.174934.4888@ux1.cso.uiuc.edu>,
> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes...
> >[about HFS Backup 3 deleted] make it confused after a while.  It
> >has a lot of nice features; but you can NOT tolerate bugs in
> >backup software.
> 
> That was why I switched from HFS Backup to Redux, which I like
> very much.  I have discovered a possible bug in v1.5, though.
> 
> I did the following :
> 
> 1. Backup entire hard disk.
> 
> 2. Erase said hard disk.
> 
> 3. Restore disk from backups.
> 
> Watch as some files are restored, and others are not.  Redux will
> say something like "xxx files restored, yyy files not restored"
> and "Finished, had problems."  Scrolling back through the restore
> log window indicates no errors.
> 
> The only way I could discover to retrieve the non-restored files
> was to start a backup on the semi-restored hard disk, and look at
> the list of files Redux wanted to delete from the backup set.  I
> then canceled the backup, and explicitly selected those files for
> restore, and it all worked.
> 
> This does not happen to me with v1.01, which I have dropped back
> to.
> 
> Anyone else seen this problem?
 
I spoke with Dave Winzler, author of Redux, and he replied:
 
DW> The usenet message refers to a bug seen occasionally in 1.5 where
DW> it skips over certain files during Restore.  Doesn't happen all
DW> the time, which is why we and the beta testers didn't catch it.
DW> The solution is to use Redux Restore (which is recommended for
DW> restore anyway), or to do what the person suggested.  The problem
DW> is fixed in 1.6, and people shouldn't have any more problems
DW> restoring.
 
I never experienced that bug, either in using 1.5 or in 1.6
betas.  I'm curious:  did this happen to you _regularly_?
 
--Adam--
 
^^^^^
The above statement expresses the views of the individual and does
not necessarily reflect the views or concerns of this place of origin.
 
--  
ADAM FRIX via cmhGate - Net 226 fido<=>uucp gateway Col, OH
UUCP: ...!osu-cis!n8emr!cmhgate!200!ADAM.FRIX
INET: ADAM.FRIX@f200.n226.z1.FIDONET.ORG