Hi Debra, Yes, this will work if I use different labels not related with the name of the diskdevice, the only problem is more work when I run amstatus and amrecover to match the label with the disk/diredctory
Cheers, Nuno On Thu, 2019-06-27 at 18:37 +0000, Debra S Baddorf wrote: > > On Jun 27, 2019, at 7:38 AM, Nuno Dias <[email protected]> wrote: > > > > > I guess another possible solution is to using disknames of a form > > > that > > > are designend to be unique, e.g. something like (not tested) > > > > > > > ---------------------------------- > > > > MACHINE dir-main /dir { > > > > tar > > > > exclude "./subdir/*" > > > > } > > > > > > > > MACHINE dir-subdir /dir { > > > > tar > > > > include "./subdir/*" > > > > } > > > > ---------------------------------- > > > > > > ... and use those disknames on the amdump command line... (But > > > you > > > have to choose disknames carefully so your Amanda Mail Report > > > looks > > > reasonable, etc.) > > > > > > > > > Nathan > > > > Possibly not tested, but that was what I was describing. I use text- > only disknames > like that all the time. No slashes in them, so they cannot be > confused with actual disk designations! > > Deb Baddorf > Fermilab > > -- Nuno Dias <[email protected]> LIP
smime.p7s
Description: S/MIME cryptographic signature
