Charmed MySQL
- By Canonical Data Platform
- Cloud
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 8.0/stable | 196 | 29 Sep 2023 | |
| 8.0/candidate | 196 | 27 Sep 2023 | |
| 8.0/beta | 196 | 25 Sep 2023 | |
| 8.0/edge | 196 | 08 Sep 2023 |
juju deploy mysql --channel 8.0/stable
You will need Juju 2.9 to be able to run this command. Learn how to upgrade to Juju 2.9.
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
How to restore backup
Hint: Use Juju 3. Otherwise replace
juju run ...withjuju run-action --wait ...for Juju 2.9.
This is a How-To for performing a basic restore (restoring a locally made backup). To restore a backup that was made from the a different cluster, (i.e. cluster migration via restore), please reference the Cluster Migration via Restore How-To:
Restoring from a backup requires that you:
- Scale-down to the single MySQL unit (scale it up after the backup is restored).
- Access to S3 storage
- Have configured settings for S3 storage
- Have existing backups in your S3-storage
To view the available backups to restore you can enter the command list-backups:
juju run mysql/leader list-backups
This should show your available backups
backups: |-
backup-id | backup-type | backup-status
----------------------------------------------------
YYYY-MM-DDTHH:MM:SSZ | physical | finished
To restore a backup from that list, run the restore command and pass the backup-id to restore:
juju run mysql/leader restore backup-id=YYYY-MM-DDTHH:MM:SSZ
Your restore will then be in progress.
Help us improve this documentation
Most of this documentation can be collaboratively discussed and changed on the respective topic in the doc category of the Charmhub forum. See the documentation guidelines if you’d like to contribute.