Suggestion: Ask for confirmation before restoring potentially incompatible backup

Post Reply
bruno.ph
Posts: 1
Joined: Sat Jan 30, 2021 5:54 pm

I have moved from a VestaCP server to a freshly installed myVesta setup. Sadly I did not notice that myVesta installs MySQL by default, where my previous server used Postgres. However the backup script was happy to restore that backup. I did not have any critical data in my old server DBs so I didn't notice it, and it's not a critical issue, however it broke automatic backups, because the backup script was attempting to read the Postgres configuration file in

Code: Select all

/usr/local/vesta/conf/pgsql.conf
Attempting to simply delete the database entry also failed for the same reason. It would be nice if there was a check when restoring a backup from the command-line to make sure things were set up as desired.

I was able to fix backups by adding the name of the Postgres database to the backup exclusions list, so it's all good.

Thanks for the great software!
User avatar
myVesta
Site Admin
Posts: 928
Joined: Fri Jun 19, 2020 9:59 am
Has thanked: 8 times
Been thanked: 6 times

Probably you can manually delete entries from /usr/local/vesta/data/users/yourusername/db.conf
Post Reply