> On Thu, Oct 15, 2015 at 05:50:11PM -0400, Phil Stracchino wrote:
> > On 10/15/15 14:02, Doug Sampson wrote:
> > > I've revised the version to 14 and executed the script giving me this
> error message:
> > >
> > >
> > > root@pisce
> > I've revised the version to 14 and executed the script giving me this
> error message:
> >
> >
> > root@pisces:/usr/local/share/bacula# ./update_postgresql_tables
> >
> > This script will update a Bacula MySQL database from version 12-14 to 15
> >
> > Depending on the current version of your ca
> >> This query should do it, assuming your Bacula schema is named 'bacula'
> >> and you haven't skipped any intervening DB versions before the current
> 15:
> >>
> >> update bacula.Version set VersionId = 14;
> >
> > Forgive my ignorance but at this point, I am unsure which choice to
> choose:
> >
> >> You could manually revert the version table in the DB to the previous
> >> version, run the update script again, and record the errors this time.
> >
> > How does one accomplish this? Is there a secret trick to revise the
> version?
>
> This query should do it, assuming your Bacula schema is
>
> You could manually revert the version table in the DB to the previous
> version, run the update script again, and record the errors this time.
How does one accomplish this? Is there a secret trick to revise the version?
~Doug
-
Hello-
Yesterday I upgraded Bacula from 7.0.5 to 7.2 running on a FreeBSD 10.1 system.
It appears that the upgrade didn't go well. All of my jobs failed overnight.
This is a sample of a failed job:
*mes
15-Oct 06:58 pisces-dir JobId 16576: Start Backup JobId 16576,
Job=mailfilter.2015-10-15_06
6/05/2015 12:20 pm, Dimitri Maziuk wrote:
> > On 06/05/2015 11:17 AM, Doug Sampson wrote:
> >>>
> >>> I have been running 5.20 for some time, it did break the script, but
> >>> the
> >>> fix was rather simple, probably should have posted somethi
>
> I have been running 5.20 for some time, it did break the script, but the
> fix was rather simple, probably should have posted something to a
> mailing list so that it was fixed by now.
>
> in /usr/local/share/bacula/make_catalog_backup.pl I just changed the
> first line from:
> #!/usr/bin/env
Recently FreeBSD announced that its default Perl version is now 5.20 and urged
all users to upgrade to that version. I did so. Now make_catalog_backup.pl
doesn't run. The first indication was as follows:
30-May 09:05 pisces-dir JobId 15770: shell command: run BeforeJob
"/usr/local/share/bacula
Egads! I completely forgot to update all of the volumes in the pools with the
change! Once I did that, I now am able to truncate!
Thank you, Ana!
~Doug
From: Ana Emília M. Arruda [mailto:emiliaarr...@gmail.com]
Sent: Thursday, May 28, 2015 6:56 PM
To: Doug Sampson
Cc: bacula-users
I changed the Recycle flag to YES in most of the pools (including the ‘aries’
pool) and reloaded. The truncate command didn’t work.
What else am I overlooking?
~Doug
From: Ana Emília M. Arruda [mailto:emiliaarr...@gmail.com]
Sent: Thursday, May 28, 2015 4:30 PM
To: Doug Sampson
Cc: bacula
h "Recycle = no". Bacula will not recycle
these volumes this way.
Best regards,
Ana
On Thu, May 28, 2015 at 7:41 PM, Doug Sampson
mailto:do...@dawnsign.com>> wrote:
Hello-
I am experiencing the exact same situation as Erik Olsen did when he posted to
the list last week. I have ye
Hello-
I am experiencing the exact same situation as Erik Olsen did when he posted to
the list last week. I have yet to hear from him whether he has succeeded in
truncating purged volumes automatically. I am still getting the message that
there are no volumes to truncate when in fact there are
> This will cause a problem presumably, if you do backups on an LZO client
> (such as I'm
> considering on my SPARC T2 hosts, weedy CPU cores) then if necessary you
> can't restore these
> backups to a GZIP only client.
>
> It essentially limits the restore clients to those who also have LZO
>
> > Thanks for confirming this. I've recompiled both the server and client
> on the Bacula server and the configure options confirms the LZO support
> option is enabled.
>
> Nice, you should now have a director (bacula-dir)with lzo compression
> options and storage (bacula-sd) with lzo stream supp
> yes you need to have LZO include and lib installed in your system AND you
> need to compile bacula (client, storage and director) in order to get LZO
> compression support.
>
> There is a major compression speed improvement in LZO 2.05 and up on
> 64bits Intel system. Check that you have at leas
Hello-
I want to use LZO compression in two of my jobs instead of GZIP. These jobs
back up to hard drives on a FreeBSD 9.1-RELEASE machine. Bacula v5.2.12.
I installed archivers/lzo2 and verified that /usr/local/lib/liblzo2.so exists.
This was after I had been using Bacula on this particular se
>
> You might run Baculas "dbcheck" to prune unused entries in the
> database before migration.
>
I ran:
root@pisces:/~# su -m bacula -c '/usr/local/sbin/dbcheck -B -c
/usr/local/etc/bacula-dir.conf'
catalog=MyCatalog
db_name=bacula
db_driver=
db_user=bacula
db_password=
db_address=
db_port=0
db_s
> I need to migrate Bacula from PGSQL 8.3 as it's being EOL'ed. The newest
> version of PGSQL available in the FreeBSD ports tree is 9.2. Below are the
> steps I've taken to describe the migration process:
>
>
>
> Backup PGSQL config file(s
> Zitat von Doug Sampson :
>
> >>
> >> Questions:
> >>
> >> 1) Do I actually need to remove the bacula packages?
>
> From Bacula point of view, no. But your package system might force
> you because of dependencies. If you compile from source it
I need to migrate Bacula from PGSQL 8.3 as it's being EOL'ed. The newest
version of PGSQL available in the FreeBSD ports tree is 9.2. Below are the
steps I've taken to describe the migration process:
Backup PGSQL config file(s)
/h
>
> try to pkg_delete bacula-client and bacula-server before
>
I did a symlink and was able to start Bacula. My concern is whether I will be
bitten again on the next upgrade.
~Doug
--
Live Security Virtual Conference
Upon performing a portmaster -w upgrade of Bacula-client and bacula-server from
5.2.6 to 5.2.10 and restarting all of the Bacula processes, I received the
following error:
Shared object "libbaccats-5.2.10.so" not found, required by "bacula-dir"
root@pisces:/usr/ports/sysutils/bacula-server# ll
> I think you should first delete both bacula-server and bacula-client,
> and then install them both. I don't know whether the order matters.
>
> PS. This 2 ports having the same libraries is quite a mess in means of
> FreeBSD ports, isn't it?
So I uninstalled and reinstalled both server and clie
> On 02/03/2012 16:52, Doug Sampson wrote:
> > Hello-
> >
> > While upgrading from 5.2.3 to 5.2.6 on a FreeBSD 9.0-RELEASE machine and
> restarting, I encountered an error as follows:
> >
> > ===>>> Done displaying pkg-message files
> >
> >
Hello-
While upgrading from 5.2.3 to 5.2.6 on a FreeBSD 9.0-RELEASE machine and
restarting, I encountered an error as follows:
===>>> Done displaying pkg-message files
===>>> Upgrade of bacula-client-5.2.3 to bacula-client-5.2.6 complete
root@pisces:/# rehash
root@pisces:/# /usr/local/etc/rc.d
> >>>>> On Mon, 6 Feb 2012 17:48:51 -0800, Doug Sampson said:
> >
> > I've outputted a list of files from this and compared with the bls
> > output.
> > Even though the bconsole 'list' files reports 989 lines, there are
> > actual
> > > How do I output the results of the bconsole 'list' command to a
file?
> > > I've outputted from the 'bls' command quite easily.
> > >
>
> Use
>
> @output filename
> list files jobid=8295
> @output
>
Okay, I've learned a thing here! Thanks for the tip.
I've outputted a list of files from thi
> > >>>>> On Thu, 2 Feb 2012 13:11:15 -0800, Doug Sampson said:
> > >
> > > > >>>>> On Tue, 31 Jan 2012 11:02:59 -0800, Doug Sampson said:
> > > > >
> > > > > > >>>>> On Mon, 30 Jan 201
> >>>>> On Thu, 2 Feb 2012 13:11:15 -0800, Doug Sampson said:
> >
> > > >>>>> On Tue, 31 Jan 2012 11:02:59 -0800, Doug Sampson said:
> > > >
> > > > > >>>>> On Mon, 30 Jan 2012 13:28:47 -0800, Doug Sampson
> >>>>> On Tue, 31 Jan 2012 11:02:59 -0800, Doug Sampson said:
> >
> > > >>>>> On Mon, 30 Jan 2012 13:28:47 -0800, Doug Sampson said:
> > > >
> > > > Hello-
> > > >
> > > > Since upgrading to 5.2.
> >>>>> On Mon, 30 Jan 2012 13:28:47 -0800, Doug Sampson said:
> >
> > Hello-
> >
> > Since upgrading to 5.2.3 from 5.0.3 on a FreeBSD 7.4 server two
weeks
> > ago, I've started seeing this message:
> >
> > 28-
Hello-
Since upgrading to 5.2.3 from 5.0.3 on a FreeBSD 7.4 server two weeks
ago, I've started seeing this message:
28-Jan 06:08 pisces-sd JobId 8299: End of Volume at file 1 on device
"FileStoragecepheus" (/backup), Volume
"Backup_cepheus-fd_2012-01-28_00.05.01"
28-Jan 06:08 pisces-sd JobId 8299
> > Are you using the --disable-libtool option to configure? If so,
> > you'll need the attached patch to make it work.
> >
> > __Martin
>
> Yes, I was. On more than one system. I should have mentioned this in
the
> first place. I will investigate applying this patch and report back.
>
The patc
> -Original Message-
> From: Martin Simmons [mailto:mar...@lispworks.com]
> Sent: Monday, September 13, 2010 03:22 AM
> To: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Cannot build bacula-client 5.0.3 on
> FreeBSD 7.3
>
> >>>>> O
Today I went ahead to upgrade bacula-client to 5.0.3 from 5.0.2 and the
build broke down at the point listed below:
Linking bacula-fd ...
/usr/bin/c++ -rpath=/usr/local/lib -L../lib -L../findlib -o bacula-fd
filed.o authenticate.o acl.o backup.o estimate.o fd_plugins.o accurate.o
filed_conf.o hea
Hello,
While configuring the 'make config' options, I see that there isn't any
option to disable the libtool option. I wish to create a statically linked
bacula client which requires disabling the libtool option. When I attempt to
do:
./configure --disable-libtool
it complains of not being told
> > > What then? Was this because of the failed 'make path' command?
> >
> >
> > It's 'make patch' but adding the proper CONFIGURE_ARGS environment
> > variable as Dan stated would be the best way to go. Example for
> > csh/tcsh:
> >
> > cd /usr/ports/sysutils/bacula-client
> > env CONFIGURE_ARG
> > What then? Was this because of the failed 'make path' command?
>
>
> It's 'make patch' but adding the proper CONFIGURE_ARGS environment
> variable as Dan stated would be the best way to go. Example for
> csh/tcsh:
>
> cd /usr/ports/sysutils/bacula-client
> env CONFIGURE_ARGS+=--enable-static
> > Found a few ways to create a static-fd (i think)
> >
> > run make configure in /usr/ports/sysutils/bacula-client
> > write down (copy) the configure command with all the argument from
> > config.log in the work/bacula-2.4.4 dir
> > run make clean in /usr/ports/sysutils/bacula-client
> > now ru
> Found a few ways to create a static-fd (i think)
>
> run make configure in /usr/ports/sysutils/bacula-client
> write down (copy) the configure command with all the argument from
> config.log in the work/bacula-2.4.4 dir
> run make clean in /usr/ports/sysutils/bacula-client
> now run make extract
> >>>>> On Wed, 11 Feb 2009 16:34:16 -0800, Doug Sampson said:
> >
> > I poked around some more. I discovered the 'ldd' command
> which shows the
> > libraries used/required by bacula-fd as follows:
> >
> > r...@pisces:/root
> > Doug Sampson wrote:
> > > I'm using this to recover data onto a FreeBSD 7.1
> prerelease server:
> > >
> > >
> > http://www.bacula.org/fr/dev-manual/Disast_Recove_Using_Bacula
> .html#SECTION0
> > 082314000
> > >
> Doug Sampson wrote:
> > I'm using this to recover data onto a FreeBSD 7.1 prerelease server:
> >
> >
> http://www.bacula.org/fr/dev-manual/Disast_Recove_Using_Bacula
.html#SECTION0
> 082314000
> >
> > All of the steps work up until
I'm using this to recover data onto a FreeBSD 7.1 prerelease server:
http://www.bacula.org/fr/dev-manual/Disast_Recove_Using_Bacula.html#SECTION0
082314000
All of the steps work up until #17 where I need to chroot in order to start
the bacula-fd daemon. I get the following error messa
Anyone have a clue about this? I'd like to get to the bottom of this.
~Doug
-Original Message-
From: Doug Sampson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2008 02:47 PM
To: 'Bacula-users@lists.sourceforge.net'
Subject: [Bacula-users] "Cannot find an
Hi all,
I'm running Bacula 2.4.2 off a FreeBSD 7.0 server using a DDS-3 tape drive.
I'm using a Grandfather/father/son tape rotational scheme where I back up
the data and the catalog as two nightly jobs onto a tape each time that it
runs. All is well. Except for the monthly full backup. It will s
> > >> Bacula 2.2.5 and PGSQL 7.4.18. I am seeing the same
> errors on another
> > >> FreeBSD 6.2 machine with Bacula 2.2.5 and PGSQL 8.0.14
> >
> > I'm not sure which version of PostgreSQL is required for the batch
> > inserts. I coldn't find that in the ReleaseNotes, but there was a
> > discussi
> Doug Sampson wrote:
> >>> 07.11.2007 02:41,, Doug Sampson wrote::
> >>>> I am testing the restore function of Bacula 2.2.5 on
> >>> FreeBSD 6.2 and in the
> >>>> process of restoring ~20,000 files recursively from the
> >>>
> Doug Sampson wrote:
> > I am testing the restore function of Bacula 2.2.5 on
> FreeBSD 6.2 and in the
> > process of restoring ~20,000 files recursively from the
> /var directory, I am
> > seeing numerous error messages as follows:
> >
> > <..sn
> > 07.11.2007 02:41,, Doug Sampson wrote::
> > > I am testing the restore function of Bacula 2.2.5 on
> > FreeBSD 6.2 and in the
> > > process of restoring ~20,000 files recursively from the
> > /var directory, I am
> > > seeing numerous er
> 07.11.2007 02:41,, Doug Sampson wrote::
> > I am testing the restore function of Bacula 2.2.5 on
> FreeBSD 6.2 and in the
> > process of restoring ~20,000 files recursively from the
> /var directory, I am
> > seeing numerous error messages as follows:
> >
>
I am testing the restore function of Bacula 2.2.5 on FreeBSD 6.2 and in the
process of restoring ~20,000 files recursively from the /var directory, I am
seeing numerous error messages as follows:
<..snip..>
06-Nov 17:37 aries-fd JobId 2326: Warning: restore.c:588 Can't restore ACL
of
/tmp/bacula-r
Hi folks,
I'm seeing a problem in that prior to the Bacula 2.0 upgrade, I was able to
run a verify job on the current day's tape data to ensure that the tape can
be read as well as verifying the tape data reflects the data on the server's
HDs. However, after the upgrade to 2.0 from 1.38.11 (or so)
> On 9 Jan 2007 at 13:52, Doug Sampson wrote:
>
> > I'm getting an PGSQL error each time I attempt to dump
> bacula to a SQL file
> > during catalog backup as follows:
> >
> > [EMAIL PROTECTED]:/usr/local/share/bacula#
> > /usr/local/share/bacula/ma
I'm getting an PGSQL error each time I attempt to dump bacula to a SQL file
during catalog backup as follows:
[EMAIL PROTECTED]:/usr/local/share/bacula#
/usr/local/share/bacula/make_catalog_backup1 bacula bacula
pg_dump: attempt to lock table "location" failed: ERROR: permission denied
for relati
P.S. Ooops! I overlooked the subject header- now reporting with subject
header. My bad.
Occasionally, I see the following error in my emailed job logs as follows:
18-Jul 03:00 aries-dir: The job will require the following Volumes:
18-Jul 03:00 aries-dir:
18-Jul 03:00 aries-dir:Backup_ari
Occasionally, I see the following error in my emailed job logs as follows:
18-Jul 03:00 aries-dir: The job will require the following Volumes:
18-Jul 03:00 aries-dir:
18-Jul 03:00 aries-dir:Backup_aries-fd_2006-07-18_00.05.03
18-Jul 03:00 aries-dir:
18-Jul 03:00 aries-dir: Start Verify Jo
> Doug Sampson <[EMAIL PROTECTED]> wrote:
>
> > I'm backing up data to files- not tapes. I've configured
> the bacula-dir.conf
> > to activate compression (compression=GZIP6) as follows:
> >
> >
> > List of files to be backed
I'm backing up data to files- not tapes. I've configured the bacula-dir.conf
to activate compression (compression=GZIP6) as follows:
List of files to be backed up
FileSet {
Name = "Full Set"
Include {
Options {
signature = MD5
aclsupport = yes
compression = GZIP6
H
> > This is a FYI.
> >
> > Got the following message in bconsole:
> >
> > 20-Jun 00:05 aries-dir: ABORTING due to ERROR in bsys.c:375
> > Mutex lock failure. ERR=Resource deadlock avoided
> > 20-Jun 00:05 aries-dir: Fatal Error because: Bacula
> interrupted by signal
> > 11: Segmentation violation
> Yesterday I upgraded Bacula on FreeBSD-4.9 from 1.38.9 to
> 1.38.10. I hadn't
> seen Bacula crashing or anything before, but today bacula-dir
> wasn't running
> and message in console said:
>
> 15-Jun 22:00 mybacula-dir: ABORTING due to ERROR in bsys.c:375
> Mutex lock failure. ERR=Resource
FWIW.
My experience with using Bacula on tape drives is similar to Beren's. When
used on HD server, Bacula runs like a dream. But when used with a server
using tape drives, I am seeing Bacula wanting to append to volumes that
aren't full when I've specificaly requested that Bacula reuse the tape
c
>
> A known problem and easily fixed. Do a make clean, then make a one
> character change to the file described here:
>
>http://www.freebsd.org/cgi/query-pr.cgi?pr=88997
>
>
Yes, that was it. Fixed. Thanks!
~Doug
---
SF.Net email is
While trying to upgrade to 1.38 from 1.36.3 on FreeBSD 5.4, the installs
fails with the following:
<...snip...>
---> Backing up the old version
---> Uninstalling the old version
---> Deinstalling 'bacula-server-1.36.3'
rmdir: /var/db/bacula: Directory not empty
Check if /var/db/bacula is empty
> Take a look at the end of the Restore chapter in the
> development manual. I
> have started a list of things you should do and how to
> recover from various
> situations -- note the word "started" above, which means
> there is still much
> more documentation to add. If you have any commen
Hi all,
I've been using Bacula on our FreeBSD servers for less than half of this
year and it has worked quite well. It occurred to me that I should brush up
on the Bacula recovery process and in the process of reading I find I am not
quite clear as to what I need to do in order to restore a Bacula
This is a new bacula installation and am testing prior to putting into
production. I'm having trouble opening bconsole each morning:
[EMAIL PROTECTED]: cd /usr/local/etc
aries-root@/usr/local/etc: bconsole
Connecting to Director aries:9101
05-Oct 11:12 bconsole: Fatal error: bnet.c:775 Unable to
> On FreeBSD the bacula storage daemon usually runs as the user
> "bacula" which
> is in group "bacula". Try (as root):
>
> chmod bacula:bacula /backup
>
> And re-run your test.
Ah, that did it. Obviously this was a newb question.
> > drwxrwxr-x 4 root wheel 512 Sep 30 14:14
I've configured Bacula (ver 1.36.3) on a FreeBSD 5.4 machine to write to a
file on /backup but I'm getting the following error message each time I
attempt a job:
30-Sep 14:50 aries-sd: Aries.2005-09-30_14.50.25 Fatal error: device.c:317
Unable to open device /backup. ERR=dev.c:340 Could not open:
> If I guess right the file is only created during a query and
> automatically deleted afterwards, so that it exists when the FD scans
> the directory but disappeared already when it wants to process it.
>
> Excluding it from the file set should take care of that (I hope).
I'll try excluding th
> >>If I'm right, you can
> >>a) safely ignore the message, or
> >>b) exclude this file from the backup. This not only gets rid of the
> >>message, it also saves space because this file would be useless to
> >>restore. If you've got a catalog backup, of course.
> >
> >
> > How do I prevent Bacu
> If I'm right, you can
> a) safely ignore the message, or
> b) exclude this file from the backup. This not only gets rid of the
> message, it also saves space because this file would be useless to
> restore. If you've got a catalog backup, of course.
How do I prevent Bacula from trying to 'stat
Below is a status report from bacula with an error message- "23-Aug 00:12
orion-fd: Could not stat /var/db/bacula/bacula.db-journal: ERR=No such
file or directory".
23-Aug 00:05 orion-dir: Start Backup JobId 233,
Job=Orion.2005-08-23_00.05.00
23-Aug 00:05 orion-sd: Volume "Tuesday-0001" previ
74 matches
Mail list logo
