[google-cloud-sql-discuss] Re: Cloudsql backup validation

Hi Sharath,

After some research and discussion, I can confirm now that there is no way to accomplish step 3 since step 2 will almost certainly fail if a backup is corrupted. In other words, the backup would not be corrupt if the restore in step 2 succeeds and restore would fail if there is actual corruption. 

- Jun

On Tuesday, May 23, 2017 at 11:25:34 AM UTC-4, Sharath Kumar wrote:

Hello there, 

We are trying to create an automated cloudsql backups validation process. We have read posts on cloudsql backups being corrupt and not being able to restore it. So we wanted to make sure the backups we take are valid!

This is our current set-up:

cloudsql-master

 - cloudsql-read-replica

 - cloudsql-failover-replica

We plan to do the following to validate our backups:

 1. create a new instance: backup-instance

 2. restore one of the backup files onto backup-instance

 3. make backup-instance a read replica to cloudsql-master

 4. run pt-table-checksum  on cloudsql-master to verify if backups are valid and in sync with master

My question is:

 - is it possible to do step 3 and 4?

 - If not is there a better way to verify the validity of cloudsql-backups?

Thanks

--
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/cf609ab6-ec13-422c-9672-aa5c946ddc25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.