Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 82C589FB33D for ; Tue, 7 Aug 2007 08:29:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 76054-05 for ; Tue, 7 Aug 2007 08:29:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id B56229FB326 for ; Tue, 7 Aug 2007 08:29:54 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 07 Aug 2007 06:29:53 -0500 Message-Id: <46B8114E.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.2 Date: Tue, 07 Aug 2007 06:29:35 -0500 From: "Kevin Grittner" To: Subject: PITR backup to Novell Netware file server Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/42 X-Sequence-Number: 26373 We have a database in each Wisconsin county which is part of the official court record for the circuit courts in that county. We are required to = keep a backup in each county, such that we could recover a lost or corrupted database with what is in the county (as well as keeping at least four separate sources, each regularly confirmed as usable, at our central = site). Currently, the only two boxes available besides the database server (in = most counties) are a "utility server" (a Windows desktop class machine used to push workstation images and other support tasks) and a Novell Netware file server. =20 We had to get something going quickly when we started rolling PostgreSQL = out to the counties as a replacement of a commercial database product; the = quick and (way too) dirty approach was to create a samba share on the utility server for the target of the archive_command and our base backups. We = rsync from there back to the central site using the samba share, too. We frequently lose the mount points or they become unresponsive. We also frequently have corrupted files when they rsync across the WAN, so we want to move away from all use of samba. =20 The Netware server supports ssh, scp, and an rsync daemon. I don't see = how the ssh implementation is helpful, though, since it just gets you to the Netware console -- you can't cat to a disk file through it, for example. (At least not as far as we have been able to see.) It appears that the = scp and rsync techniques both require the initial copy of the file to be saved on the database server itself, which we were hoping to avoid for performanc= e reasons. =20 We could create ncp mounts on the database servers; but, frankly, we = haven't had much better luck in keeping those connected than we have with samba. Has anyone else been through this and found a robust and reliable way to do PITR backups from a PostgreSQL database on one machine to a Netware = file server on another? =20 Apparently we will be moving to a Linux-based implementation of Netware at some unspecified future date, at which point we will apparently be able to deal directly with the Linux layer. At that point, there are obvious, = clean solutions; but we've got to have something reasonable until such date, = which is most likely a few years off. =20 -Kevin =20