Re: PG migration policy

In addition to all this, you will need to outline an actual plan for
the migration itself:

1) Steps to migrate
2) Testing strategy to ensure the migration actually worked
3) Estimated time
3a) How much of that time is actual downtime
4) Fallback plan in case the migration fails

For such documents, we also include a checklist for everything that needs
to be done so that it can be signed off at each step of the process.

I didn't see "monitoring" on Sim's list, but in addition to the stuff you
monitor for any server, you'll need to monitor DB-specific stuff like
table bloat, slow queries, etc.

On Sun, 29 Jan 2012 10:14:21 +0200 Sim Zacks <sim(at)compulab(dot)co(dot)il> wrote:

> You are moving to a dedicated server for a reason, most probably
> performance.
> The intro section of the document should discuss the reasons you are
> moving and what you hope to accomplish.
>
> Hardware - The discuss the new platform that you are moving to, in terms
> of how it will perform better. Important aspects are memory, disk speed,
> RAID set up, cpu (not so much).
>
> Server Configuration
> Include:
> * Kernel compile options
> * params such as shmmax
> * file system chosen
>
> Postgresql Configuration:
> List each option you are going to change and values you are planing on using
>
> Backup strategy
> How often backups will be taken, where they go, if there is an offsite
> plan, how often restores are tested.
>
> HA strategy
> What are you plans if the server dies.
>
> You should also have a test server where you can test changes without
> affecting production. It should have the same configuration as the primary.
>
>
>
> On 01/29/2012 08: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.
> >
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

--
Bill Moran <wmoran(at)potentialtech(dot)com>