[Bacula-users] Possible missing SD Device resource configuration options

Hi all, I just upgraded to 2.0 and have been going through my configuration files (converting to per-client Devices). I noticed a couple definitions in my old 1.38 Device {} sections that are not mentioned in the manual. The first is Automatic Mount, is this still valid (was it ever? am I craz

[Bacula-users] Problems getting TLS working between FD and Director

Hello, Trying to get TLS going. I have it working between Dir/console (including remote), and Dir/SD, but can't get it working between Dir/FD. I followed , which is pretty good. Most of my confusion was where to put what, not what to put in

Re: [Bacula-users] Problem/confusion regarding running concurrent jobs.

Hi Arno, Thanks for the response. Arno Lehmann wrote: > Do you think a separate section regarding concurrent jobs would be > necessary, that extends the existing contents in "Tips and Suggestions"? I don't think so, I understood how things worked where I was looking, but wasn't looking in the

[Bacula-users] Problem/confusion regarding running concurrent jobs.

Hello, I have about 20 clients backing up to disk (all 1.38.11) and I'd like to run at least a few of them simultaneously but can't get it working. The manual mentions Maximum Concurrent Jobs all over the place and nowhere does it explain well how to get this to work. The best place I found was

Re: [Bacula-users] Trouble restoring from a disk backup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I still can't figure this out. I can't believe it's such a HUGE PITA getting disk-based backup and restore to work with Bacula. It should be easy. WTF. I'm so freaking frustrated right now. Dammit. Josh Endries wrote: > Hello,

[Bacula-users] Trouble restoring from a disk backup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I'm having trouble restoring from a File device. The backup says it runs OK, and a verify job says the backup is OK, but the restore job gives me this: Error: block.c:305 Volume data error at 0:2405980938! Block checksum mismatch in block=1410

[Bacula-users] 1.38.1 on FreeBSD "device not configured" and "mutex unlock failure"

Hello, I'm having trouble getting things working after upgrading to 1.38 on my system. btape's normal and autochanger tests were all successful, it's probably a FreeBSD issue but I don't know what. I have an Exabyte VXA 1x10 2U autoloader. 19-Nov 00:14 backup-dir: Start Backup JobId 162, Job=leto

[Bacula-users] More problems with 1.37.38, no tape loading?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ugh, this is so frustrating. Now Bacula won't load any tapes from my autochanger to write to...and I still can't get btape to run. If I load a tape manually, then run a job in bconsole, it works. If I start a job without any tape loaded, it never tries

Re: [Bacula-users] 1.37.38 problem: Inappropriate ioctl for device

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Langille wrote: > Is bacula in the operator group? On FreeBSD, bacula-sd should be > running as bacula:bacula. You'll need to restart bacula-sd after > changing /etc/group. Yep, everything is just like yours, root:operator and 660 except for t

[Bacula-users] 1.37.38 problem: Inappropriate ioctl for device

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I tried upgrading to 1.37.38 last night. Things were going okay but it couldn't find the end of medium so I tried running btape again, now I'm getting this: backup# btape -d 99 -v /dev/nsa0 Tape block granularity is 1024 bytes. btape: butil.c:

[Bacula-users] "Network send error" and "Broken pipe"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, My backups were working good for the past few days but this morning I got a bunch of errors. I'm using the latest stable on FreeBSD 5.4, with a 1x10 VXA AutoPak autochanger. The first client backed up OK but every other client (six) got errors.

[Bacula-users] Core dump with 1.36.3 on FreeBSD 5.4, "Fatal Error because: Bacula interrupted by signal 10: BUS error"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I noticed someone else had the same error a couple months ago. My test server's director died this morning mid-backup with the "BUS error" in the subject: "Fatal Error because: Bacula interrupted by signal 10: BUS error" It's running on a Pen

Re: [Bacula-users] Concurrency with a single tape drive?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Arno Lehmann wrote: > Josh Endries wrote: > > Is it possible to have multiple clients back up nightly to a bacula > server with one autochanger? > >> Yes. Okay, that's good news...now to just get it working. ;) >>

[Bacula-users] Concurrency with a single tape drive?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is it possible to have multiple clients back up nightly to a bacula server with one autochanger? I've been trying to get mine going with three test clients but, even though spooling works, it does them one at a time. The only thing I can think of is b

Re: [Bacula-users] Spooling to disk and concurrency

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 LHERBIER Lois wrote: > And the "SpoolData = yes" in the job directive. > > Do not forget to have the spool directory writable for the bacula-sd > process or your backup will fail. Thanks for the response. It's spooling now, but concurrent jobs aren't

[Bacula-users] Spooling to disk and concurrency

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've been trying to get Bacula to spool to disk and run concurrent jobs but it just isn't working...backing up works one-by-one but nothing gets spooled to disk in the meantime. Is there a way to force it to spool, or is it supposed to always spoo