Update on sbackup saga

[Dazed_75]

sbackup seems to have good facility for doing scheduled or manual backups to
networked or local storage.  Options are easy to change in the GUI.  The
defaults are to manually backup /var, /etc, /home, and /usr/local excluding
/proc, /tmp, /dev, /var/cache, /var/tmp, /sys and certain file types and
large files to /var/backup.  The first backup is called a .ful although that
is not a traditional full (complete) backup while subsequent backups are
incrementals of the same selections.  After a configurable time, another
.ful is produced etc.

Although sbackup will not write to CD/DVD, I found it easy t use k3b to copy
all backups to a CD or even to add the incrementals to an existing k3b
created CD if mutisession is set to auto in k3b.  The hardest part was
finding that info for k3b.  The other key is that one must use k3b as root
since sbackup makes all the backup directories and files owned and
accessible by root.  Fortunately, the actual files backed up are stored in a
tar file with their original permissions. k3b is also good enough to make
the directories on the CD viewable by all so the CD does not appear to be
unusable.  Security is not compromised because other users can only tell
that the CD is backup material and from when but cannot tell what is in the
backup.

I am less confident of the utility of the restore side.  I say that solely
because there does not seem to be a way to specify a restoration from a .ful
backup and all the available incrementals.  That may be my misunderstanding
but am I wrong to expect that?
-- 
Be who you are and say what you feel, because those who mind don't matter
and those who matter don't mind.  - Dr. Seuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.PLUG.phoenix.az.us/pipermail/plug-discuss/attachments/20061127/ca9ad5cf/attachment.htm