Dear users,

I'm using file-based backups and configurated Bacula[bacula-dir Version:
5.2.13 (19 February 2013)] to write one volume per job, with an
exclusive label containing the client name, data and time as shown
bellow in the config files attached.

The problems is: 

1º Why Bacula creates a volume for a job if the job has no data to be
backed up? That causes the created volume to stay open for writing, what
causes another problem:

2º Instead of creating a new volume for the next client to be backed-up,
Bacula writes in the empity volume created at problem 1.

I'm dealing with a situation where an client named Git has no
modifications, but a volume Git-{data}... was created.

Then, the next job starts, for the client Samba, and the data end-up
being recorded on the volume Git-{data}... because the empty volume
created on the previous job that has no modifications, was not closed.

What I've donne wrong? Suggestions?

bacula-dir.conf
Description: Text document

bacula-dir-clients-and-jobs.conf
Description: Text Data

basic-client.conf
Description: Text document

bacula-dir-pools.conf
Description: Text document

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users