You can try importing the MySQL DBs from the external resource to Cloud SQL by assigning a higher resources (machine type) compared to what normally it would be required. You might use those machine types with higher memory so that it could be able to do the export-import operation on a minimum amount of time. This would help you to perform the whole operation on a much lower downtime.
You can check this help center article for various machine types available for the Cloud SQL instance and choose the appropriate one that might do your operation on less amount of time.
After importing the db to the CloudSQL, you can downgrade the machine type of the Cloud SQL to a lower tire.
Additionally, you might also need to check this best practice guide for importing and exporting MySQL data as well. Also, check the section where it has provided some tips if you are having a long-running import and export processes.
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/88908c41-b197-45a8-b00b-c451f59700b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment