[google-cloud-sql-discuss] Re: Tablespace free space info is corrupted

Hi. I'm on Lucas' team.

Our backups have always been enabled, every 24h. However, when the problem started happening the backup failed as well.

This is why Lucas said "We accepted that we have lost 1 day and start the recovering work". We started working from the backup of a previous day and did all we could to recover data through other means.

We are now running on a new instance and we have left the problematic one behind. We would still like to access the old one, there might be data on it that we haven't been able to recover, it would be useful for us. The logs are still showing lots of errors constantly and we can't fix those errors directly as Lucas has explained.

Regarding the clone, we have opened a case and it has been answered. The clone is no longer an issue, thanks.

Regards,

Vitor De Mario

On Friday, January 5, 2018 at 8:23:03 PM UTC-2, Karthick (Cloud Platform Support) wrote:

Hello Lucas, 

Enabling the backup provides the best way to restore SQL instance and recover the lost data.  However, to delete your unsuccessful creation of SQL clones, I would recommend to raise a concern in google public issue tracker platform by marking the issue private. Also please provide the following information along with it, so the engineering team can assist: 

1. Project Number.

2. Name of the affected instances. 

3. Output of "gcloud sql instances delete INSTANCEID --verbosity-debug"

4. gcloud sql instances describe INSTANCEID

--
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/e8e44b99-f44d-44ef-8d85-31410cbefc03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.