Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 00CA79FB6D6 for ; Tue, 7 Aug 2007 18:51:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 95989-02 for ; Tue, 7 Aug 2007 18:51:39 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 397B69FB5A7 for ; Tue, 7 Aug 2007 18:51:43 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id E48AE564B6; Tue, 7 Aug 2007 16:51:41 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Tue, 7 Aug 2007 16:51:39 -0500 Date: Tue, 7 Aug 2007 16:51:39 -0500 From: Decibel! To: Kevin Grittner Cc: pgsql-admin@postgresql.org Subject: Re: PITR backup to Novell Netware file server Message-ID: <20070807215139.GT25704@nasby.net> References: <46B8114E.EE98.0025.0@wicourts.gov> <20070807182800.GJ25704@nasby.net> <46B87DCD.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YX3j2TVtVK6AUAU8" Content-Disposition: inline In-Reply-To: <46B87DCD.EE98.0025.0@wicourts.gov> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070807:kevin.grittner@wicourts.gov::8byllIRPnaLzOSOx:0000000000 000000000000000000000000BhTL X-Hashcash: 1:20:070807:pgsql-admin@postgresql.org::Iv1xZKkYzHBSD0zS:00000000000 0000000000000000000000005P7/ X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/53 X-Sequence-Number: 26384 --YX3j2TVtVK6AUAU8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 07, 2007 at 02:12:29PM -0500, Kevin Grittner wrote: > > 2) Have archive_command copy to someplace on the database server, and > > have another process copy from there to both the local backup as well as > > the central backup. > =20 > A possible option; although if the rsync daemon on the file server proves > reliable, I don't see the benefit over having the archive command make a = copy > on the database server which flows to the file server and from the file s= erver > back to the central site. I'd rather add the load to the file server tha= n the > database server. Yeah, if you can make that work reliably, then I agree it's probably better. > > Copying a 16MB file that's already in memory isn't exactly an intensive > > operation... > =20 > That's true for the WAL files. The base backups are another story. We w= ill > normally have a database vacuum analyze between the base backup and the u= sers > being in there to care about performance, but that's not always the case = -- > sometimes jury trials go late into the night and could overlap with this a > base backup. And some judges put in a lot of late hours; although they d= on't > tend to bang on the database very heavily, they hate to be made to wait. Ahh... well, that's something where rsync could actually help you since it allows you to put a bandwidth cap on it. Another option is that some OSes (FreeBSD for one) will respect process priority when it comes to scheduling IO as well, so if you nice the backup process it hopefully wouldn't impact the database as much. --=20 Decibel!, aka Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) --YX3j2TVtVK6AUAU8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGuOlrdO30qud8SkgRAt0XAKCHo6b/YmULciTmMyllCi6RhRUfZACbBcsv isBC2/5pzI8cqSV3lBjFiSQ= =P/dQ -----END PGP SIGNATURE----- --YX3j2TVtVK6AUAU8--