Tested with Everest v1.2.0-rc3 version and did not observe the issue. Manual and scheduled backups were successful with the backup storage having same bucket name, region and url as another one in a different namespace

Hi ! thank you for providing a detailed STR. The problem was fixed only partially, created a PR to fix it completely Checked the solution according to the STR - now it works as expected. The change is small and don’t affect other functionality except of creating scheduled PG backups.

Hi , I tested this with Everest v1.2.0-rc2 version and I am observing the same issue. The scenario is as follows:

Installed mysql operator in a1 namespace and pg operator in a2 namespace.

Created a mysql database with namespace1 backup storage. Enable scheduled backups and PITR.

Created a pg database with namespace2 backup storage. Enable scheduled backups and PITR.

Both namespace1 and namsepace2 have the same bucket name, region and url.

The backup in pg database gets stuck in Unknown Status. The backup schedule is created with the namespace2 backup storage but the backup is started with namespace1 backup storage.

The everest operator displays this error in logs

Attaching the everest operator log

Please check this issue, thanks.

The backup storages have different names, namespace1 and namespace2 but the bucket name, region and url are same. The scheduled backup was created using namespace1 backup storage, but Everest started the backup using namespace2 backup storage.