[Bacula-users] About Difference between File and Job Retention
Hi All.
I am a newbie of Bacula and learning how to set up Bacula's
configuration files and how the directives of these files work.
For this study, I complied the RPMS of Bacula 5.0.2 from source RPM
and installed them in Redhat EL 5.4.
Now, I am checking File and Job Retention of Client resource.
Both of these directives are explained in Bacula Main Reference.
The manual gives almost same description to these directives,
but I found them work different when auto pruning runs.
When File Retention is set to 0 and the same job is performed twice,
auto pruning induced by the 2nd job deletes the file records of the
1st job.
But when Job Retention is set to 0, auto pruning induces by the 2nd
job doesn't delete any job record of the 1st job. More than that,
no matter how many times the job runs, no job record is deleted by
auto pruning.
# It seems that setting 0 to Job Retention is to prohibit auto
# proning for job records.
The definition of the Client resource for this test is:
Client {
Name = take104-fd
Address = take104
FDPort = 9102
Catalog = MyCatalog
Password = @@ # password for FileDaemon
File Retention = 1000 seconds
Job Retention =0 seconds
AutoPrune = yes # Prune expired Jobs/Files
}
The report about auto pruning showed by messages command is:
27-Jul 14:51 take104-dir JobId 1: Begin pruning Jobs older than 0 secs.
27-Jul 14:51 take104-dir JobId 1: No Jobs found to prune.
27-Jul 14:51 take104-dir JobId 1: Begin pruning Jobs.
27-Jul 14:51 take104-dir JobId 1: No Files found to prune.
27-Jul 14:51 take104-dir JobId 1: End auto prune.
# I tried running the same job five times in a row and
# every run makes the same message.
Is this a feature of Bacula? Is there any reason for this?
Sincerely.
--
Kazuhiro Takenaka
takena...@intellilink.co.jp
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula Status report
On Fri, Jul 23, 2010 at 05:54:03PM +0200, Kern Sibbald wrote: 2. New release cycle: The little code we currently have for the next major release is in the SF bacula git repository under Branch-5.1. We are considering to moving to a regular 6 month release cycle. The advantage of such a cycle is that it gets features out to you faster. The disadvantage is that it doesn't work so well in small projects like Bacula if there are not sufficient contributions. Such a release would consist of the following points: - A release every 6 months Hopefully this means 'major' release every 6 months. - The deadline is not absolute and could be extended to 9 months if there were insufficient new submissions. - There will be far fewer or no bug fix updates as they are not really needed if we can maintain a 6 month cycle. I've read your comments about this from the other emails, but I think it's important to release new *minor* versions for known/important bugs, assuming the fixes are available. - Two months before the projected release we will decide if there are sufficient new features to release - The release count down will consist of 3 phases 1. We will add all new approved features The first 4 months after a release this phase will go into effect for the next release - 2. Only very small new features (a few lines) will be added Two months before the final release this phase will go into effect. Note, this phase can be delayed 3 months if insufficient new features are submitted 3. Only bug fixes This phase will go into effect one month before the release Under this scheme, we are currently in Phase 3 for the 5.0.3 release, and the next major release (5.2.0) would be made before mid-January 2011, and is currently under development in Branch-5.1 on Source Forge. So if 5.0.3 ends up having some bad bug, 5.0.4 should be released before 5.2.0. ie. use most development efforts on the major/master branch, but still maintain stable branch. -- Pasi I would appreciate comments on this proposed new deadline release cycle. 3. New bugs tracking database Sometime in early August (possibly slightly before) we will be moving the current Mantis based bug tracking system to a new RT based system hosted by Bacula Systems. The upside is that the RT system is far more powerful, flexible and adaptible, and most important of all, it allows email responses to bugs. The downside is that it is a bit more complicated (as are most things that have more features) and that it will require everyone to re-register for the new system. In addition, if you don't want to rely on just the community to furnish bug fixes, you will be able to subscribe to a bug fix service that is more professional and has a guaranteed response time (not to be mistaken for a guaranteed fix time). More on this when the service is ready for production. 4. New Bacula server The current Bacula Community server is as you probably know generously offered by UKFast. However, the hardware is starting to age, so they have gratiously provided us with a new machine that we will be putting in place in the next few weeks. We don't expect that you will notice any differences, but the hardware running www.bacula.org should be more stable. 5. New Bacula source distribution server You may or may not be aware that we have not always been pleased with the services offered by Source Forge. The uploading is complicated by lines dropping (I have *never* seen this else where), their user interface is horrible, we don't get good statistics, being US based, they block direct access to our code from a number of countries such as Cuba, ... So, probably in September or October we will be moving our Bacula project off of Source Forge to a new server provided by UKFast. There is still a *lot* of work to be done to make this work -- principally getting up a good and suitable interface for users -- more as this develops. As mentioned above, I would appreciate any comments you might have, particularly on the proposed new release cycle. Best regards, Kern -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Bacula-devel mailing list bacula-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details:
Re: [Bacula-users] About Difference between File and Job Retention
On Tue, 27 Jul 2010 16:02:01 +0900, Kazuhiro Takenaka said:
Hi All.
I am a newbie of Bacula and learning how to set up Bacula's
configuration files and how the directives of these files work.
For this study, I complied the RPMS of Bacula 5.0.2 from source RPM
and installed them in Redhat EL 5.4.
Now, I am checking File and Job Retention of Client resource.
Both of these directives are explained in Bacula Main Reference.
The manual gives almost same description to these directives,
but I found them work different when auto pruning runs.
When File Retention is set to 0 and the same job is performed twice,
auto pruning induced by the 2nd job deletes the file records of the
1st job.
But when Job Retention is set to 0, auto pruning induces by the 2nd
job doesn't delete any job record of the 1st job. More than that,
no matter how many times the job runs, no job record is deleted by
auto pruning.
# It seems that setting 0 to Job Retention is to prohibit auto
# proning for job records.
The definition of the Client resource for this test is:
Client {
Name = take104-fd
Address = take104
FDPort = 9102
Catalog = MyCatalog
Password = @@ # password for FileDaemon
File Retention = 1000 seconds
Job Retention =0 seconds
AutoPrune = yes # Prune expired Jobs/Files
}
The report about auto pruning showed by messages command is:
27-Jul 14:51 take104-dir JobId 1: Begin pruning Jobs older than 0 secs.
27-Jul 14:51 take104-dir JobId 1: No Jobs found to prune.
27-Jul 14:51 take104-dir JobId 1: Begin pruning Jobs.
27-Jul 14:51 take104-dir JobId 1: No Files found to prune.
27-Jul 14:51 take104-dir JobId 1: End auto prune.
# I tried running the same job five times in a row and
# every run makes the same message.
Is this a feature of Bacula? Is there any reason for this?
File and Job pruning work differently for safety reasons.
Pruning files is always safe, because the job remains on the volume and can
still be used to restore files.
Pruning jobs is not safe because a volume can be recycled if it has no
remaining jobs in the catalog.
For safety, Bacula tries to avoid losing all copies of a backup. It will only
prune a job if it can find a similar Full backup that is newer than the Job
Retention period. Setting Job Retention = 0 makes this impossible, so nothing
is pruned.
__Martin
--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] [Bacula-devel] Bacula Status report
On Tuesday 27 July 2010 12:21:01 Pasi Kärkkäinen wrote: On Fri, Jul 23, 2010 at 05:54:03PM +0200, Kern Sibbald wrote: 2. New release cycle: The little code we currently have for the next major release is in the SF bacula git repository under Branch-5.1. We are considering to moving to a regular 6 month release cycle. The advantage of such a cycle is that it gets features out to you faster. The disadvantage is that it doesn't work so well in small projects like Bacula if there are not sufficient contributions. Such a release would consist of the following points: - A release every 6 months Hopefully this means 'major' release every 6 months. It means a release irrespective if it is a bug fix, a minor, or a major release. There are probably not enough submissions to do a major release every six months, which is why I suggested it could be extended to 9 months. - The deadline is not absolute and could be extended to 9 months if there were insufficient new submissions. - There will be far fewer or no bug fix updates as they are not really needed if we can maintain a 6 month cycle. I've read your comments about this from the other emails, but I think it's important to release new *minor* versions for known/important bugs, assuming the fixes are available. Yes, I agree with you, but someone other than me, in many cases, will need to do it. That is someone in the community will need to step forward to do more frequent releases. I have been releasing Bacula for more than 8 years now, and the project has grown sufficiently large, and it is also quite stable. I no longer have the time or energy to make more frequent releases. If you look at the past release history, I doubt that we ever released more frequently than a six month cycle on the average. If you want releases more frequently that fix bugs, then you can get them from Bacula Systems -- they have trained people to do this, but they are on salary and so it costs money to make the releases, which means there is a price. - Two months before the projected release we will decide if there are sufficient new features to release - The release count down will consist of 3 phases 1. We will add all new approved features The first 4 months after a release this phase will go into effect for the next release - 2. Only very small new features (a few lines) will be added Two months before the final release this phase will go into effect. Note, this phase can be delayed 3 months if insufficient new features are submitted 3. Only bug fixes This phase will go into effect one month before the release Under this scheme, we are currently in Phase 3 for the 5.0.3 release, and the next major release (5.2.0) would be made before mid-January 2011, and is currently under development in Branch-5.1 on Source Forge. So if 5.0.3 ends up having some bad bug, 5.0.4 should be released before 5.2.0. That is the way it used to work. It may not work that way in the future. The definition of a bad bug is up to me as long as it is me doing the work for free, and since I am overloaded with work, I won't be very inclined to release something that has a workaround. Doing a release is at least 8 hours of work, and often much more. As I mentioned above, if there are other people in the community who want to take up this workload and do more frequent releases, then I don't see any problem. ie. use most development efforts on the major/master branch, but still maintain stable branch. This is the way we have always worked, and I don't see, at least at this time, any reason to change. Thanks for your comments, Kern -- Pasi I would appreciate comments on this proposed new deadline release cycle. 3. New bugs tracking database Sometime in early August (possibly slightly before) we will be moving the current Mantis based bug tracking system to a new RT based system hosted by Bacula Systems. The upside is that the RT system is far more powerful, flexible and adaptible, and most important of all, it allows email responses to bugs. The downside is that it is a bit more complicated (as are most things that have more features) and that it will require everyone to re-register for the new system. In addition, if you don't want to rely on just the community to furnish bug fixes, you will be able to subscribe to a bug fix service that is more professional and has a guaranteed response time (not to be mistaken for a guaranteed fix time). More on this when the service is ready for production. 4. New Bacula server The current Bacula Community server is as you probably know generously offered by UKFast. However, the hardware is starting to age, so they have gratiously provided us with a new machine that we will be putting in place in the next few weeks. We don't expect that you will
Re: [Bacula-users] Error BB02. Volume created successfully?
John, What should the timing look like? Something I can set in storage.conf in case this is the issue? Thanks, JJ -Original Message- From: John Drescher [mailto:dresche...@gmail.com] Sent: Monday, July 26, 2010 4:30 PM To: Jeremiah D. Jester Cc: bacula-users Subject: Re: [Bacula-users] Error BB02. Volume created successfully? 2010/7/26 Jeremiah D. Jester jj...@u.washington.edu: I'm getting a bunch of error messages stating a Volume data error when I run 'label barcodes'. John Drescher advised me to rewind that tape and write and eof to clear the data. However, in this case I did notice that the last line of output states that it was the volume was created successfully. Interesting enough the volume does not appear when I issue a 'status slots'. Any thoughts on this? Here is the full error message output for one of the volumes. Thanks, JJ Sending label command for Volume KL0433 Slot 14 ... 3307 Issuing autochanger unload slot 13, drive 1 command. 3304 Issuing autochanger load slot 14, drive 1 command. 3305 Autochanger load slot 14, drive 1, status is OK. block.c:275 Volume data error at 0:0! Wanted ID: BB02, got . Buffer discarded. 3000 OK label. VolBytes=64512 DVD=0 Volume=KL0433 Device=Drive2 (/dev/nst1) Catalog record for Volume KL0433, Slot 14 successfully created. Can you look in the log for the timing. Normally the time is listed by each message. I want to see if the system is giving the load enough time. John -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Error BB02. Volume created successfully?
What should the timing look like? Something I can set in storage.conf in case this is the issue? It should take at least 1 minute probably closer to 2 minutes to load the tape. Was worried that mtx-changer was completing before the volume was actually loaded. This was just a guess.. John -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Bacula license changed from GPLv2 to AGPLv3
Hello, This is to let you know that we, with the agreement of the Free Software Foundation Europe, have changed the Bacula license from GPLv2 with some exceptions (allow linking with OpenSSL + Windows, ...) to AGPLv3 with the same exceptions. This was done to help ensure that users whose files are backed up by ISPs using Bacula or cloud providers can request any modifications the service providers make to Bacula. The next versions of Bacula, namely Bacula Enterprise 4.0.1 released today, and Bacula community 5.0.3 to be release during the month of August will be released on the new license. The modifications to the LICENSE and the source copyrights have been pushed to the Source Forge get repository. Best regards, Kern -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] cannot find any appendable volumes
On 7/26/10 12:13 PM, John Drescher wrote: snip Did it try to use B002 and fail? John Both B001 and B002 are in the changer. I tried loading each of them in the drive, and after each time running the mount command in bacula, but I just keep getting the message that there are no appendable volumes. Did you change the status of these volumes after the job started? John So, I just tried moving a volume from my scratch pool to my Servers pool, and pruned it. Bacula marked it purged. I then ran the mount command, and again I got the message that there are no appendable volumes: *messages 27-Jul 14:35 billie-sd JobId 1700: Job MailBackup.2010-07-25_01.10.00.28 waiting. Cannot find any appendable volumes. Please use the label command to create a new Volume for: Storage: Drive-1 (/dev/st0) Pool: Servers Media type: VXA-2 *list volumes pool=Servers +-++---+-+-+--+--+-+--+---+---+-+ | MediaId | VolumeName | VolStatus | Enabled | VolBytes| VolFiles | VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | +-++---+-+-+--+--+-+--+---+---+-+ | 8 | A007 | Purged| 1 | 123,725,887,488 | 196 | 864,000 | 1 |7 | 1 | VXA-2 | 2009-06-26 11:10:47 | | 10 | A010 | Full | 1 | 85,035,073,536 | 94 |2,592,000 | 1 |9 | 1 | VXA-2 | 2010-07-04 04:21:32 | | 11 | B001 | Recycle | 1 | 1 | 0 |1,814,400 | 1 |2 | 1 | VXA-2 | 2010-06-27 06:48:34 | | 12 | B002 | Append| 1 | 0 | 0 |2,592,000 | 1 |5 | 1 | VXA-2 | 2010-06-13 05:50:03 | | 31 | C006 | Full | 1 | 71,120,738,304 | 76 |2,592,000 | 1 |8 | 1 | VXA-2 | 2010-07-23 16:15:26 | +-++---+-+-+--+--+-+--+---+---+-+ What the heck could be going on here? I have recently ran into some weirdnesses with my setup. Everything had been running fine for a long time, and then when I rebooted the machine, the tape drive showed up on a different device address. I had to change this, and then it appeared that suddenly there were some strange problems with my config file, which I fixed (stuff like it suddenly didn't like upper case letters, where apparently it didn't care before). But, now I have run a couple of successful backups since then, until I ran into this weirdness, and I'm not sure what to do... Using bacula 2.4.4-1 on debian lenny. -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] bconsole command to display jobs on volume
Hello, I'm using bacula-5.0.2. Is there a way in bconsole to see which jobs used a particular tape? I can run list jobmedia, save the output to a file and then grep for the media name but it's a lot of steps and it shows only the jobid. Thanks Peter -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bconsole command to display jobs on volume
On 27/07/10, Lamp Zy (lam...@gmail.com) wrote: Hello, I'm using bacula-5.0.2. Is there a way in bconsole to see which jobs used a particular tape? I can run list jobmedia, save the output to a file and then grep for the media name but it's a lot of steps and it shows only the jobid. The following is a generic SQL query that I think might do what you want. SELECT j.name as jobname, m.volumename as volname, p.path as path, fn.name as filename FROM job j, media m, file f, jobmedia jm, filename fn, path p WHERE jm.mediaid = m.mediaid AND jm.jobid = j.jobid AND jm.startfile = f.fileid AND f.pathid = p.pathid AND f.filenameid = fn.filenameid; This might be worth saving as a view. In Postgres you would do something like: CREATE VIEW v_job_vol_path_name AS query body as above You could then query it to find jobids by media like this: SELECT distinct(jobname), volname FROM v_job_vol_path_name ORDER BY jobname, volname; You can also use this view to find which files are on which jobs, which are on which tapes and son on. I hope this helps. Rory -- Rory Campbell-Lange r...@campbell-lange.net -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://ad.doubleclick.net/clk;226879339;13503038;l? http://clk.atdmt.com/CRS/go/247765532/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
