You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 6, 2022. It is now read-only.
When creating service instance we can specify what are the backup settings. Is it possible, though, to use those backups, to restore (using OSBA) the backup into the new service instance?
I'd like to create kubernetes based CI/CD pipeline which will build a new application environment automatically, using an existing database as a starting point.
If possible I'd like to avoid mysqldump-ing the data and manual data restore as much as possible since the database in question has few GB of data and manual import via mysql ... < dump.sql takes way too long for my liking.
The text was updated successfully, but these errors were encountered:
Both restoring backup into new service instance and creating new service instance from an existing database are not supported.
The scenario makes sense to me. Actually SQL Server in OSBA implemented using existing database. That was a big refactor. And as a result, the usage of the module got more complicated and maybe also a little confusing. I really not sure whether it was a good change. So sorry there is no plan to support the scenario for MySQL yet :(.
I'd like to keep this issue open. Appreciate more feedback.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When creating service instance we can specify what are the backup settings. Is it possible, though, to use those backups, to restore (using OSBA) the backup into the new service instance?
I'd like to create kubernetes based CI/CD pipeline which will build a new application environment automatically, using an existing database as a starting point.
If possible I'd like to avoid mysqldump-ing the data and manual data restore as much as possible since the database in question has few GB of data and manual import via
mysql ... < dump.sql
takes way too long for my liking.The text was updated successfully, but these errors were encountered: