Facebook
Twitter
User name: Peter Debik
TITLE
Server backup claiming issues since upgrade to 18.0.28 without issues visible in log file or on restore page
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Obsidian 18.0.28, CentOS 7.8, latest MU
PROBLEM DESCRIPTION
Since the upgrade to 18.0.28 on two machines:
- The incremental backups display an error on the backup overview list. However, there is no warning message on this on top of the screen as it usually is shown when a backup is not fully valid.
- When you click on the backup name to "restore" it, there is no indication that the backup would not be fully valid.
- I did not find any issues in the backup log file either.
On a production machine where only incremental backups were done since the upgrade, all incremental backups are marked as invalid.
On an empty test machine where one incremental backup was done, then one full backup, then another incremental backup, only the first incremental backup is marked invalid while the full backup and the following increment are marked valid.
STEPS TO REPRODUCE
Create at least one full backup, then one increment.
Then upgrade 18.0.27 to 18.0.28
Then let the system create another increment on a backup plan.
ACTUAL RESULT
See problem description.
EXPECTED RESULT
Either explain why the backup file is invalid (display an error message with the log excerpt that triggers the invalid warning) or display the file as valid if it is valid.
ANY ADDITIONAL INFORMATION
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
Server backup claiming issues since upgrade to 18.0.28 without issues visible in log file or on restore page
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Obsidian 18.0.28, CentOS 7.8, latest MU
PROBLEM DESCRIPTION
Since the upgrade to 18.0.28 on two machines:
- The incremental backups display an error on the backup overview list. However, there is no warning message on this on top of the screen as it usually is shown when a backup is not fully valid.
- When you click on the backup name to "restore" it, there is no indication that the backup would not be fully valid.
- I did not find any issues in the backup log file either.
On a production machine where only incremental backups were done since the upgrade, all incremental backups are marked as invalid.
On an empty test machine where one incremental backup was done, then one full backup, then another incremental backup, only the first incremental backup is marked invalid while the full backup and the following increment are marked valid.
STEPS TO REPRODUCE
Create at least one full backup, then one increment.
Then upgrade 18.0.27 to 18.0.28
Then let the system create another increment on a backup plan.
ACTUAL RESULT
See problem description.
EXPECTED RESULT
Either explain why the backup file is invalid (display an error message with the log excerpt that triggers the invalid warning) or display the file as valid if it is valid.
ANY ADDITIONAL INFORMATION
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
