vdzump: log with what retention settings we prune

may not be obvious from the task log alone if we're relying on the
retention setting configured on a storage or the ones from local
node's vzdump.conf

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm
index e6a3a16f1c67cc38e08dc19359486d6a19d7c663..b400ffa04a0be9b54977d46c61a97fc262ddb808 100644 (file)
--- a/PVE/VZDump.pm
+++ b/PVE/VZDump.pm
@@ -995,8 +995,9 @@ sub exec_backup_task {
            debugmsg ('info', "archive file size: $cs", $logfd);
        }
 
-       # purge older backup
        if ($opts->{remove}) {
+           my $keepstr = join(', ', map { "$_=$prune_options->{$_}" } sort keys %$prune_options);
+           debugmsg ('info', "prune older backups with retention: $keepstr", $logfd);
            if (!defined($opts->{storage})) {
                my $bklist = get_backup_file_list($opts->{dumpdir}, $bkname, $task->{target});
                PVE::Storage::prune_mark_backup_group($bklist, $prune_options);