Tested with Everest vv0.0.0-d762746 version.
Create a mongodb database of 3 nodes. Enable scheduled backups and PITR.
Take some scheduled backups
Delete the database.
Create a new database with the same name as mongodb-g97
mongodb-g97
After creation, the backups of the old database are available in the new database
The backups of the old database shouldn’t be associated with the new database as the new database may be owned/created by a different user.
Tested with Everest v0.0.0-4dac952 version and did not observe any issues. Now the backups are deleted after a database is deleted, hence if a new database with the same name is created, the old backups are not available.
Tested with Everest vv0.0.0-d762746 version.
Create a mongodb database of 3 nodes. Enable scheduled backups and PITR.
Take some scheduled backups
Delete the database.
Create a new database with the same name as
mongodb-g97
After creation, the backups of the old database are available in the new database
The backups of the old database shouldn’t be associated with the new database as the new database may be owned/created by a different user.