[google-cloud-sql-discuss] Re: Cloud SQL skipping backups even if there are changes

Hey Stevie,

A backup will skip if the instance has been idle since the last backup. If you feel that this isn't the case, this represents a potential production issue which should be reported in the Cloud SQL Public Issue Tracker. When reporting an issue, provide as much technical information about your system as possible, timeline of events, any relevant ID's, and we'll be able to take a look at the issue.

Sincerely,

Nick
Cloud Platform Community Support

On Tuesday, April 26, 2016 at 8:28:04 AM UTC-4, Stevie Frederick wrote:

The automatic backup skipped the last 4 scheduled backups:

DUE_TIME                          ERROR  STATUS

 

2016-04-25T14:00:00.344000+00:00  -      SKIPPED

2016-04-24T14:00:00.814000+00:00  -      SKIPPED

2016-04-23T14:00:00.769000+00:00  -      SKIPPED

2016-04-22T14:00:00.909000+00:00  -      SKIPPED

2016-04-21T14:00:00.527000+00:00  -      SUCCESSFUL

Even though there were changes in the database. My other GCloud SQL instances have continued on their schedule however.

Any ideas why this is happening? I haven't been able to find anything in the support documents.

Bests,

-Stevie

--
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/24723f57-6ce3-4f3e-ae04-377c48170a28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.