Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id ED4529F95CB for ; Tue, 21 Aug 2007 05:53:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 91455-09 for ; Tue, 21 Aug 2007 05:53:41 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.187]) by postgresql.org (Postfix) with ESMTP id 754499F9502 for ; Tue, 21 Aug 2007 05:53:40 -0300 (ADT) Received: by fk-out-0910.google.com with SMTP id b27so1546311fka for ; Tue, 21 Aug 2007 01:53:38 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=RTU8Vovv57RLP0OEWmlG3U/QlmXJmIEnXtlUP1LnJ6ipLKtmo3pLfu8pS0NQeYJBl4x8A+FQGSabcmmJxEYWy3l+g+SphozudwcNpxNYCO9/I0fY2tU+AIHbHBUaWhUwAI7Pk54F5uVbGjmT61QoquPSuquC9a5f5+auYjLNQXg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=kj5x9grIzEwh7I6BWJPIlqkE8YOgbpNpsUyJDcz2qnlTzId103mGcHGjUyz25a4WWtETOvVDeMj1bpYTA4anc2h9iAS9rt4iTJrgTNVUEd/KrWqGfl4pFsdwo2O3XT9JBcryzizoKvEDBNzr3DcRthNUwWpH5XL1n3M0mE8iNEg= Received: by 10.82.136.4 with SMTP id j4mr9901689bud.1187686415794; Tue, 21 Aug 2007 01:53:35 -0700 (PDT) Received: from ?192.168.1.199? ( [80.35.110.41]) by mx.google.com with ESMTPS id 1sm1683871nfv.2007.08.21.01.53.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 21 Aug 2007 01:53:26 -0700 (PDT) Message-ID: <46CAA800.6080803@gmail.com> Date: Tue, 21 Aug 2007 10:53:20 +0200 From: Luis Perruca User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: SOS. Database Lost References: <16e1f7ed0708200324w227a4f86q4fd3337f4a402f00@mail.gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------000301080307060507020708" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/245 X-Sequence-Number: 26576 This is a multi-part message in MIME format. --------------000301080307060507020708 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Scott Marlowe wrote: > On 8/20/07, luis perruca wrote: > >> Hi All: I'm From Spain and I'll try to write in english as best as possible: >> > > Your english > my spanish, so please don't worry. > > >> I'm new in the list, and I have a serious problem: I am novice with >> Postgresql and I haven't found any solution. >> I Wil descrive the scenario: >> >> I have Postgresql 8.0.1 running on Windows 2003 Server. >> I have a Backup of my database, but is a little old >> > > A pg_dump type backup, or a file system backup? > > A file System backup >> And here is my problem: >> >> First, the Postgresql service didn't started (really started, but shut down >> immediatly) >> > > What steps led to this happening. They might be important. > > Did you install new /update software on this server? Especially > anti-virus software? That stuff's nearly as dangerous as a virus > itself for a database. > > What are the exact error messages you got when this happened. > > I don't remember exactly the error, but says something like "the service started and then shut down. (some services shut down when have nothing to do)". This really says nothing. >> then I copied all the "postgresql" folder in other place, uninstalled and >> reinstalled Postgresql, and then overwrite the "data" folder with the one >> from the copy that I did. >> > > Did you shut down postgresql while you were copying those files back? > Yes, postgresql was down when restoring the folder. > >> Now, the service starts properly, but the database doesnīt work. I did >> "pg_resetxlog" (I donīt know what it does, but I saw it somewhere). >> > > It reselts the transaction log pointer. It has likely set back in > time to when there was nothing in the database. Just guessing. > > >> From pgAdmin III, I see the database, I access it, I see the tables and >> their properties, but no data. I get the error "xlog flush request >> 6D/432AAAA8 is not satisfied --- flushed only to 0/C03D020 CONTEXT: writing >> block 925 of relation 16631/17254/18128" when I try to view the tables >> > > Have you still got that old pg directory? Try shutting down pgsql, > copying the data part back in place, and restarting pgsql and see if > it starts up right or not. > The service starts, but with the errors that I have told: I see the tables but I get error or no data. > >> I would need to know if I can recover the data from the tables and how to do >> it. >> > > Can't tell from what you've told us so far. Need more info of how you > got into this state and exact error messages you're getting as well. > > My one piece of advice would be that if you data that's important, > look into running PostgreSQL (or any database really) on a unix box > with regular backups. If you must use windows use a single purpose > machine firewalled away from the rest of the universe with only a > pgsql port (5432) showing and no logins for anyone but the DBA to the > machine. > > --------------000301080307060507020708 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Scott Marlowe wrote:
On 8/20/07, luis perruca <l.perruca@gmail.com> wrote:
  
Hi All: I'm From Spain and I'll try to write in english as best as possible:
    

Your english > my spanish, so please don't worry.

  
I'm new in the list, and I have a serious problem: I am novice with
Postgresql and I haven't found any solution.
I Wil descrive the scenario:

I have Postgresql 8.0.1 running on Windows 2003 Server.
I have a Backup of my database, but is a little old
    

A pg_dump type backup, or a file system backup?

  
A file System backup

  
And here is my problem:

First, the Postgresql service didn't started (really started, but shut down
immediatly)
    

What steps led to this happening.  They might be important.

Did you install new /update software on this server?  Especially
anti-virus software?  That stuff's nearly as dangerous as a virus
itself for a database.

What are the exact error messages you got when this happened.

  
I don't remember exactly the error, but says something like "the service started and then shut down. (some services shut down when have nothing to do)". This really says nothing.

  
then I copied all the "postgresql" folder in other place, uninstalled and
reinstalled Postgresql, and then overwrite the "data" folder with the one
from the copy that I did.
    

Did you shut down postgresql while you were copying those files back?
  
Yes, postgresql was down when restoring the folder.
  
Now, the service starts properly, but the database doesn´t work. I did
"pg_resetxlog" (I don´t know what it does, but I saw it somewhere).
    

It reselts the transaction log pointer.  It has likely set back in
time to when there was nothing in the database.  Just guessing.

  
From pgAdmin III, I see the database, I access it, I see the tables and
their properties, but no data.  I get the error  "xlog flush request
6D/432AAAA8 is not satisfied --- flushed only to 0/C03D020  CONTEXT: writing
block 925 of relation 16631/17254/18128" when I try to view the tables
    

Have you still got that old pg directory?  Try shutting down pgsql,
copying the data part back in place, and restarting pgsql and see if
it starts up right or not.
  
The service starts, but with the errors that I have told: I see the tables but I get error or no data.
  
I would need to know if I can recover the data from the tables and how to do
it.
    

Can't tell from what you've told us so far.  Need more info of how you
got into this state and exact error messages you're getting as well.

My one piece of advice would be that if you data that's important,
look into running PostgreSQL (or any database really) on a unix box
with regular backups.  If you must use windows use a single purpose
machine firewalled away from the rest of the universe with only a
pgsql port (5432) showing and no logins for anyone but the DBA to the
machine.

  

--------------000301080307060507020708--