[Bacula-users] automatic purge/delete volumes on full 'File' storage
Hello everyone. Tell me, please, how in the bacula possible to automate the process of automatic removal (or reuse) volumes, and, of course, prune jobs in database, when storage with 'File' type is completely full? In my case jobs/volumes retention period is 2 month, but disk filled before two months elapsed. I would prefer actions when early volumes/jobs will be purged, even without waiting for 2 months of storaging, but not a situation where, for example, "Device is BLOCKED waiting for mount of volume" users-0213 "" in the case where the disk filled. I'll be glad to any proposals that may resolve this situation. Thank you :) -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On 10/28/2014 01:46 PM, Alan Brown wrote: > On 28/10/14 18:39, Dimitri Maziuk wrote: >> (As an aside, bacula, specifically, seems to force you to use different >> Media Type for each physical device so I don't get how it would work >> with multiple drives in the same jukebox, either -- thankfully I don't >> need to.) > > It's been more than happy to set the media type to LTO-5 on 7 drives, > LTO-2 on 2 (different changer) and LTO-6 on another. > > What it can't handle is that you can load media types LTO4 RW in the > LTO5 drives and also LTO3 RO, which would be extremely handy. We used ait-1 tapes in ait-3 drive with notworker and just ignored the "premature eot" (or whatever it was) barf. But I was referring to Kern's > Message-ID: <518dd7f5.7080...@sibbald.com> > Date: Sat, 11 May 2013 07:32:37 +0200 > From: Kern Sibbald > Subject: Re: [Bacula-users] backup to multiple disks ... > Yes, Media Type is very important. It must > be in the Storage resources on the Director > side, and notice that as I mentioned before, on > the SD side, Autochanger really just groups a > number of Devices. The Media Type must be > in each Device, because each one can be different > so it is not in the Autochanger resource. > > There is no restriction for multiple devices to have > the same Media Type, but if they are disk devices > and don't have the same Archive Device, Bacula > won't be able to "mount" them. So, use the same > Media Type only in Devices that have the same Archive > Device. I expect someone had reasons to code it that way for disk devices specifically, and they may even seemed good at the time -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On Tue, Oct 28, 2014 at 3:46 PM, Alan Brown wrote: > On 28/10/14 18:39, Dimitri Maziuk wrote: > > What it can't handle is that you can load media types LTO4 RW in the > LTO5 drives and also LTO3 RO, which would be extremely handy. > > You can get this just defining two device that references the same drive: one that will work with LTO4 tapes and the other will work with the LTO5 tapes. I have this configured and it is working fine. The same tape library reads/writes LTO-3 and LTO-5 HP tapes. Is this could be best configured? Yes, I think. If we could set "Media type = LTO-3. LTO-4". But this is still not implemented and I´m not sure about the difficulties this should represent. Because in database we have a volume (tape) associated with a media type. Maybe if we could have another "media type" directive for pools. So we could say: this device can read/write LTO-4 and LTO-5 types, but the volumes in this pool are from media type = LTO-5. > > > > > > -- > ___ > 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] Configuration reload for bacula-sd
On 28/10/14 18:39, Dimitri Maziuk wrote: > There is no reason to see file volumes as dedicated to a client AFAICT; Habit, I suspect. It's a bad one, given there's a database driving everything to tell you what is where. > (As an aside, bacula, specifically, seems to force you to use different > Media Type for each physical device so I don't get how it would work > with multiple drives in the same jukebox, either -- thankfully I don't > need to.) It's been more than happy to set the media type to LTO-5 on 7 drives, LTO-2 on 2 (different changer) and LTO-6 on another. What it can't handle is that you can load media types LTO4 RW in the LTO5 drives and also LTO3 RO, which would be extremely handy. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On 10/28/2014 01:04 PM, Alan Brown wrote: > > Block devices may be block devices, but a tape drive is a character device. Oops. Works either way, disks are char aka "raw" devices too. > People coming from a tape environment tend to see tapes (volumes) as > something you use for a pool of clients or filesets, because changing > volumes is NOT trivial, the tapes are only reated for a limited number > of load cycles and you can only access one volume at a time. > > If you have more tape drives you can access more volumes simultaneously, > but changing volumes is no less difficult/timeconsuming. As is changing disks. Skipping from one tarball to another on tape may take much longer, but that shouldn't make any difference to the higher-level code. There is no reason to see file volumes as dedicated to a client AFAICT; those who want it can do pool per client and volumes per pool -- works with tapes just as well. Yes, in general you can access multiple files on the same disk simultaneously. I don't expect that a backup application streaming data to or from that disk would -- or should -- actually do that, for any number of obvious reasons. Which is why I'll never understand the tape/disk dichotomy. (As an aside, bacula, specifically, seems to force you to use different Media Type for each physical device so I don't get how it would work with multiple drives in the same jukebox, either -- thankfully I don't need to.) -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On 28/10/14 14:59, Dmitri Maziuk wrote: > OT comment: I'll probably never understand that, I always thought a > block device is a block device and one of the unix's strong points was > to abstract away the physical differences and let the same code work > with either. Block devices may be block devices, but a tape drive is a character device. > AFAICT the only reason they're different (in how SD treats > them) is because the software is written that way... It's more about the way people approach the configuration and that has much more to do with sequential vs random access and device naming conventions. People coming from a disk-environment tend to see files on disks (volumes) as dedicated to a client, because you can trivially skip from volume to volume and access multiple volumes simultaneously. People coming from a tape environment tend to see tapes (volumes) as something you use for a pool of clients or filesets, because changing volumes is NOT trivial, the tapes are only reated for a limited number of load cycles and you can only access one volume at a time. If you have more tape drives you can access more volumes simultaneously, but changing volumes is no less difficult/timeconsuming. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
I´m very very sorry. I´m not presuming to lecture you about what you should do or should not be doing in your enterprise environment. Maybe my english was too bad to lead to this embarrassment situation. I was just trying to find, colaboring with all the others here, a solution for your case, with the current version of the software. Also, like all the others, give feedback about things . It is my believe this is the great objective of this list. On Tue, Oct 28, 2014 at 10:24 AM, Alan Brown wrote: > On 28/10/14 12:46, Ana Emília M. Arruda wrote: > > , maybe >> > a second device definition for a job or pool could be more helpful than >> a bacula-sd.conf reload on-the-fly or the enable/disable commands. >> > > This does not work. I've tried it. > Yes, I´m aware that this does not work. It was a suggestion for adding in new versions because I´was not understanding the whole thing. > > Thankfully Kern and his team are well aware that needs vary depending on > setups and that multiple-tape drive setups need improvement. > > Yes, Kern and his team are always aware of all the suggestions and demands discussed here. Best regards, Ana -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On 10/28/2014 9:24 AM, Alan Brown wrote: > On 28/10/14 12:46, Ana Emília M. Arruda wrote: > > >> , maybe >> a second device definition for a job or pool could be more helpful than >> a bacula-sd.conf reload on-the-fly or the enable/disable commands. > This does not work. I've tried it. > > If an autochanger tape drive fails, jobs pile up behind it. > > What's far worse than a drive failing is one getting dirty - they spend > forever doing rewrites and througput drops from hundreds of Mb per > second to 10-20, WITHOUT raising errors in the backup system - and > running a cleaning tape doesn't work in a lot of cases (LTO drives are > self cleaning, If you need a tape then you're already in trouble) > > This is far from ideal behaviour, especially when there are petabytes of > science data involved. Granted. But that sort of hardware failure must be handled at the device driver level. Bacula cannot be blamed for the device driver not raising an error, and the same behavior would be observed regardless of user mode software used. > The only way out of either situation at the moment involves restarting > the storage daemon, which kills ALL jobs running on ALL drives. Have you tried the umount command in bconsole? umount will close the device and allow using mt or whatever tools to fix the problem. A subsequent mount command will re-open the device. If a new or different tape has been inserted, then the mount command will cause the volume label to be read. The current job will likely have to be canceled, unfortunately. Nevertheless, it is often possible to fix a drive issue without restarting bacula-sd. Ideally, there would be some way to declare all data written to the failing tape invalid and cause Bacula to restart the job from the point where data was first written to the failed tape, though I don't know if that is currently possible. And what about other jobs that have already successfully written to the now failed tape? > Comment: Please don't presume to lecture me about what I should or > should not be doing in my enterprise environment, or indeed about the > way systems are setup (it's all fabric path for starters and bacula does > not do d2d unless you count disk spooling - which we use intensively), > you have no idea of the operational constraints on my site and you're > making a bunch of fairly arrogant assumptions about the way things are > run which impinge on the way you think Bacula should operate. > > It's this kind of attitude which results in inflexible software that > gets sworn at, rather than sworn by. > > > Thankfully Kern and his team are well aware that needs vary depending on > setups and that multiple-tape drive setups need improvement. Absolutely. It is still evolving. > Tape and disk are different animals and need to be approached differently. > > Virtual autochangers are a kludge to allow for removable disks but in > most configured installations they do _not_ treat those disks in the > same way as real tape drives. > I don't entirely agree. For the most part, Bacula sticks to the Unix principle of "everything is a file". Standard C library file i/o is used. Once the file is opened, whether device file or filesystem file, it is treated in exactly the same way by Bacula. Any difference is due to the device and/or filesystem drivers and is beyond Bacula's control, as it should be. If there are problems with the device driver and/or device firmware not detecting error conditions, then a bug report is in order. That said, there is room for improvement in how media errors, once detected, are handled. It would be nice to be able to restart jobs from the point at which data was first written to a particular tape, since by Murphy's Law, the failing tape tends to be the last tape needed. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On 10/28/2014 8:24 AM, Alan Brown wrote: ... > Tape and disk are different animals and need to be approached differently. > > Virtual autochangers are a kludge to allow for removable disks but in > most configured installations they do _not_ treat those disks in the > same way as real tape drives. OT comment: I'll probably never understand that, I always thought a block device is a block device and one of the unix's strong points was to abstract away the physical differences and let the same code work with either. AFAICT the only reason they're different (in how SD treats them) is because the software is written that way... Dima -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On 28/10/14 12:46, Ana Emília M. Arruda wrote: > You have autochangers resources (fisical for tape librareis and virtual > for disks) in Bacula. They are a "pool of drives" to be used by your > jobs. I still think about having jobs and pools associated with clients > instead of devices associated with clients are the better choice. Devices are not associated with any clients. They're used as-available. Tying devices to clients is an unnecessary restriction on resources and generally indicates accountants gone mad or lack of thought about what you are trying to achieve. > In spite of this, If you have to work with tape drives (stand alone or > tape library ones connected directly - not in a fabric topology) They are fabric connected. >, maybe > a second device definition for a job or pool could be more helpful than > a bacula-sd.conf reload on-the-fly or the enable/disable commands. This does not work. I've tried it. If an autochanger tape drive fails, jobs pile up behind it. What's far worse than a drive failing is one getting dirty - they spend forever doing rewrites and througput drops from hundreds of Mb per second to 10-20, WITHOUT raising errors in the backup system - and running a cleaning tape doesn't work in a lot of cases (LTO drives are self cleaning, If you need a tape then you're already in trouble) This is far from ideal behaviour, especially when there are petabytes of science data involved. The only way out of either situation at the moment involves restarting the storage daemon, which kills ALL jobs running on ALL drives. Comment: Please don't presume to lecture me about what I should or should not be doing in my enterprise environment, or indeed about the way systems are setup (it's all fabric path for starters and bacula does not do d2d unless you count disk spooling - which we use intensively), you have no idea of the operational constraints on my site and you're making a bunch of fairly arrogant assumptions about the way things are run which impinge on the way you think Bacula should operate. It's this kind of attitude which results in inflexible software that gets sworn at, rather than sworn by. Thankfully Kern and his team are well aware that needs vary depending on setups and that multiple-tape drive setups need improvement. Tape and disk are different animals and need to be approached differently. Virtual autochangers are a kludge to allow for removable disks but in most configured installations they do _not_ treat those disks in the same way as real tape drives. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Configuration reload for bacula-sd
On Mon, Oct 27, 2014 at 7:25 AM, Alan Brown wrote: > On 24/10/14 23:27, Ana Emília M. Arruda wrote: > >> Maybe this could be usefull. But I'm still trying to understand why are >> you using disk drives directly in archive device configuration. >> > > We don't. We use tape drives. IMHO. You have autochangers resources (fisical for tape librareis and virtual for disks) in Bacula. They are a "pool of drives" to be used by your jobs. I still think about having jobs and pools associated with clients instead of devices associated with clients are the better choice. In spite of this, If you have to work with tape drives (stand alone or tape library ones connected directly - not in a fabric topology), maybe a second device definition for a job or pool could be more helpful than a bacula-sd.conf reload on-the-fly or the enable/disable commands. I mean, if the first drive designated for the job or the pool falis (director could check if no response is received, like it already does) and then director instructs the use of the second drive, present in job or pools definition of storage (Storage = Drive-1, Drive-2). This way it is not necesary to reastart the failed job (once it could not run because of the drive failure) and you can have enough time to change the crashed drive and no changes in bacula-sd.conf would be necesary since you will have symlinks for the archive device configuration. > > I also think that backup software cannot be aware of hardware faliures. >> > > I _strongly_ disagree, especially in an enterprise-scale setup. > Sorry Alan, in an enterprise-scale setup, you need, as I mentioned before, other fault tolerance levels (disk-to-disk backups in storage arrays before disse-to-tape backup, raids, multipaths, etc.). Best regards, Ana -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Webacula 7. Coming…
Hello,
It is not particularly easy to parse Bacula configuration files,
particularly the FileSet resource, and I am not sure it can be done with
regex. However, Bacula does read its own conf files, and there is a
program named DassModus (posted on Internet) that reads Bacula conf
files in Python partially using regexes ...
Concerning your "conf" file listed below. I am 99% sure it is not a
valid conf file and could not even be scanned by Bacula.
If you are worried about all the things that Bacula permits such as
spaces in names, simply define a simpler Bacula syntax where names
cannot have spaces. Another way is to choose your own format (such as
xml, which as you know, I do not like) and use it since it is easy to
parse with web tools, then convert it into Bacula syntax before giving
it to Bacula. Converting xml, json, or any other representation into
Bacula should be a lot easier than going the other way.
Best regards,
Kern
On 14-10-28 04:19 AM, Yuriy Tim wrote:
I kept my old letter (2011 :)
I tried to parse the bacula-dir.conf.
However, this is probably not possible with simple regexp's.
It turned out that some applications, for example, Webmin does this
with a regexp.
But they're doing it wrong!
For example, here is test configuration (which is written according to
"Bacula Main Reference: Customizing the Configuration Files")
contains no errors in terms of Bacula (I checked it) but it would be
wrong parsed (I have not tested it, but I'm sure of it) by 3rd parties
parsers (not native) :
-
# comment1
# comment2
c o n s o l e
{ Name=name1; Password = "p; \\\a s s w o rd"; J o b A C L = *all\*
}Con sole { N a m e = "name 2"; Pass word = "password"; JobACL =
job/\1, job2, job3
}
-
I.e. in other words to parse with regexp any Bacula configuration will
be very difficult.
2014-10-28 7:08 GMT+03:00 Victor Hugo dos Santos >:
On Sat, Oct 25, 2014 at 3:09 PM, Kern Sibbald mailto:k...@sibbald.com>> wrote:
> On 14-10-05 03:36 AM, Yuriy Tim wrote:
>
> What I have in mind:
> 1 store all config files in the database
> 2 to store all the jobs in the database (for example, scheduled
tasks, and
> not only already made)
> 3 to store other information in the same database
> 4 to have a function that preserves the tree to the the database
for select
> the files and restore. Now it makes BVFS,but for Web-UI is useless.
>
> I once wrote in the bacula-devel but
>
> Bacula "configuration files editing" ? NOO! :)
>
>
> I am not sure why any one would object to doing configuration
file editing
> in a Web based GUI -- we have that in Bacula Enterprise. Also
who you asked
> to program it and when could make a big difference in the
response ...
>
> Where I am not very enthusiastic is to put the configuration
files in the
> SQL database. This would make it harder to recover Bacula
during disaster
> recovery, and if you destroyed your database, it could make it
impossible to
> even start Bacula.
Hi
I think the same with you about the posibility to store the
configuration in database (is a very, very, very bad idea) !!!
but, maybe the idea of this mail (If not, Yuriry can use this idea to
improve webacula) is to use a database to save all the hosts, files,
storages and others "only to webacula" interface... After the end, the
user will apply the changes and so, the GUI get all the information
from the database and generate a new bacula-dir.conf for example.
that is the same idea that the Centreon project use to make the nagios
configuration files, and IMHO, I believe that is a good idea.
salu2
--
--
Victor Hugo dos Santos
http://www.vhsantos.net
Linux Counter #224399
--
with best regards
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Inconsistent backups of windows clients
On 28/10/2014 5:30 PM, Florian wrote: > Hello again. > > So, after maybe 4 days, one of the clients again randomly couldn't be > reached, so apperently adding 30 seconds sleep between wake-on-lan and > backup didn't help... > Your network environment is slow. The network topology is dodgy, or it simply takes a long time for the clients to establish their existence. Have the problematic jobs sleep for 2 minutes after waking the machines, and do a traceroute to them at that time to see if they really are accessible. Cheers, GaryB-) -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] How to mask spaces in script?
Florian, Yes, you can mask any shell special character in bacula confs with \. Regards, -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br Em 28 de outubro de 2014 04:51:57 BRST, Florian escreveu: >Hello, everyone. > >I have a small problem: >I went to start a script on a windows client after a backup was done. >The script is located at "C:\Program Files\Bacula\ShurdownScript.bat" > >I know I can mask the \ with a second \, but can I do that with the >space in "program files", too? > >Regards, > >Florian S. > >-- >___ >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] Inconsistent backups of windows clients
Just in time: "s/Retry on Error/Reschedule on Error/g" -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br Em 28 de outubro de 2014 05:41:45 BRST, Heitor Faria escreveu: >Mr. Florian, > >Hey... I'm glad you tried my sugestion. lol >Maybe could you try more something like 60 secs? Some machines may take >some time to turn on. >As a workaround, alternativaly, you could use the Retry on Error >option, in order to assure the backup execution in the time frame you >need. >-- >Heitor Medrado de Faria >+55 61 82684220 >Precisa de treinamento Bacula presencial, telepresencial ou online? >Acesse: http://www.bacula.com.br > >Em 28 de outubro de 2014 04:30:23 BRST, Florian >escreveu: >>Hello again. >> >>So, after maybe 4 days, one of the clients again randomly couldn't be >>reached, so apperently adding 30 seconds sleep between wake-on-lan and > >>backup didn't help... >> >>Here is the whole log. Maybe this has any hint in it that I don't see? > >>(sorry for german languege) >> >>27-Okt 23:00 ubuntu-dir JobId 214: shell command: run BeforeJob >>"powerwake XXX" >>27-Okt 23:00 ubuntu-dir JobId 214: BeforeJob: INFO: Trying to wake >>host: [XXX] >>27-Okt 23:00 ubuntu-dir JobId 214: BeforeJob: INFO: Sending magic >>packet to: [X] >>27-Okt 23:00 ubuntu-dir JobId 214: shell command: run BeforeJob "sleep >>30s" >>27-Okt 23:00 ubuntu-dir JobId 214: Start Sicherung JobId 214, >>Job=Backup_WS-005.2014-10-27_23.00.01_51 >>27-Okt 23:00 ubuntu-dir JobId 214: Using Device "BackupDevice_WS-005" >>to write. >>27-Okt 23:03 ubuntu-dir JobId 214: Warning: bsock.c:112 Could not >>connect to Client: WS-005_fd on 192.168.1.105:9102. ERR=Unterbrechung >>während des Betriebssystemaufrufs >>Retrying ... >>27-Okt 23:03 ubuntu-dir JobId 214: Fatal error: bsock.c:118 Unable to >>connect to Client: WS-005_fd on 192.168.1.105:9102. ERR=Unterbrechung >>während des Betriebssystemaufrufs >>27-Okt 23:03 ubuntu-dir JobId 214: Fatal error: FD hat keinen >Jobstatus >>zurückgegeben. >>27-Okt 23:03 ubuntu-dir JobId 214: Error: Bacula ubuntu-dir 7.0.5 >>(28Jul14): >> Build OS: x86_64-unknown-linux-gnu ubuntu 12.04 >> JobId: 214 >> Job:Backup_WS-005.2014-10-27_23.00.01_51 >> Backup Level: Incremental, seit=2014-10-26 23:01:01 >>Client: "WS-005_fd" 5.2.10 (28Jun12) Microsoft Windows >>7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64 >> FileSet:"Standard Windows Set" 2014-09-23 23:00:00 >> Pool: "Pool_WS-005" (From Job Ressource) >> Catalog:"StandardCatalog" (From Client resource) >> Storage:"Storage_WS-005" (From Job Ressource) >> Scheduled time: 27-Okt-2014 23:00:01 >> Start time: 27-Okt-2014 23:00:33 >> End time: 27-Okt-2014 23:03:43 >> Elapsed time: 3 mins 10 secs >> Priority: 10 >> FD Files Written: 0 >> SD Files Written: 0 >> FD Bytes Written: 0 (0 B) >> SD Bytes Written: 0 (0 B) >> Rate: 0.0 KB/s >> Software Compression: None >> VSS:Nein >> Encryption: Nein >> Accurate: Ja >> Volume name(s): >> Volume Session Id: 34 >> Volume Session Time:1413870076 >> Last Volume Bytes: 17,056,640,116 (17.05 GB) >> Non-fatal FD errors:1 >> SD Errors: 0 >> FD termination status: Error >> SD termination status: Waiting on FD >> Termination:*** Sicherungsfehler *** >> >>Regards, >> >>Florian S. >> >> >> >> >> >>-- >> >> >> >> >>___ >>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 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Migrate: copy or duplicate?
Sorry, as usual I think I found it within minutes after sending out a request
for help.
I should have re-read the documentation first, instead of afterward.
Selection Type = PoolUncopiedJobs
I had left it at PoolTime and reduced the time to 1 minute.
-Original Message-
From: Luc Van der Veken [mailto:luc...@wimionline.com]
Sent: 28 October 2014 8:31
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Migrate: copy or duplicate?
Sorry if this is a stupid question, but with copy instead of migrate, how do
you keep Bacula from copying the same jobs over and over again each time a copy
job is being run?
My original backup schema was like this:
* Full backup to disk once a month on Friday night, systems distributed about
evenly over 1st to 4th Friday, 1 month retention.
* Differential backup the other Fridays, 1 month retention.
* Incremental every Monday to Thursday, with 1 week retention.
** Migrate full and differential backups older than 1 week to tape on Monday.
** Jobs moved to tape get retention of 3 months. Tapes are stored off-site.
But this meant that
- I got off-site backups only after a full week,
- restores almost always required the tapes to be brought in,
so a few weeks ago, I changed the last two steps into this:
** Changed migrate into a copy job that copies full and differential backups to
tape on Monday. No minimum age restrictions.
** Retention of jobs on disk 1 month, copies on tape 3 months.
I was used to some fluctuation in the number of tapes per week I needed with
the first schema, but it started to look a bit ridiculous yesterday, so I
checked the original job numbers: it was copying the same full backups to tape
for the third time.
Doesn't bacula keep track of which jobs it has already copied and which not?
Actually this is something that had crossed my mind when I was making the
changes, but that I dismissed because it has to keep track of those copies to
promote them to main later, so it must "know" about them.
The job definition for the migrate job that I changed to copy:
# Migration job to move older jobs to tape
Job {
Name = Transfer to Tape
# Type = Migrate
Type = Copy
Pool = File
Selection Type = PoolTime
Messages = Standard
Client = bacula-main # required and checked for validity, but ignored at
runtime
Level = full # idem
FileSet = BaculaSet # ditto
Priority = 20
## only for migration jobs
# Purge Migration Job = yes# purge migrated jobs after successful migration
Schedule = TransferToTapeSchedule
Maximum Concurrent Jobs = 5
}
-Original Message-
From: Luc Van der Veken [mailto:luc...@wimionline.com]
Sent: 15 September 2014 13:22
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Migrate: copy or duplicate?
From: Radosław Korzeniewski [mailto:rados...@korzeniewski.net]
> No. All copies goes to database as well, but they are indirectly available
> for restore and are promoted as a main backup only when original job expire.
> I could be wrong about it, but it was working as described last time I've
> check.
Thanks, it looks like I misunderstood or misread that part of the docs.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
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
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Inconsistent backups of windows clients
Mr. Florian, Hey... I'm glad you tried my sugestion. lol Maybe could you try more something like 60 secs? Some machines may take some time to turn on. As a workaround, alternativaly, you could use the Retry on Error option, in order to assure the backup execution in the time frame you need. -- Heitor Medrado de Faria +55 61 82684220 Precisa de treinamento Bacula presencial, telepresencial ou online? Acesse: http://www.bacula.com.br Em 28 de outubro de 2014 04:30:23 BRST, Florian escreveu: >Hello again. > >So, after maybe 4 days, one of the clients again randomly couldn't be >reached, so apperently adding 30 seconds sleep between wake-on-lan and >backup didn't help... > >Here is the whole log. Maybe this has any hint in it that I don't see? >(sorry for german languege) > >27-Okt 23:00 ubuntu-dir JobId 214: shell command: run BeforeJob >"powerwake XXX" >27-Okt 23:00 ubuntu-dir JobId 214: BeforeJob: INFO: Trying to wake >host: [XXX] >27-Okt 23:00 ubuntu-dir JobId 214: BeforeJob: INFO: Sending magic >packet to: [X] >27-Okt 23:00 ubuntu-dir JobId 214: shell command: run BeforeJob "sleep >30s" >27-Okt 23:00 ubuntu-dir JobId 214: Start Sicherung JobId 214, >Job=Backup_WS-005.2014-10-27_23.00.01_51 >27-Okt 23:00 ubuntu-dir JobId 214: Using Device "BackupDevice_WS-005" >to write. >27-Okt 23:03 ubuntu-dir JobId 214: Warning: bsock.c:112 Could not >connect to Client: WS-005_fd on 192.168.1.105:9102. ERR=Unterbrechung >während des Betriebssystemaufrufs >Retrying ... >27-Okt 23:03 ubuntu-dir JobId 214: Fatal error: bsock.c:118 Unable to >connect to Client: WS-005_fd on 192.168.1.105:9102. ERR=Unterbrechung >während des Betriebssystemaufrufs >27-Okt 23:03 ubuntu-dir JobId 214: Fatal error: FD hat keinen Jobstatus >zurückgegeben. >27-Okt 23:03 ubuntu-dir JobId 214: Error: Bacula ubuntu-dir 7.0.5 >(28Jul14): > Build OS: x86_64-unknown-linux-gnu ubuntu 12.04 > JobId: 214 > Job:Backup_WS-005.2014-10-27_23.00.01_51 > Backup Level: Incremental, seit=2014-10-26 23:01:01 >Client: "WS-005_fd" 5.2.10 (28Jun12) Microsoft Windows >7 Professional Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64 > FileSet:"Standard Windows Set" 2014-09-23 23:00:00 > Pool: "Pool_WS-005" (From Job Ressource) > Catalog:"StandardCatalog" (From Client resource) > Storage:"Storage_WS-005" (From Job Ressource) > Scheduled time: 27-Okt-2014 23:00:01 > Start time: 27-Okt-2014 23:00:33 > End time: 27-Okt-2014 23:03:43 > Elapsed time: 3 mins 10 secs > Priority: 10 > FD Files Written: 0 > SD Files Written: 0 > FD Bytes Written: 0 (0 B) > SD Bytes Written: 0 (0 B) > Rate: 0.0 KB/s > Software Compression: None > VSS:Nein > Encryption: Nein > Accurate: Ja > Volume name(s): > Volume Session Id: 34 > Volume Session Time:1413870076 > Last Volume Bytes: 17,056,640,116 (17.05 GB) > Non-fatal FD errors:1 > SD Errors: 0 > FD termination status: Error > SD termination status: Waiting on FD > Termination:*** Sicherungsfehler *** > >Regards, > >Florian S. > > > > > >-- > > > > >___ >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] Migrate: copy or duplicate?
Sorry if this is a stupid question, but with copy instead of migrate, how do
you keep Bacula from copying the same jobs over and over again each time a copy
job is being run?
My original backup schema was like this:
* Full backup to disk once a month on Friday night, systems distributed about
evenly over 1st to 4th Friday, 1 month retention.
* Differential backup the other Fridays, 1 month retention.
* Incremental every Monday to Thursday, with 1 week retention.
** Migrate full and differential backups older than 1 week to tape on Monday.
** Jobs moved to tape get retention of 3 months. Tapes are stored off-site.
But this meant that
- I got off-site backups only after a full week,
- restores almost always required the tapes to be brought in,
so a few weeks ago, I changed the last two steps into this:
** Changed migrate into a copy job that copies full and differential backups to
tape on Monday. No minimum age restrictions.
** Retention of jobs on disk 1 month, copies on tape 3 months.
I was used to some fluctuation in the number of tapes per week I needed with
the first schema, but it started to look a bit ridiculous yesterday, so I
checked the original job numbers: it was copying the same full backups to tape
for the third time.
Doesn't bacula keep track of which jobs it has already copied and which not?
Actually this is something that had crossed my mind when I was making the
changes, but that I dismissed because it has to keep track of those copies to
promote them to main later, so it must "know" about them.
The job definition for the migrate job that I changed to copy:
# Migration job to move older jobs to tape
Job {
Name = Transfer to Tape
# Type = Migrate
Type = Copy
Pool = File
Selection Type = PoolTime
Messages = Standard
Client = bacula-main # required and checked for validity, but ignored at
runtime
Level = full # idem
FileSet = BaculaSet # ditto
Priority = 20
## only for migration jobs
# Purge Migration Job = yes# purge migrated jobs after successful migration
Schedule = TransferToTapeSchedule
Maximum Concurrent Jobs = 5
}
-Original Message-
From: Luc Van der Veken [mailto:luc...@wimionline.com]
Sent: 15 September 2014 13:22
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Migrate: copy or duplicate?
From: Radosław Korzeniewski [mailto:rados...@korzeniewski.net]
> No. All copies goes to database as well, but they are indirectly available
> for restore and are promoted as a main backup only when original job expire.
> I could be wrong about it, but it was working as described last time I've
> check.
Thanks, it looks like I misunderstood or misread that part of the docs.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
___
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] How to mask spaces in script?
I haven't tested it with scripts, but I use double quotes when specifying paths in a fileset: File = "c:/documents and settings/davidp/" It should be the same with scripts. On Tue, Oct 28, 2014 at 7:51 AM, Florian wrote: > Hello, everyone. > > I have a small problem: > I went to start a script on a windows client after a backup was done. > The script is located at "C:\Program Files\Bacula\ShurdownScript.bat" > > I know I can mask the \ with a second \, but can I do that with the > space in "program files", too? > > Regards, > > Florian S. > > > -- > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- Un saludo, David Prieto. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
