On Saturday 26 September 2009 21:24:27 Nicolae Mihalache wrote:
> Kern Sibbald wrote:
> > On Friday 25 September 2009 16:35:42 Nicolae Mihalache wrote:
> >> Hello,
> >> I've been struggling for two days to understand how to make a file
> >> virtual backup that uses the same source and destination pool. It was
> >> always deadlocking wanting to read and write from the same device.
> >> I think now I managed, the trick being that one storage can contain
> >> multiple devices. This is not explained in the documentation, I think it
> >> should be corrected.
> > I am not sure why your are making that statement. The second sentence of
> > the Device resource documentation for the Storage daemon clearly resolves
> > that point.
> Sorry, yes, it is documented that one storage daemon can contain
> multiple devices.
> What is not is that one storage resource defined in
> the director, can also point to multiple devices from SD. I thought that
> one has to define one director storage resource for each device.
Yes, the above is not documented because it is something that is not ready
for "production" use. The syntax and sematics of specifying multiple devices
in a Director Storage resource will almost surely change when we add the
ability to backup to multiple Storage daemons. Thus as it stands, we do not
support it, it is not documented, and you are free to use it but at your own
> >> One other thing: I noticed is that if you run a job with run
> >> Job=job-name storage=storage-name, the storage-name does not override a
> >> storage definition in the selected pool. It is not clear from the
> >> documentation which parameters you can override in the schedule or when
> >> running a job manually and which not.
> > That may in fact be true. Overrides are a bit complicate. Could you
> > please submit a patch for the documentation that explains what you have
> > found.
> Ok, I will try.
Great, thanks. Overrides is an area where I am not totally satisified, so
any suggestions for improvement would be carefully considered.