Bugfix evaluating backup name

Nun, da logging angeschaltet ist, sieht man auch, was genau da passiert. Es wird immer der zuerst generierte Name für das neue Backup verwendet, nicht das aktuelle Datum, da muss ich nochmal reinschauen...

2021-06-07 06:20:23,018 - Job - INFO - Running job doBackup_1
2021-06-07 06:20:24,399 - BackupOrRestorePostgres - INFO - Starting backup from postgres:5432/rv-tool to backup@backup.n4group.eu:rv-tool-databa
se-develop::rv-tool-2021-06-05...
Archive rv-tool-2021-06-05 already exists
2021-06-07 06:20:25,679 - BackupOrRestorePostgres - INFO - Starting check of backup@backup.n4group.eu:rv-tool-database-develop:rv-tool-2021-06-0
5...
2021-06-07 06:20:27,240 - BackupOrRestorePostgres - INFO - Starting prune of backup@backup.n4group.eu:rv-tool-database-develop with pattern "rv-
tool-[0-9][0-9][0-9][0-9]-[01][0-9]-[0123][0-9]"...
2021-06-07 06:20:30,074 - BackupOrRestorePostgres - INFO - Starting backup from postgres:5432/rv-tool-supplier to backup@backup.n4group.eu:rv-to
ol-database-develop::rv-tool-supplier-2021-06-05...
Archive rv-tool-supplier-2021-06-05 already exists
2021-06-07 06:20:31,485 - BackupOrRestorePostgres - INFO - Starting check of backup@backup.n4group.eu:rv-tool-database-develop:rv-tool-supplier-
2021-06-05...
2021-06-07 06:20:33,187 - BackupOrRestorePostgres - INFO - Starting prune of backup@backup.n4group.eu:rv-tool-database-develop with pattern "rv-
tool-supplier-[0-9][0-9][0-9][0-9]-[01][0-9]-[0123][0-9]"...
2021-06-07 06:21:04,608 - Scheduler - INFO - Evaluating jobs to run