From: Chander Ganesan <chander@otg-nc.com>
To: Donald Fraser <postgres@kiwi-fraser.net>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: WAL segment question
Date: Mon, 06 Aug 2007 18:54:30 -0400
Message-ID: <46B7A6A6.9010401@otg-nc.com> (raw)
In-Reply-To: <008601c7d622$244237a0$b464a8c0@demolish1>
References: <008601c7d622$244237a0$b464a8c0@demolish1>
Donald Fraser wrote:
> Our company has two sites, a master and a disaster recovery site.
> I am trying to assess whether data has been lost during a fail-over,
> due to the asynchronous method of transporting WAL file data between
> sites (we use DRBD).
>
> Disaster recovery node start-up log:
> user= pid=9907 timestamp=[2007-08-01 17:09:51 BST] tid= LOG: record
> with zero length at 0/7C62F52C
> user= pid=9907 timestamp=[2007-08-01 17:09:51 BST] tid= LOG: redo
> done at 0/7C62F4E8
>
> My question is: given the above WAL segment information, can I use it
> to decide whether information was lost in the master database site, at
> the point of failure, without starting the database up?
>
> Regards
> Donald Fraser.
DRBD is a synchronous method of transferring data - it's not
asynchronous. Assuming you are using Protocol C you should find that
both are always in sync. If you are using protocol B then things will
be in sync so long as the remote system didn't crash, and if you are
using Protocol A then things should be in sync as long as the local
system didn't crash.
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/866-229-3386
http://www.otg-nc.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: chander@otg-nc.com, postgres@kiwi-fraser.net
Subject: Re: WAL segment question
In-Reply-To: <46B7A6A6.9010401@otg-nc.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox