On 9/6/16 10:53 PM, John R Pierce wrote:
1) setup new streaming slave at new provider using 9.2, wait for replication to complete and satisfy yourself that the database is complete and intact. 2) shut down master at old provider (and any other slaves), promote new provider 9.2 to master. 3) pg_upgrade using --link option to 9.4 on new provider. if this fails, restart old master and start over at step 1 4) bring up applications on new database. if they fail, restart old master, and start over at step 1 5) bring up new slave(s) on new database.
Or if you want, upgrade on your existing provider first, then setup streaming replication. But no matter what, pg_upgrade will require some form of downtime.
You could also use either Slony or londiste to directly migrate from Rackspace to an EC2 instance on 9.5; no need for DMS at all. That has the added benefit of allowing you to switch to a new version with virtually zero downtime (as in seconds if you script it) and allowing you to maintain the old version (along with any new data changes) in case you need to fail back (without data loss).
Keep in mind that in this case you're really only using DMS as a form of replication, so you might be better off just sticking with Postgres tools.
-- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
