I had configured a new backup task and was checking its status. The logfile states
INFO: adding '/dev/virt_store_sas/vm-102-disk-1' to archive ('vm-disk-virtio0.raw')
INFO: Total bytes written: 42945620480 (11.95 MiB/s)
INFO: archive file size: 22.41GB
INFO: delete old backup '/mnt/pve/backup01/dump/vzdump-qemu-102-2012_01_29-23_55_08.tar'
INFO: Finished Backup of VM 102 (00:57:31)
INFO: Backup job finished successfully
Oops, "delete old backup"??? (unfortunatly I didn't remove the previous
backup from the default 'dump' dir)?
Deleting old files by default is IMHO very bad idea. I'm very new to proxmox
and had no contact with it before 2.0 Beta. So i'm not familiar with usual
do's and don'ts.
The the only lines of any kind of rotation man is mentioning are
| -maxfiles integer (1 - N)
| Maximal number of backup files per VM.
| BACKUP FILE NAMES
| Newer version of vzdump encodes the virtual machine type and the
| backup time into the filename, for example
| That way it is possible to store several backup into the same
| directory. The parameter "maxfiles" can be used to specify the
| maximal number of backups to keep.
So from reading this did not expect that only one level of backups is kept by
default. Maybe it's only me but I think this is a pitfall. At least it happens to
me that I lost backups.
The default should be: *NO* rotation if '-maxfiles' is not specified explicitly.
The manual should also be more clarifying on this.