This repository was archived by the owner on May 28, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 236
Backup Issue in S3 bucket #212
Comments
see this too, may look into it when have a chance. |
Thanks for the bug report @JJSWAIN2018. I believe the issue is that the agent backup and restore controllers only check if the backup/restore is scheduled before processing rather than also checking the mysql-operator/pkg/controllers/backup/agent_controller.go Lines 128 to 143 in ee732cf
mysql-operator/pkg/controllers/restore/agent_controller.go Lines 138 to 152 in ee732cf
|
Resolved by #213 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Backup Issue in S3 bucket
Choose one: BUG REPORT
Backup Issue in S3 bucket
Versions
MySQL Operator Version: 0.2.0
Environment:
kubectl version
): 1.11uname -a
):What happened?
When we take backup in both on-demand as well as schedule backup . multiple database .sql.gz files
are stored in S3 bucket .
Name Size Type Storage class Last modified Private access Encryption
db-cluster-db-backup.20180827153653.sql.gz 891.6 KB — Regional 8/27/18, 9:06 PM
db-cluster-db-backup.20180827153654.sql.gz 891.6 KB — Regional 8/27/18, 9:06 PM
db-cluster-db-backup.20180827153656.sql.gz 891.6 KB — Regional 8/27/18, 9:06 PM
What you expected to happen?
Only one backup file should be stored in s3 bucket in on-demand backup .
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
The text was updated successfully, but these errors were encountered: