Hi again

I have tried to check different /var/log/messages on the servers but they only 
go back 1 month. I also had quick glance at  Nagios and Munin logs but I could 
not find anything there.

This database is mainly used for reading data as it is now, but it's a couple 
of applications which also store data. The 2 days with out activity in the 
archive logs is strange when I checked back on the activity reports for 
applications. I will set the archive_timeout, but the problem  is that we have 
small updates and the archive files has the same size and is not depending on 
the amount of changed data.

We use NFS to copy archive  files to the backup server because that is simple, 
but maybe we should have used rsyn or something else, but independent off how 
we do it, we need a method to check that the archive file is OK after it's 
copy. 

If it's not OK the files must be transfers once more from the database server. 
I assume the archive always will be OK when it's created on the database server.

Is the the way off doing this to make a script that copies the archive file to 
backup server cheeks that the files are equal before before it is deleted on 
the database server ?

Is there any simple utility program that can check if the archive file is OK or 
do I have to do a restore to check if the file is OK  ?

Thanks Lars
________________________________________
Fra: Magnus Hagander [mag...@hagander.net]
Sendt: 7. januar 2013 21:47
Til: Lars Aksel Opsahl
Kopi: pgsql-admin@postgresql.org
Emne: Re: [ADMIN] Postgres base Backup fails to recover all logs fails from 
archive

On Sat, Jan 5, 2013 at 11:30 PM, Lars Aksel Opsahl
<l...@skogoglandskap.no> wrote:
> Hi
>
> Thanks for your help.
>
> The problem is that it stops to restore the log files after reading log file 
> 0000000100000023000000F7.
>
> The recovery does not continue to read log file 0000000100000023000000F8 and 
> the rest of the log files.
>
> I don't under stand why it stops to read the rest of the log files.

Ah, I see that now.

Well, it's claiming that the F7 logfile is corrupt.

There's also an interesting jump in timestamps - the F7 logfile is
from *much* later than F6. Almost two whole days. Is that actually
normal, or did something possibly go wrong with your archiving?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Reply via email to