[Bacula-users] understand Migration Job Part 2

Hi all,
  sorry if i open a new thread but from gmail i'm not able to reply to
myself in the other one.

After some tweaks i finally understand how it work migration task but
i need to understand if i can do a better job...

So, i add to DiskPool Pool with parameter Maximum Volume Jobs = 1

After it every client write its data to a file pool (freenas to
ServerPool0046 and winpc to ServerPool0045). If i start the migration
it done correctly

Ok, but if i remove the parameter Maximum Volume Jobs = 1 all jobs
goes to one file and i'm not able to migrate it to tape. Probably
because it contains 2 clients and 2 different file sets.

So, my question is, can i set a rexex or similar to define on the
migration job to use all jobs ?

the migration task is:

Job {
  Name     = "MigrateDiskToTape"
  Type     = Migrate
  Client   = "winpc-fd"
  FileSet  = "Windows Set"
  Messages = Standard
  Pool     = DiskPool

  Selection Type     = PoolOccupancy
  # no sense spooling local data
  Spool Data       = no
  Spool Attributes = yes
}

all clients end with -fd text and all FileSet end with Set text

Another little question, can i "purge" all data from FilePool after
migration automatically in order to keep the bacula backup disk empty?

Thanks
Riccardo

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users