On 01/29/2012 12:30 AM, Allan Kamau wrote:
Hi, This is definitely off topic, I apologize. We are planning to move our PostgreSQL installation from a shared server to a dedicated server. I have been given the responsibility of writing a migration policy document for this operation. This would be my first such document to put together, I am looking for pointers, samples and so on on which to build this document for our scenario. Allan.
When our office moved location, and thus ISP's, we layed out a simple plan to keep our websites up at all time. Our plan, 100% uptime while loosing no client updates. We layed out a time line, and on it what would happen and when. We tried to come up with problems and solutions, etc. Having a fallback wasn't really an option, because we were moving, its not like we could just give up and stay. But we had safety nets and backup options (including run a copy of the webserver VM from my house). DNS update was our biggest stumbling block, so we had to run two web servers concurrently, so that some people could hit the new and some could hit the old. And updates would find their way to the right spots. -Andy -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
