• runallReports

runall reports

Many users would like an activity report from dirvish-runall. Since runall calls separate instances of dirvish for each system, gathering statistics for a report requires a two step process.

My solution was to use a post-server script to parse the dirvish run log. It communicates by appending the data to a permanent summary log that runall reads.

I was forced to modify runall because only it knows the times of the individual backups. I added a client connection check using ping and rsh as I was tired of error messages about my laptop being offline.

runall reads post-server's summary and generates a nice little report that can optionally be mailed to a user. My runall also creates a link to the last successfully completed backup ("last"), since this is where I most often go for recovery.

This is a series of small hacks to the existing dirvish-runall script, but the dirvish backup program is in no way affected. While these scripts have run for months in my environment that doesn't mean they are well tested. Perhaps they can provide a springboard to your own custom solution to the runall reporting problem.