🚀 go-pugleaf

After a week of fiddling with HFS Backup 3.0 I found the following 
incompatibilities in the HFS Backup 3.0 scheduling process:

1. If Pyro! 3.3 is active, the scheduler will start but after a then,
before doing any backups it will crash with an ID of.

2. The backup set that is to be used with the automatic backup
scheduler must be at the root level, otherwise it will not work.
This was confirmed by a technical support person at PCPC but it is
not documented in the manual.

3. In our environment we have a FastPath kbox running KIP code from
Stanford.  We use a DEC file server as an AppleShare server.  When
trying to do a scheduled backup from a local Mac HD to a folder on
the server, HFS Backup will try to find the files BackupDir or Copy
of BackupDir at the root level even though the backup set was saved
with the folder specification.

4. If the backup is done in Finder format, incremental backup is not
possible.  Furthermore, if a backup set is created with the option of
incremental backup, when trying to execute it HFS Backup will complain
that it cannot find the files BackupDir or Copy of BackupDir, two files
it looks for when doing incremental backup in archive or overwrite modes
and won't do the backup at all.  This fact is not documented in the manual.

Overall the program is the best backup program I've seen so far, but it
need still more work (isn't every program?).

========================================================================
Arie Covrigaru
Cognitive Science and Machine Intelligence Laboratory