Am 29.11.2011 14:49, schrieb Brian Cuttler: > > Hi Stefan, > > We also do backups of VMs, ours to fiber backed storage attached to > our Solaris systems (that is the short version anyway). We have a > fabric rather than a NAS. > > We are or where backing that up using amanda, I'd have to look and > see if we where still doing it, but we where not segragating our > backups out the way you are talking about. > > Simple solution ? Put all the new backups into a (sub)directory and > allow amanda to back that up. When amanda completes, or shortly > before the new VM dump starts again, move those backups into their > archive directory and purge using the same routines you use now. > > --the new tarballs have new names ? The existing tar balls aren't > renamed, are they ?
They aren't renamed, no, but the software keeps track of them and expects them in the specific directory, so I can't move the archives without confusing that software. At least I don't want to mess with that ... I like the fact that the file-bases backups are reliably done, I just want to add the additional layer of tape-based backups. And the available tape-technology doesn't allow me to backup all VMs to tape. In fact I will get problems anyway with single huge VMs, when I think about it ..... *sigh* (LTO-2 ... biggest VM has around 300gigs, others are smaller ...). Other thought: I could add jobs to the windows-backup-software for weekly stuff only. Maybe I figure out how to put them not into a subdir of the existing share ... AND/OR I also add a second share to the NAS for weekly/"to tape" backups. This way I could separate things ... will look into that tool again. Thanks, Stefan
