>>>>> On Thu, 03 Nov 2011 20:07:57 -0400, Phil Stracchino said: > > Theorem as to a possible mechanism: > > If the catalog DB is empty when it runs, bscan creates new Clients and > Filesets as it encounters them. However, it does not guarantee that > they have the same ClientIds or FileSetIDs, and when scanning later jobs > - probably especially if you have to scan jobs in multiple batches > because there are too many Volumes to fit in the commandline at once - > if the FileSetId for the job appears to match an already existing > FileSetId, bscan assumes that the job is associated with the FileSet > *now* corresponding to that ID, even if it earlier allocated a different > ID to that FileSet. Ditto, possibly, with ClientIDs.
The volumes record the Client and FileSet names, not their ids, so it can't fail like that. However, as Kern said, there will be problems with jobs spanning volumes if you don't scan them all at once and in the correct order. Bscan could probably be smarter about this. __Martin ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
