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

[Thomas Lamprecht]

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.