Backup fails after VestaCP import

After importing a VestaCP backup, HestiaCP backups have stopped working. The problem stems from the fact that the VestaCP dump contained MySQL databases but in the new instance, that database is not running. Since then the backups throw the following error:

2023-05-29 08:10:03 admin_default (mysql)
grep: /usr/local/hestia/conf/mysql.conf: No such file or directory

How can I deactivate this database that doesn’t really exist?