Questions and thoughs on SaraB (new user)

Hi!

I'm trying to find a semi-automated backup system for my personal computer. 
Currently I'm poking around with SaraB.

The backups are to be created on a DVD+RW with utilizing the UDF file system 
and the experimental packet writing feature in the Linux 2.6 kernel. I call 
this system semi-automated as it would require me as a user to put in the DVD 
when a backup is to be made as well as clear the DVD when it, after n 
backups, has reached its maximum capacity.

The first problem I ran into with SaraB is that the script is hardcoded to 
create the temporary files in a subfolder to the destination directory. The 
destination directory in my case is /media/cdrecorder thus the temporary 
files would unneccessarily use up space on the UDF filesystem where a file 
only seemingly is deleted but still uses physical disc space (I think..).

My solution was to remove $DESTINATION/ before $WORK in the sarab.sh and in 
the DAR_CREATE variable in sarab.conf. I think this should be implemented in 
SaraB so that the temporary directory can be set independent of the 
destination directory.

One thing that puzzles me with SaraB is that some files seem to be ignored 
when I make backups. Like in this output:

 --------------------------------------------
 8654 inode(s) saved
 with 0 hard link(s) recorded
 0 inode(s) not saved (no file change)
 0 inode(s) failed to save (filesystem error)
 309 files(s) ignored (excluded by filters)
 0 files(s) recorded as deleted from reference backup
 --------------------------------------------
 Total number of file considered: 8963
 --------------------------------------------

However, finding out what files are being ignored or why is still eluding me. 
dar -l showed a bunch of files and directories with size 0 but I am unsure as 
to why those files are recorded in the archive at all!

Another thing I'm thinking about is compression. As I understand, DAR 
compresses files indepenently to reduce problems if a defect in the backup 
medium creates an error in the archive. The thing I don't like with this is 
that it reduces compression ratio. Bzip2 does have some recovery features 
nowadays.. I'd be happier if the archive could be streamed to bzip2 for 
compression.

Finally, I think SaraB should have an option for checking archive integrity 
AFTER it has been moved to the destination (medium). First it could do the 
CRC-check it does now but after copying the archive to $DESTINATION it should 
be compared to the archive in $WORK to ensure the destination medium isn't 
damaged.

Hope someone understands theese ramblings..I am perhaps too tired to try to 
explain.

/ Carl


-- 
http://people.arcada.fi/~englundc
"So slay me now! I have little magic left."
- Kallak, leader of the royal mystics


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl