Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id C0E769FB78C for ; Tue, 7 Aug 2007 21:39:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 20760-05 for ; Tue, 7 Aug 2007 21:39:07 -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 407E79FB739 for ; Tue, 7 Aug 2007 21:39:12 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 07 Aug 2007 19:39:10 -0500 Message-Id: <46B8CA47.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.2 Date: Tue, 07 Aug 2007 19:38:47 -0500 From: "Kevin Grittner" To: "Decibel!" Cc: Subject: Re: PITR backup to Novell Netware file server References: <46B8114E.EE98.0025.0@wicourts.gov> <20070807182800.GJ25704@nasby.net> <46B87DCD.EE98.0025.0@wicourts.gov> <20070807215139.GT25704@nasby.net> In-Reply-To: <20070807215139.GT25704@nasby.net> 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/56 X-Sequence-Number: 26387 > >>> Decibel! 08/07/07 4:51 PM >>>=20 > On Tue, Aug 07, 2007 at 02:12:29PM -0500, Kevin Grittner wrote: > > > 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 will > > normally have a database vacuum analyze between the base backup and = the users > > 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 don't > > tend to bang on the database very heavily, they hate to be made to = wait. >=20 > 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. Thanks for the suggestions. A new OS is not in the cards any time soon, = but I think the --bwlimit option makes sense -- there's not a lot of point = moving it from the database server to the file server faster than the WAN can = take it, anyway. I suppose I could "nice" the rsync requester on the database = side, too. =20 -Kevin =20