[pve-devel] [PATCH pve-guest-common 1/1] vzdump: added "includename" option

Alwin Antreich a.antreich at proxmox.com
Wed Feb 5 15:14:31 CET 2020

On Thu, Nov 14, 2019 at 03:01:37PM +0100, Thomas Lamprecht wrote:
> On 11/14/19 6:30 AM, Dietmar Maurer wrote:
> >> The main reason for this is to identify backups residing on an old backup store like an archive.
> >>  
> >> But I am open. Would you prefer having a manifest included in the archive or as a separate file on the same storage?
> > 
> > The backup archive already contains the full VM config. I thought the manifest should be
> > an extra file on the same storage.
> > 
> An idea for the backup note/description feature request is to have
> a simple per backup file where that info is saved, having the same
> base name as the backup archive and the log, so those can easily get
> moved/copied around all at once by using an extension glob for the
> file ending.
> Simple manifest works too, needs to always have the cluster storage
> lock though, whereas a per backup file could do with a vmid based one
> (finer granularity avoids lock contention). Also it makes it less easier
> to copy a whole archive to another storage/folder.
If I didn't miss an email, then this feature request (#438 [0]) seems to
be still open (I'm the assignee).

In which direction should this feature go? Per backup manifest?

Or maybe extending the vzdump CLI with an info command that displays
some information, parsed from the backup logfile itself. Since the VM/CT
name is already in the log. Would that be a possibility too?

Example form a backup logfiles:
2020-02-04 15:58:55 INFO: VM Name: testvm
2020-01-13 15:39:35 INFO: CT Name: test

[0] https://bugzilla.proxmox.com/show_bug.cgi?id=438

More information about the pve-devel mailing list