Skip to:
Tested in Everest v0.10.0-rc5 version.
Create a mysql/mongodb database, enable scheduled backups and PITR.
After some backups, restore the same database using a backup.
After the database comes up, delete it. The database is removed, but the restore still remains in the namespace.
For example, this is the list of databases remaining
These are the database restores
The databases mysql-t22, restored-mysql-2, restored-mysql-aft-upg have been deleted but there restores are still remaining.
This issue was not observed in Everest v0.10.0-rc6 version.
If recreate the database with the same name as deleted one, then it doesn't come up and the same restore gets associated with it
Tested in Everest v0.10.0-rc5 version.
Create a mysql/mongodb database, enable scheduled backups and PITR.
After some backups, restore the same database using a backup.
After the database comes up, delete it. The database is removed, but the restore still remains in the namespace.
For example, this is the list of databases remaining
These are the database restores
The databases mysql-t22, restored-mysql-2, restored-mysql-aft-upg have been deleted but there restores are still remaining.