Dan Langille wrote: > On 9 Oct 2007 at 20:05, Leon Bruno wrote: > >> On 9 Oct 2007 at 19:54, Leon Bruno wrote: >> >>> Hi all, >>> >>> One of my job is calling a script to do some databases backup. >>> The fileset is then defined to call that same script with another >>> parameter that list the backup that has just been done. >>> >>> >From what I've tested, it seems that the fileset is estimated >>>> before the >>> runbefore task. This is preventing my backup because at the time the >>> fileset is estimated, the backup is not yet done... Is there any way >>> to tell bacula to do the fileset estimation after the runbefore task >>> ? >> Have you considered the estimate command in bconsole? >> >> Would that output be useful for you? > > Leon wrote: > >> Yes I did the estimate command on the fileset and the result is what I >> expected. That's why I believe at the time bacula get the list of >> files to backup, the backup is not yet done, thus the runbefore >> command is actually executed after the fileset has been estimated. > > Please do not reply at the top of the email. > > I do not understand what you need. From the subject, I think you > want to create a FileSet from ClientRunBefore. But I have a hard > time parsing the content of your email to understand your objective. > > I will guess again: If you are trying to dynamically create a > FileSet, I suggest reading this URL: > > http://www.bacula.org/rel-manual/Configuring_Director.html > > And search for this test: > > "There are a number of special cases when specifying directories and > files in a file-list. They are:" > > If that is not what you need, please tell us your goal / objective. > You are asking how "to do the fileset estimation after the runbefore > task". I think you've already decided what the solution is but I > think some context will help us find a solution for you that will > work. >
I might be wrong, but I read this to mean Bruno was having problems because Bacula builds the fileset/filelist it is going to back up before it runs the RunBefore job. However, Bruno's script is designed to do a Database backup first and then provide the fileset information on where this Backup is stored second. As far as I know there is no way to control this behavior, I can see a couple of ways to work around it: 1) Have the actual Database Backup done as part of an Admin job scheduled to occur just before the Bacula Backup job runs. If you are running multiple concurrent jobs this might be hard to implement. 2) Backup the files to a location you can calculate in advance - For example, make every days backup get created in a subfolder named after the date for example. The 'fileset building script' can then easily pass this folder back to Bacula. 3) Have the fileset building process run the backup directly first - No idea whether this would even work, nor exactly how bad an idea it would be. Hope this helps, Troy. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
