On Mon, Feb 13, 2017 at 09:46:00AM +0100, Stefan G. Weichinger wrote: > > (didn't show up on the ml, so I re-send) > > is there any good trick to do this: > > on amanda-client-host I run backups of VMs to tarballs (using > virt-backup and LVM) > > in my amanda config I have DLEs pointing at the generated tarballs > > Now it happens that the virt-backup isn't fully done when amanda already > wants to dump the DLEs -> this results in invalid backups! > > I know, I could schedule amdump *after* all the virt-backups are done, > but I would like to optimize that: amdump should be able to dump other > DLEs in parallel already. > > One solution would be to use the starttime parameter? > Rather static. > > plan B: make virt-backup create some lock-file during its runs and make > the amanda DLE wait to be dumped until after that virt-backup lock file > has been removed. > > Does anyone of you already have such a setup running? >>> End of included message <<<
Would it be unreasonable to leave unfinished virt-backups til the next amdump? If not, make sure they unique names or time-stamps. Do the virt-backups to a ?.tmp name that is excluded by amanda. Renam the ?.tmp backup upon completion. jl -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
