On Tue, Jun 30, 2009 at 8:09 PM, Jon Schewe wrote:
> I have a long running job that I want to run before backups. It backs up
> the databases on the client. I've added the ClientRunBeforeJob line and
> noticed that I was getting errors like this:
>
> 29-Jun 09:11 jon-dir JobId 4073: Start Backup Jo
I have a long running job that I want to run before backups. It backs up
the databases on the client. I've added the ClientRunBeforeJob line and
noticed that I was getting errors like this:
29-Jun 09:11 jon-dir JobId 4073: Start Backup JobId 4073,
Job=mtu.2009-06-29_09.11.03
29-Jun 09:11 jon-dir
Test your config file using `bacula-dir -t`, and if everything is ok, run
bconsole and type the command `reload`. This will cause the director to
reread the configuration while it is running without interruption. You
should also be able to run `/etc/init.d/bacula-dir reload` to accomplish the
same
Hi every:
I'm configuring Bacula but day by day I need to add a client or maybe
two or even more. I do that including a config file using "@" notation
in bacula-dir.conf. I'm asking if I need to restart Bacula every times I
add a new client or when I make changes in some specified client. Exist
In my opinion that´s wrong and confusing because in my case it´s no
new file but a deleted one. Even if I "List Jobs where a given File is
saved" in "restore" of bconsole I got a job listed where the file was
not backed up:
Enter Filename (no path):bacula-2.2.5-patch.tar.gz
++
i see the same problem since upgrading to 3.0.1
2009-06-25 07:59:28 backup-dir : Verifying against JobId=9247
2009-06-25 07:59:28 backup-dir : Start Verify JobId=9451 Level=Catalog
2009-06-25 07:59:32 backup-dir : New file: /etc/ssh/ssh_config
2009-06-25 07:59:32 backup-dir : New
I´m not sure if that is ok but I did not remember this before using 3.0.x (and
using Accurate = yes) so I try to understand. If I delete one file after and
incremental job an run again an incremental one I got differences in verify
afterwards. The deleted file is shown as "New file" in the ver
