From ca155141b00ef1c5f0cb7a51e8aa5c3e035694a1 Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Thu, 17 Jun 2021 17:55:50 +0200 Subject: [PATCH] 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 --- PVE/VZDump.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/PVE/VZDump.pm b/PVE/VZDump.pm index e6a3a16f..b400ffa0 100644 --- 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);