Cloud SQL backup failing with "Unknown error"

[Gustavo Rocha]

The instance seems to be stuck with failing backup operations. The last successful backup was made on November 12 and since then the instance has been stuck trying (and failing) to create a new backup.

This is a db-f1-micro instance used for development, it only has 3 out of 20 GB used (meaning there is more than enough free space) and I can connect to and query the instance the just fine.

It is a second gen MySQL instance with no replication or HA. I could make a dump of the data and recreate everything on another instance, but I'm not even sure I would be able to delete this instance while it is stuck on this state.

Anyone has any idea on how to "unstuck" it?

Regards,

Gustavo Rocha.

Esta mensagem e seus eventuais anexos podem conter dados confidenciais ou privilegiados. Se você a recebeu por engano ou não é um de seus destinatários, elimine imediatamente a mensagem e seus eventuais anexos ou cópias e comunique o remetente. É proibida a divulgação, distribuição, retenção ou utilização através de qualquer meio das informações contidas nesta mensagem. Agradecemos sua colaboração.

This message may contain confidential and/or privileged information. If you are not the addressee or if you are not authorized to receive this message on behalf of the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message by mistake, please inform the sender immediately by replying this e-mail and delete this message. Thank you for your cooperation.

[Kenworth (Google Cloud Platform)]

Hi Gustavo, a thread like this is off-topic for Google Groups. As it may potentially be a defect on the platform and most likely lead to a specific situation which may require some exchange of project information to reproduce the behavior you described, I highly encourage you to submit a defect report as described in this article so that proper attention and weight will be given to it. We monitor that issue tracker closely.

We look forward to this issue report.