On Tue, Mar 10, 2009 at 12:30:58PM -0400, Phil Stracchino wrote: > Graham Keeling wrote: > > On Mon, Mar 09, 2009 at 07:17:23PM -0400, Dan Langille wrote: > >> Kern Sibbald wrote: > >>> On Monday 09 March 2009 18:39:49 Graham Keeling wrote: > >>>> On Mon, Mar 09, 2009 at 05:56:36PM +0100, Kern Sibbald wrote: > >>>>> On Monday 09 March 2009 17:40:15 Graham Keeling wrote: > >>>>>> Hello, > >>>>>> > >>>>>> I have come across some problems involving a single client, a single > >>>>>> fileset, and more than one job definition. > >>>>>> > >>>>>> My setup... > >>>>>> > >>>>>> Client: myclient > >>>>>> FileSet: myfileset > >>>>>> > >>>>>> Job: myjob1 > >>>>>> Job: myjob2 > >>>>> Bacula does not support this option. > >>>> I don't believe that this is made very clear in the documentation. > >>> > >>> Unfortunate what you are trying to do is simply not possible in the way > >>> you are trying to do it with the current code. > >> What the original poster could do to achieve the same result: > >> > >> Have two FileSets with identical content but different names. > >> > >> I am pretty sure the goal is to manage just one FileSet. I suspect you > >> can do this with the existing Bacula directives. > > > > This is what I'm going to have to do for now - have duplicate filesets with > > different names. > > > You still haven't answered what your actual goal is, i.e. what (at high > level) you're trying to accomplish. There may well be a better way to > do it. If we understand what you're trying to do, we'll be better > equipped to point you at the best solution.
I think I did, in this mail from earlier today: http://marc.info/?l=bacula-devel&m=123667853425498&w=2 I would like to be able to backup my fileset to my local storage daemon, and then do another backup to a remote storage daemon. I would then like to be able to restore from either storage daemon at will. As I understand it, a 'copy job' is very similar to a 'migration job', only the original does not get deleted. I have looked at the 'copy job' documentation, and it seems that it would not help. Some reasons from the documentation as to why I think a 'copy job' won't help: a) "the copy is treated as a copy rather than a backup job, and hence is not directly available for restore." b) "Migration is only implemented for a single Storage daemon. You cannot read on one Storage daemon and write on another." ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
