We need to migrate a CloudSQL PostgreSQL 12 database from one GCP account to another, and currently there's no automatic / 'cloudy' solution offered by Google to perform this.
Its a critical online database that cant stop for a multitude of reasons
Im looking to implement the following process.
0- Setup primary as replica source, and increase WAL files retention time
1- take a PITR backup of primary
2- restore the PITR backup as a new database server
3- Make the necessary changes on the primary and standby to activate stream replication
4- Use standby as read replica to test the application for a short period of time to test if its allright.
5- switch off the primary and activate the app on the newly promoted standby to primary
May i ask if someone have a step by step procedure as reference for this?
Also, if choosing logical replication , is it possible to keep the PITR in the same way?
Thanks
Alexandre
A CloudSQL PostgreSQL database replicated to another GCP account, initially thru PITR restore, then using stream replication and zero downtime for switchover/takeover manually by the second one.
Once the standby is up to date with the primary (LSN, and so on), it will take over as primary (or even standalone) , then to shut down the application, and point it to the standby now as primary
I could see that i could use pglog
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/ca217fd0-0ac7-4c20-b961-e5ff67caa8e8n%40googlegroups.com.
No comments:
Post a Comment