I can't find reference to this anywhere else, so I'm posing it here in case anyone else has a solution.
I have four 'dar' jobs defined, three of which are manual and one automatic. I am finding that any of the jobs can be manually run, and they work correctly (the backups go into relevant directories etc.)
Now, when the automatic job runs, it starts at the correct time, but the wrong job gets run. The job that does get run is the first one in the list of jobs, rather than the one with the day and time defined.
It could be that the correct job is run, but the wrong name is used. I haven't dug into the code that far yet.
The questions are:
- Is this a known bug?
- Is there a fix?
- Is there a way to get notified of fixes and download them through yum?
A great contrib through. The fact that each backup gets written to its own directory (or should be;-) is a great improvement over backup2, because it now means multiple backups can be kept on one USB disk.
I'm running the latest dar backup contrib, smeserver-dar2-0.0.1-1dmay.noarch.rpm
-- Jason
PS Another little point though, is the destination drop-down in the job setup screen. It lists 'ext3' as the local filesystem option. That is not necessarily the case with a USB disk, as it could have just about any other supported filesystem (I happen to use FAT32, because it means I can read the disk on a Windows machine). Perhaps the label 'local/mounted filesystem' would make more sense that 'ext3', especially to a newbie.
1 Replies
1015 Views