On 11/04/11 08:14, Martin Simmons wrote:
> 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.
Oh, also, spanning isn't an issue here because the way I have my Volume
allocation set up, no Job ever spans multiple volumes. (Sure, this
means my most recent Full backup volume was almost 1TB. But I'm OK with
that.)
Is there anything else I can usefully test on this right now to help
isolate the problem? If not, I'm going to drop the Catalog again and
all the old Volumes (unless you'd like me to keep some around), and
start fresh with a clean Catalog and a new Full backup. (I do this
periodically anyway for varying reasons.)
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
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
