Re: [Bacula-users] clarify 'with-systemd' usage?

There may be a special target that you can use for installing systemd, but the easiest way should be: - do configure as yu did - build and install Bacula normally - cd /platforms/systemd - make install That *should* do everything you need, but I have never tried it. Best regards, Kern On

Re: [Bacula-users] Windows client 7.0.5 broken?

I have no idea what "developer's gift" is but to the best of my knowledge no Windows 7.0.5 ever existed. On 02/26/2016 08:49 AM, Cejka Rudolf wrote: > Hello, >after Windows client upgrade from public 5.2.10 to developers' > gift 7.0.5, I have noticed that incremental jobs started to be too

Re: [Bacula-users] bextract error

Please translate "dislink" to "dislike" On 02/26/2016 03:52 PM, Kern Sibbald wrote: > This is not a bextract error per-se, rather when Bacula is reading the > volume, the checksum it found in a block is not the same as the checksum > it computed with the data that was read. Normally this means

Re: [Bacula-users] Write Retry on Network Error without Restarting the Job

No this feature does not exist. However, in a recent version of Bacula (7.2.0 I think, but maybe 7.4.0) you can restart failed jobs and it will start roughly from the point the backup failed. Look in the New Features section of the document for Incomplete Jobs. Best regards, Kern On

Re: [Bacula-users] Problem with unmounting a device

It would probably help get a response if you give some details about "this seems to work no longer". Why doesn't it work? What does it do? What is the exact output? On 02/24/2016 04:04 AM, Dietz Pröpper wrote: > Hi, > > I have a little problem: > I have an autochanger with two devices. In

Re: [Bacula-users] bextract error

This is not a bextract error per-se, rather when Bacula is reading the volume, the checksum it found in a block is not the same as the checksum it computed with the data that was read. Normally this means that your disk drive is going bad. In your case, you aare using a mounted volume, and

[Bacula-users] Windows client 7.0.5 broken?

Hello, after Windows client upgrade from public 5.2.10 to developers' gift 7.0.5, I have noticed that incremental jobs started to be too big and too slow. Before upgrade with 5.2.10: Elapsed time: 4 hours 28 mins 43 secs FD Files Written: 180,897 FD Bytes Written:

Re: [Bacula-users] Write Retry on Network Error without Restarting the Job

I believe this feature is now available in version 7.4 From: "Clark, Patti" To: "Duane Webber" , "bacula-users" Sent: Thursday, February 25, 2016 3:09:40 PM Subject: Re: [Bacula-users] Write Retry on Network

Re: [Bacula-users] Write Retry on Network Error without Restarting the Job

Bacula Enterprise has this feature where a job can be restarted. There is no work around other than breaking up the jobs into smaller chunks. Patti Clark Linux System Administrator R Systems Support Oak Ridge National Laboratory From: Duane Webber

Re: [Bacula-users] Write Retry on Network Error without Restarting the Job

Hello Duane, Have you tried the heartbeat interval configuration to maintain connections alive between the daemons? Best regards, Ana Em qui, 25 de fev de 2016 às 18:05, Duane Webber escreveu: > Is there an option to have Bacula retry write operations without >

[Bacula-users] Write Retry on Network Error without Restarting the Job

Is there an option to have Bacula retry write operations without restarting the job? A search shows the last time this question was asked was in 2010 (the answer was no) and I'm hoping there is a change since then. I have remote backups that can take days, if not a week plus and it is not

[Bacula-users] bacula-fd and systemd

Hello, I have a strange issue with bacula and systemd and was hoping someone might have an answer. We have create a bacula systemd file (which I will post below). The issue is, if I warm boot the machine (reboot) it works fine. If I cold boot the machine (the machine is currently in a

Re: [Bacula-users] Automatic Volume generator on pool (and presentation)

Hello Guiseppe, The volume use duration period begins from the time of first data written to the volume. And this specific time is a slightly different from the scheduled time for your first job writing to the volume. In your case, you have your job scheduled to start at 23:05:00. The first data

Re: [Bacula-users] filesystem full

Hello Lylex, You can delete (i'm sorry this is too late) jobs and volumes for the old servers using the purge command from bconsole. The pools (if they were only used by the old servers and you are not going to use them anymore) should be deleted using the delete command from bconsole and

[Bacula-users] Next Scheduled Jobs as SQL Query?

Hello Heitor Faria, thanks for you reply. Exactly this way im running it, but im using "status dir" because i wasn't aware of the schedule option :( [Embarassed] Do you know if these information is also stored in the DB? The information i get via "status schedule" is very nice, but to avoid