On Tue 01 May 2007, Gert Brinkmann wrote: > > When starting to set up the system I ask myself how expiring works. The > problem is that the machine is not running continuously, so I cannot use > a cronjob to start the backup. I want to trigger it manually also > because the external backup drive should be turned off whenever possible.
Dirvish will always keep at least one successful backup image, whatever happens. > expire-rule: > # MIN HR DOM MON DOW STRFTIME_FMT > * * * * 1 +3 months > * * 1-7 * 1 +1 year > > with the explanation: > > the first line has "1" for DOW (day of week), i.e. Monday. Hence backups > made on a Monday will stay around for 3 months. The second line says > that backups made in the first week of the month (DOM = day of month) > won't expire until after one year. > > > Now my question: > > What happens if I did not run a backup on the 1. DOW and none in the > first week of a month? Does dirvish use the next happening backup-image > or is this image-time-slot left blank (so a backup image would be missing)? the expire-rule stuff has nothing to do with time slots or such, only with rules defining when the image should be expired. Dirvish will also always use the last (existing) successful image as a basis for new images. > Or my question asked the other way around: I would like dirvish to keep > all sporadicly run backups for 2 months and one backup per month for 2 > years, independent of the time the backups were taken. Is this possible? You will probably be best off building some wrapper thing that modifies the Expires: line in the images' summary files according to your own wished; that line (and only that!) is used by dirvish-expire to determine whether an image is eligible for deletion or not. You can change that without any problems, as long as you don't break the format of the date/time. Paul Slootman _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
