• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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