• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs Server backup claiming issues since upgrade to 18.0.28 without issues visible in log file or on restore page

Bitpalast

Plesk addicted!
Plesk Guru
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.

plesk01.jpg


plesk02.jpg


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
 
Thank you, Peter.
Internal request PPPM-12110 has been created.
 
Back
Top