Cloud SQL skipping backups even if there are changes
37 views
Skip to first unread message
Stevie Frederick
Apr 26, 2016, 8:28:04 AM4/26/16
to Google Cloud SQL discuss
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 - SUCCESSFULEven 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
paynen
May 9, 2016, 4:24:04 PM5/9/16
to Google Cloud SQL discuss
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
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
Reply all
Reply to author
Forward
0 new messages