Re: [Bacula-users] volume selection algorithm again
On 2015-10-31 08:23, Josh Fisher wrote: > Volume selection is fairly complex. The order in which volumes are > purged greatly affects the next available volume selection. With > multiple pools, varied retention times, and occasional error jobs, there > is no way to maintain a static order. While that may be true, this is a brand new install with nothing purged, nothing backed up, one pool, and all volumes available. Not picking the volume in slot 1 is simply bad coding. > Vchanger does not care which volumes are on which magazines as > long as a update slots command is issued to inform Bacula of the moved > volumes. Yeah, that's what I though you'd say ;) Dima -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula for Windows?
Thank you Carlo :) I'm glad this helped. Regards, Ana On Fri, Oct 30, 2015 at 12:08 PM, Carlo Filippetto < carlo.filippe...@gmail.com> wrote: > ANA!!! You are the best! > > :D > > 2015-10-30 15:59 GMT+01:00 Ana Emília M. Arruda : > >> Hello Carlo, >> >> The latest windows binaries released for community use is the 5.2.10. You >> can find more information here: >> http://www.baculasystems.com/windows-binaries-for-bacula-community-users >> >> The status client bconsole command shows the client version at the >> begining of its output. >> >> Best regards, >> Ana >> >> On Fri, Oct 30, 2015 at 11:43 AM, Carlo Filippetto < >> carlo.filippe...@gmail.com> wrote: >> >>> Dears, >>> it is possibile that the last version for windows is the 5.2.10? >>> I upgrade all (Linux client and servers), and I can't find any new >>> *.exe version for Windows >>> >>> Do you know any command to show the version of every client from >>> bconsole? >>> >>> >>> Thank you >>> >>> >>> >>> >>> -- >>> >>> ___ >>> Bacula-users mailing list >>> Bacula-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bacula-users >>> >>> >> > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Copy job with PoolUncopiedJobs
Hello Jerry, On Fri, Oct 30, 2015 at 6:38 PM, Jerry Lowry wrote: > Hi, > > Centos 5.11 64bit OS > Bacula 5.2.6 on all directors and clients > > I have run across a problem with one of my copy jobs. The job is setup > with the PoolUncopiedJobs parameter. The jobs are failing with the > following: > > 30-Oct 11:05 distress JobId 28325: Error: block.c:291 Volume data error at > 3:87310201! Wanted ID: "BB02", got "Í". Buffer discarded. > > (not all of them get the same "got") > > I can understand the error because I had problems with the backup disks > during the date it is trying to copy. > It seems your volumes became unusable by bacula because of the problems with your backup disks. You can always try bls/bextract to recover the data stored in these volumes. Have you already recovered these data? Could these volumes be deleted? If you're getting BB02 error, IMHO It would be a good idea to delete them (phisically and from catalog). This way you will not have volumes in error in your catalog. There is a script ( https://www.mail-archive.com/bacula-users%40lists.sourceforge.net/msg60597/checkVolLabel.sh) that helped once in finding the volumes in error and maybe this could help in finding the ones to delete. Doing this, all the jobs and files associated to these corrupted volumes will be deleted from your catalog and your copy jobs will not try to retrieve data from them. > > Question is, How can I get around these bad backups to the date where the > disks were functioning properly and get them copied to my offsite disk? > > thanks for the pointers. > Hope this helps. Best regards, Ana > > > jerry > > > -- > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Old fileset still showing on restore
Hello, 2015-10-30 10:32 GMT+01:00 Waqar Khan : > Hi All, > > > > I removed an old FileSet definition from my director config but when I do > restore, bacula still thinks its a defined fileset.. Ive restarted sd,dir > and fd for good measure. Here are the steps: > > > > Bconsole -> Restore -> Select the most recent backup for a client -> > MyCLIENT. Then under “The defined FileSet resources are:” its still showing > the old one. > > It is defined in catalog database. Even you remove a fileset from config files you can have some backups which was performed with this fileset, so Bacula gives you information about it. best regards -- Radosław Korzeniewski rados...@korzeniewski.net -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] volume selection algorithm again
On 10/30/2015 2:16 PM, Dimitri Maziuk wrote: > I'm burning in a 7.0.5 (since I don't see 7.2 RPMs in Simone's repo) > server with the latest vchanger and 8 disk "magazines", 3TB each. Here's > what I get backing up a 5+TB filesystem -- note that this is just a > burn-in, not production: > > - full backup runs from 22-Oct 21:05 to 29-Oct 02:36, > - it's done spooling the first volume on Oct 23 01:17 and it writes it > to vchanger_7_9 -- *that is the last volume in the last magazine*, > - and then wakes up and starts writing to mag 0, fills it up, moves over > to mag 1 in sequence. > > This is commodity spinning run disks so I have a post-job script that > rsyncs the last written magazine to another drive (poor man's guard > against drive failure). For that to work, it is very important that a > backup is *not* spread randomly over different magazines. > > Is that even doable with bacula? > > Josh, do you think the ordering could be enforced by vchanger maybe? No. Volume selection is fairly complex. The order in which volumes are purged greatly affects the next available volume selection. With multiple pools, varied retention times, and occasional error jobs, there is no way to maintain a static order. Most likely you will have to change the post-job script to rsync the particular volumes, rather than a magazine. Alternatively, you could manually move volume files between magazines so that all of the volumes that need to be rsync'd are on one magazine. Vchanger does not care which volumes are on which magazines as long as a update slots command is issued to inform Bacula of the moved volumes. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
