We’re making developers lives easier by allowing granular control of their backups and restores. The backup command still handles both backups together, but there are times when you simply need to backup files (volumes) or just backup and restore databases.
We noticed that developers had the need to restore parts of the backup when testing as opposed to restoring both database and files together. The new functionality allows developers to target exactly what they need.
With the new release v0.28.0 you’ll be able to:
- List, backup and restore a MySQL database
- List, backup and restore volumes
The technical benefits
Granular Control
You can now individually backup and restore the MySQL database of the application or just the Volumes (files and other assets). This means that when you don’t need to restore either one, you can simply backup and restore the one you need to, saving time and complexity in the process.
Speed
Now that you can split backups, there’s no need to wait for them all to finish–saving on time.
More transparency
The ability to just list the MySQL, volume backup or restore processes helps identify which is taking longer or which one is holding up the backup or the restore. This can help debug or identify issues with either (database or volumes) when running the backups or restores.
CI/CD Pipeline friendly
Now that we have granular control over what we backup, we can integrate into new places in the CI/CD pipeline e.g. Database backup before deployment. This way we can backup what we truly need to, saving time on nightly backup pipelines and optimising storage.
Your Next Steps
- MySQL Backup Create: Create MySQL backups for an environment.
- MySQL Restore Create: Restore a MySQL backup to an environment.
- Volume Backup Create: Create Volume backups for an environment.
- Volume Restore Create: Restore a Volume backup to an environment.