Arno Lehmann wrote: > Yes and yes ;-) > Depending on what you want.
It to work properly ;) > Admittedly, the best solution would be 'Full Backup Storage=', > 'Differential Backup storage=' and 'Incremental Backup Storage=' > directives in the job resource. Strangely enough I was sat there thinking "I wish there was an equivalent set of directives for Storage as there are for Pools". If people don't mind waiting, I can add them myself; after I've finished work on some code that's apparently due next week but I still haven't been given all the information I need to write it</rant>. > As of now, I decided to go the manual way: I create volumes manually (I > don't use file storage) and, when a job level is automatically elevated, For a couple of the jobs I run I'm doing incrementals every hour and differentials every day (backing up development trees); it makes more sense to use disk storage. They're really not "live" long enough for me to worry about writing them to tape. > I usually notice the stuck backup job in reasonable time and manually > cancel that job and re-run the job with the necessary settings by hand. I normally notice in the morning because it's stuck on the one it upgraded...clearing it seems to be a right royal pain in the proverbial as well. > Arno -- Chris Crowther Developer J&M Crowther Ltd. _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
