• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Input Backup and restore of MySQL database should handle correctly views

carini

Basic Pleskian
When attempting to restore databases, the process fails to recreate database views. This seems to be a significant oversight in the restoration functionality (see support request Id #95245922)

During a database restore procedure, all table data is correctly reinstated; however, views are not being recreated. The expectation for a restoration process is a complete replication of the original database state, which includes tables, views, stored procedures, etc. Currently, the absence of views post-restoration necessitates manual intervention, which is not feasible in scalable environments.

Storing and subsequently executing the SQL queries used to create views during the backup phase is entirely feasible. Implementing this would ensure that views are restored accurately, maintaining the integrity and utility of the database post-recovery.
 
Issue has not be recognised as a bug as per Id #95245922. So I opened the request for future improvement.
 
Back
Top