Re: [Bacula-users] Migrating form mysql to postgresql: Loading the database takes very long

2011-06-27 Thread Marcus Mülbüsch
Am 26.06.2011 00:18, schrieb Gavin McCullagh: > It seems you need to drop --quick which is implied in --skip-opt. The > resulting command that I'm working with at the moment is: > > mysqldump -t -n -c --compatible=postgresql --skip-quote-names --quick \ > --lock-tables --add-drop-table --ad

Re: [Bacula-users] Migrating form mysql to postgresql: Loading the database takes very long

2011-06-22 Thread Marcus Mülbüsch
Am 22.06.2011 12:05, schrieb Jérôme Blion: > I don't know how you dumped your mysql database. > Did you try to use mysqldump -T ? mysql2pgsql ? > I used some other scripts to migrate data pieces. I will look for them > this evening... mysqldump -t -n -c --compatible=postgresql --skip-quote-names

Re: [Bacula-users] Migrating form mysql to postgresql: Loading the database takes very long

2011-06-22 Thread Marcus Mülbüsch
Am 22.06.2011 06:14, schrieb Stuart McGraw: > You can identify the indexes from the CREATE INDEX commands > in /usr/libexec/bacula/make_postgresql_tables. Drop them > prior to loading, and then rerun the CREATE INDEX commands > after loading -- it can make a big difference in loading > time. I w

[Bacula-users] Migrating form mysql to postgresql: Loading the database takes very long

2011-06-21 Thread Marcus Mülbüsch
I want to migrate my bacula installation from mysql to postgresql, following the guide in http://www.bacula.org/5.0.x-manuals/en/main/main/Installing_Configuring_Post.html#SECTION00445 After dumping and converting the database the sql-file now has 9GiB. I began loading the db in

[Bacula-users] Non-working bacula client breaks backups

2010-11-24 Thread Marcus Mülbüsch, AS-Infodienste GmbH (Systemadministration)
oth jobs remain at that status indefinately. The bacula-director is "Version: 5.0.3 (04 August 2010) i686-pc-linux-gnu gentoo" running on "2.6.22-vs2.2.0.7-gentoo" Thanks for any help or pointers, Marcus Mülbüsch ---

[Bacula-users] Several "Exclude Dir Containing" in a fileset

2010-09-08 Thread Marcus Mülbüsch, AS-Infodienste GmbH (Systemadministration)
Hello all, I had an 'Exclude Dir Containing = ".exclude"' in the fileset for the windows clients. Now, for a "regular" user it's quite difficult to rename a file to a ".name" under Windows, besides a name as "data.nobackup" is more clear. To not search for all the ".exclude" files on t

[Bacula-users] bacula 5.0.2 for the Optware Itsy Package Management System ("ipkg")

2010-05-20 Thread Marcus Mülbüsch
Hello all, does anybody know whether there ia a package in the making for bacula-5.0.2 so we can run the storage daemon on the NAS itself? http://wiki.qnap.com/wiki/Install_Optware_IPKG http://www.nslu2-linux.org/wiki/Optware/PackageWishList Currently only a 3.0.1 (or thereabout) is pro

Re: [Bacula-users] Basic question on Pruning and Volume Retention

2010-05-20 Thread Marcus Mülbüsch
>I have to admit I am a bit confused now with two places to define > AutoPrune. > > The manual tells nothing about which resource takes precedence; or > at least I cannot find it. One cigarette later it is clear now: The AutoPrune directive in the Client Resource prunes Job and Fil

Re: [Bacula-users] Basic question on Pruning and Volume Retention

2010-05-20 Thread Marcus Mülbüsch
Martin Simmons schrieb: >>So with this settings I have archived a backup (including holding the >> Job Records indefinitely) until I manually work on it? > > If you have "AutoPrune = yes" in the Client definition then it might still get > pruned. That directive causes File and Job pruning fo

Re: [Bacula-users] Basic question on Pruning and Volume Retention

2010-05-19 Thread Marcus Mülbüsch
Martin Simmons schrieb: >> On Wed, 19 May 2010 10:31:34 +0200, Marcus said: >> Hi all, >> >> if I understand everything correctly, when I define a pool and set >> "AutoPrune = no" and "Volume Retention = 2 years", the first statement >> actually nulls out the Volume Retention period, sinc

[Bacula-users] Basic question on Pruning and Volume Retention

2010-05-19 Thread Marcus Mülbüsch
Hi all, if I understand everything correctly, when I define a pool and set "AutoPrune = no" and "Volume Retention = 2 years", the first statement actually nulls out the Volume Retention period, since the Volume will never be pruned, and thus is never be able to be recycled. The Volume