Topic 1 Question 108
You want to migrate your on-premises PostgreSQL database to Compute Engine. You need to migrate this database with the minimum downtime possible. What should you do?
Perform a full backup of your on-premises PostgreSQL, and then, in the migration window, perform an incremental backup.
Create a read replica on Cloud SQL, and then promote it to a read/write standalone instance.
Use Database Migration Service to migrate your database.
Create a hot standby on Compute Engine, and use PgBouncer to switch over the connections.
ユーザの投票
コメント(4)
- 正解だと思う選択肢: D
B - we're not talking CloudSQL here C - you can only migrate PostgreSQL to CloudSQL for PostgreSQL or AlloyDB for PostgreSQL A is kinda fine, but D is better
👍 3chelbsik2022/12/26 D PgBouncer maintains a pool for connections for each database and user combination. PgBouncer either creates a new database connection for a client or reuses an existing connection for the same user and database. + PgBouncer is a simple PostgreSQL connection pool that allows for several thousand connections at a time. Using Kubernetes Engine to run a Helm Chart w/ PgBouncer based on the great article from futuretech-industries, we were able to set up an easily deployable system to get the most out of our CloudSQL DBs without breaking the bank. https://medium.com/google-cloud/increasing-cloud-sql-postgresql-max-connections-w-pgbouncer-kubernetes-engine-49b0b2894820#:~:text=That%20is%20where,breaking%20the%20bank.
👍 3Atnafu2022/12/30D: Create a hot standby on ***** Compute Engine, and use PgBouncer to switch over the connections. To perform the migration, you shut down the current master and then promote the subordinate Google Cloud replica to master. PgBouncer reroutes traffic to the new master node on Google Cloud.
👍 1pk3492022/12/24
シャッフルモード