X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 422C59FB33A for ; Wed, 6 Sep 2006 22:15:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 99550-05 for ; Wed, 6 Sep 2006 22:15:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from hub.org (hub.org [200.46.204.220]) by postgresql.org (Postfix) with ESMTP id 260739FB336 for ; Wed, 6 Sep 2006 22:14:49 -0300 (ADT) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 3F7AA291AFB for ; Wed, 6 Sep 2006 22:14:43 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 01050-01; Wed, 6 Sep 2006 22:14:33 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id DE2CB290C2B; Wed, 6 Sep 2006 22:14:27 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 8485837B13; Wed, 6 Sep 2006 22:14:38 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 8103C36A59; Wed, 6 Sep 2006 22:14:38 -0300 (ADT) Date: Wed, 6 Sep 2006 22:14:38 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Dave Page cc: Christopher Browne , pgsql-hackers@postgresql.org Subject: Re: gBorg status? In-Reply-To: Message-ID: <20060906221100.S13992@ganymede.hub.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.495 tagged_above=0 required=5 WHITELISTED tests=AWL, FORGED_RCVD_HELO, RCVD_IN_DSBL X-Spam-Level: * X-Archive-Number: 200609/621 X-Sequence-Number: 90150 On Mon, 4 Sep 2006, Dave Page wrote: > My understanding is that Gborg is being recovered from backup as I type. > I also understand that the delay was not caused by lack of backups or > anything similarly scary, but simply by other priorities. Yes, I have the backup uploaded right now, and doing 'recover procedures' as I type this ... it will be up before I go to bed tonight ... As for the 'other priorities' ... the delay was due to an insufficient Internet connection to upload the backup ... we were waiting for our Internet to be installed in our new location, and were using an underpowered temporary connection in the interim ... that one was going to tie up the connection for >40 hours ... once we were able to get the backup server onto its 'permanent connection', the upload took ~5hrs ... As I mentioned, am working on it right now ... will post a follow up once she's back up live and needing to be tested ... she's also moving to one of our 64bit servers, so should be a wee bit better performance wise ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664