Search Postgresql Archives

Postgres, High Availability, patching servers sequentially

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi:

version 9.6 on linux
Our IT dept configured our DB to be "High Availability" a couple months back.  I believe this means there's a backup server and disks that mirror the main and can kick in should main go down.

They need to install a patch on the servers which will require server downtime.  Is there a way we can leverage the fact that there are two servers, do them sequentially, without causing any effective downtime for the users ?  I'm thinking something like...

- Disconnect the backup DB from the main.  No longer a HA at this point but that's OK for the short term.

- Patch that backend server then bring it back up.

- Reconnect it to the main DB as the backup.  I'm thinking it should sync with the main and get the user changes/edits that happened while the thing was being patched.

- Switch the roles of the main and the backup. 

- Disconnect the second server, patch it, bring it back as the backup.  Back to HA.

 



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux