You could follow the steps in "How can I access transaction logs for my instances?" section of FAQ and write mysqlbinlog command based on the official MySQL documentation.You could try the following command:
mysqlbinlog -h INSTANCE_IP --user=root --password -R --base64-output=decode-rows -t --verbose LOG_NAME
For exporting any file to Cloud Storage, you could use gsutil Tool or even define a Cron job, so that you would be able to schedule making a copy of your binary log.
I hope this works for you.
On Saturday, January 13, 2018 at 12:05:50 AM UTC-5, Amit Chandel wrote:
Thanks for the quick revert, Katayoon!I am trying this approach for the first time. Due to lack of documentation around the binlog files access, this is what I thought should work (since we can setup the external replica on a GCE vm, binlog files should be accessible by the mysql user with 'REPLICATION SLAVE' privilege).Just to add more, I am using 2nd Gen cloud-sql instance.
Thanks,Amit
On Saturday, 13 January 2018 10:11:18 UTC+5:30, Katayoon (Cloud Platform Support) wrote:Could you clarify if this command has ever worked before? If yes, how recently did it stop working?For the second question, I am looking into it and come back to you shortly.
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/0e340647-4a1e-475f-8047-42744c7c6708%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment