Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7CF552E01BA for ; Tue, 4 Mar 2008 18:07:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35223-01 for ; Tue, 4 Mar 2008 18:07:52 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by postgresql.org (Postfix) with ESMTP id 287622E0088 for ; Tue, 4 Mar 2008 18:07:51 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id j3so2524868ugf.49 for ; Tue, 04 Mar 2008 14:07:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=As53zPDrx/GY8N2LX5trE9HJWWDS3YYvlnMAQosUpj8=; b=w6lJ+RiTOAVu+aYuYtbUmOOQJvvlqs6/RkxfsZClcQHh6wbHOyydm0roHInNluGU0iRSzUJizqg0ry9J/Gf03cBrHKCEnkgfjBxGdVzNh7cg1gubSpbJPM7iTaeb5oqAaT7sGSuvz/T0MuVKN5lRp5dtdjVKVOcMINbTmhDVMJw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=P3Sv7LAFieY9KOq3MGeJr0YZ/BFGEhYhpybvGdVvsqDYnR0BINZPl6pUAeadr3ucqaSSsz4eMVVwI2nwWc4TnjdpBEdxQ5+oulHcmWZZd41WozArxJZo57x7sAC4vXJLs8YaLiHiCF1U50JKe5hwKNzVWtXcRZlqmcgAW/zr+gg= Received: by 10.78.201.8 with SMTP id y8mr4776436huf.18.1204668470411; Tue, 04 Mar 2008 14:07:50 -0800 (PST) Received: by 10.78.170.2 with HTTP; Tue, 4 Mar 2008 14:07:50 -0800 (PST) Message-ID: <9abe84da0803041407u3abd92a6oc4ab099f5c3b2d1b@mail.gmail.com> Date: Tue, 4 Mar 2008 17:07:50 -0500 From: "libra dba" To: pgsql-general@postgresql.org Subject: using warm standby with drbd??? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13639_29255947.1204668470404" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200803/28 X-Sequence-Number: 28511 ------=_Part_13639_29255947.1204668470404 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi All! I have configured the warm standby using WAL FILES and DRBD. The wal files are generated as server A. I am using DRBD to replicate these wal files between server A and server B. The DRBD service is running as Primary on Server A and secondary on Server B. The wal_files are written to the server B, but there is a drawback for DRBD. The filesystme needs to be unmounted on the server B (where DRBD is running secondary role). So recovery is not countinuous.(file systme is unmounted). To start the recovery, i need to change the DRBD role to primary on server B. After that i have to mount the filesystem. Once i mount the filesystem, the recovery process starts. Is there any way in which i need not switch secondary/primary role for DRBD on server B? Is there any way in which i can have the file system mounted on server B, running DRBD secondary role? How else can i replicate the wal_files? ( i don't want to user common file system ,,, NFS,,, etc.)? Another thing which i want to ask is that if we are generating archives every 1 minute. then what happens to the data which was written to the server A after 35 seconds after the last wal file generation.(server A crashes). Since this data has not been archived (it was supposed to archive after 1 minute), do i think that this is the loss of data in a server A crash as this 35 second data has not been written to the archived logs and neither has been transported to server B? A quick reply is highly appreciated! Thanks! ------=_Part_13639_29255947.1204668470404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi All!

I have configured the warm standby using WAL FILES and DRBD. The wal files are generated as server A. I am using DRBD to replicate these wal files between server A and server B. The DRBD service is running as Primary on Server A and secondary on Server B. The wal_files are written to the server B, but there is a drawback for DRBD. The filesystme needs to be unmounted on the server B (where DRBD is running secondary role).

So recovery is not countinuous.(file systme is unmounted). To start the recovery, i need to change the DRBD role to primary on server B. After that i have to mount the filesystem. Once i mount the filesystem, the recovery process starts.

Is there any way in which i need not switch secondary/primary role for DRBD on server B?
Is there any way in which i can have the file system mounted on server B, running DRBD secondary role?


How else can i replicate the wal_files? ( i don't want to user common file system ,,, NFS,,, etc.)?

Another thing which i want to ask is that if we are generating archives every 1 minute. then what happens to the data which was written to the server A after 35 seconds after the last wal file generation.(server A crashes).

Since this data has not been archived (it was supposed to archive after 1 minute), do i think that this is the loss of data in a server A crash as this 35 second data has not been written to the archived logs and neither has been transported to server B?

A quick reply is highly appreciated!

Thanks! ------=_Part_13639_29255947.1204668470404--