On 1/8/2014 9:15 AM, Florian Heigl wrote: > Hi, > > do you know when you have some itching question that just won’t go away? > > First one: > I know various people (including me) that store to disk, and tried > > Action on Purge = Truncate > > but they all reported that the actual filesystem files did not get truncated > to zero bytes. > Especially when using a Volume just once, this is rather unfortunate. > > So, question: does action on purge = truncate actually work for someone here?
Yes. 'action on purge = truncate' only marks the volume to be truncated. The file on disk is actually truncated by running a console command as: purge volume action=all pool=Some_Pool_Name storage=Some_Storage_Defined_In_Bacula-dir_Config You can use a RunScript to issue this console command after the last job of the day, before the first job, or whatever. > Second one: > Is there a best practice to make sure that Bacula requests a new tape during > daytime? > > (We’re using maximum use duration of 15 days or so, and the problem is that > it usually decides to ask for a new tape some time in the night. > Then, that backup is stalled, until someone switches the tapes, Bacula writes > a few meg on the new tape and then it’s happy. > Sadly that means we’d need to offsite both tapes. > Backup to that tape is done Weekly on Sundays. Maybe it’s just some bad > timing offset we started with? > > What I’d want is that it just asks for a new tape on time :) > > Should I simply make a mail cron job that asks for a new tape on Friday, and > add a little wiggle room on the max duration? The tape's status will not be changed in the catalog until some job runs. The console command 'Status Dir' will also change the status. Keep in mind that the time period starts from the time the first job is written to the tape, not from when the tape was created, last recycled, etc. So if the first job runs at night, then a duration that is an integer number of days will always end at night. The duration need not be an integer number of days. Also keep in mind that changing the duration in the config files applies to new volumes only. Existing volumes will have to be updated using the update volume command. One way is to schedule a short (ie. one file) backup job on Friday during the day and set the Volume Use Duration to expire sometime Thursday night. I don't know if this is best practice, but it queries the operator in the usual way and doesn't rely on cron or external scripts. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
