From: | Jov <amutu(at)amutu(dot)com> |
---|---|
To: | Jeni Fifrick <jfifrick(at)incomm(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Suggestion on Backup |
Date: | 2013-10-16 03:41:01 |
Message-ID: | CADyrUxMFT7TFuQ50vrxFKgRbe88Gd4J+KCODmfyvoP+=yGuC6g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Why not configure one more slave.so you can maintenance any server with
other two on production.
Jov
blog: http:amutu.com/blog <http://amutu.com/blog>
2013/10/16 Jeni Fifrick <jfifrick(at)incomm(dot)com>
> We’re having Master & Slave Postgres 9.1.3 on CentOS – using Streaming
> Replication, which serve as a read-only database, and as ‘backup’ for the
> production database.****
>
> The current backup mechanism is using pg_dump. ****
>
> ** **
>
> We’re in need to do maintenance process that required the server to be
> taken down.****
>
> So, during that time, we only have 1 Production server.****
>
> ** **
>
> I’m trying to setup a process that can be used to have the continuous
> backup of the production, to make sure if some problems happen on the
> production server, we won’t loss the data.****
>
> ** **
>
> Could you experts give me suggestion on the best way to achieve this?****
>
> And detail on how to achieve it? ****
>
> ** **
>
> Thanks in advance,****
>
> Jen****
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriele Bartolini | 2013-10-16 06:51:15 | Re: Suggestion on Backup |
Previous Message | Jeni Fifrick | 2013-10-15 21:09:50 | Suggestion on Backup |