All of the affected instances should now be restored. If anyone is experiencing further issues please file a issue on the Google Issue Tracker with the project and instance details.
On Thursday, March 23, 2017 at 2:42:13 PM UTC-4, Alex (Cloud Platform Support) wrote:
-- On Thursday, March 23, 2017 at 2:42:13 PM UTC-4, Alex (Cloud Platform Support) wrote:
@Bulama, the Activation Policy of a 2nd Generation Cloud SQL instance is normally set to "ALWAYS" upon being started from a stopped state or upon creation. Alternatively, you can make sure of this by calling [gcloud sql instances patch [INSTANCE_NAME] --activation-policy ALWAYS] command (more information can be found on this Starting an instance section of the Starting, Stopping, and Restarting Instances guide).@Zhen, in case you still experience this issue, can you reply to me privately with your ProjectID and Instance ID so we can help you further?
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/5bdb6d1c-ac16-4bd5-85bc-eb311c4b4b92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment