I'm just trying to figure out how to use that effectively myself. Right
now, my script runs the verify but always fails. I have to do additional
testing and see where the problems lie, but I would think/expect that good
buisness practice would require a full verify after any backup to ensure
that the backup was done properly and is successful. However, I am not sure
what to do if a verify fails; does one delete the most recent backup and try
again?
The other thing I saw "missing" is a discussion relating to the --volsize
parameter. I have given this a lot of consideration, and I get the feeling
that keeping the backup in a single volume is the best method; my reasoning
being that there would be less chance of finding a corrupt piece. However,
I am not entirely sure about this theory and would love to hear
feedback/comments about it. For my needs, I am backing up to a local NAS so
I don't need to worry about slow network transfers, however, I don't know if
a single volume is good for remote uploads or not. Any thoughts?
Those are my biggest points that I thought of when reading your page.