• 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.

Database restoration from backup fails when using AWS RDS (or when...)

Issue

Database restoration from backup fails when:

Using a remote database && database admin user registered with Plesk is not a super user

This is a specific annoyance for any providers using Amazon RDS to host their database(s). Amazon RDS does not grant a super user account to the client, only an account with the following privileges:

SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER,SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, EVENT, TRIGGER, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EXECUTE​

Moreover, it is not necessarily best practice to register a MySQL super user with Plesk even if possible.

Root Cause

The restoration script attempts to grant super privileges to a temporary user for database import/export. Excerpt from deployer.log:

INFO: Executing utility: /usr/bin/mysql --no-defaults -u [remote_rds_admin] -h [remote_rds_server] -P 3306 -e GRANT\ ALL\ ON\ \*.\*\ TO\ \`backup_64G9Dqz\`@\`%\`\;\ FLUSH\ PRIVILEGES\;

This fails unless executed by a super user. [remote_rd_admin] is not a super user.

Suggest Fix

Change statement to GRANT SELECT, INSERT, UPDATE, CREATE, DROP, RELOAD, SHUTDOWN, FILE, INDEX, ALTER, SUPER, LOCK TABLES, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, TRIGGER, CREATE ROUTINE, DELETE, EVENT, ALTER ROUTINE ON *.*

or just use the administrative user registered with Plesk for backup operations?

(caveat: I am not a DBA and am not sure if those are the correct grants for dump/import)

Anyways, thanks for the great product!
 
Back
Top