Hi Marinos, Il 23/04/11 16:00, Marinos Yannikos ha scritto:
b) set up a PITR slave (warm standby) on the same box, fail over to it, replace SAN A, then set up a PITR slave on A and fail over to it eventually
Based on what you said (on a professional basis this would require a thorough assessment), I would recommend using warm standby then switchover to the new server. This operation will give you the shortest downtime. When it is restored, switchback to the original server using the same procedure.
You can find information on this procedure in the documentation and in PostgreSQL 9 administration cookbook (http://www.postgresql.org/docs/books/).
If you are not sure you can do this by yourself, you can still contact professional companies that regularly do this kind of services around the world (mine is one of them but for a complete list: http://www.postgresql.org/support/professional_support) and let them do the job for you. Probably cheaper and safer.
Cheers, Gabriele -- Gabriele Bartolini - 2ndQuadrant Italia PostgreSQL Training, Services and Support gabriele.bartolini@xxxxxxxxxxxxxx | www.2ndQuadrant.it -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Programming PHP] [Kernel Newbies] [PHP Classes] [Find Someone Nice] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]