Re: Automatic restore corruption problem

Perhaps you did not start up the new database in restore mode pointing
to the WAL logs that were generated during your rsync operation that
were not captured.

Regards,
Michael

> Matthieu Lejeune <mailto:matthieu(dot)lejeune(at)exxoss(dot)com>
> Friday, July 10, 2015 8:59 AM
> Hi all,
>
> I have a script for restoring a database every night to an other
> postgresql database
>
> root(at)p2prddnmdbc:~# cat /var/admin/script/restoredb.sh
> #/bin/bash
> /etc/init.d/postgresql stop
> mv /var/log/postgresql/postgresql-9.3-main.log
> /var/log/postgresql/postgresql-9.3-main.log.old
> cd /var/lib/postgresql/9.3/main
> psql --host=p2prddnmdbm --username=replicator postgres -c "SELECT
> pg_start_backup('sync');"
> rsync -av --delete root(at)10(dot)10(dot)11(dot)1:/var/lib/postgresql/9.3/main/*
> /var/lib/postgresql/9.3/main/
> rm backup_label
> chown -R postgres:postgres *
> psql --host=p2prddnmdbm --username=replicator postgres -c "SELECT
> pg_stop_backup();"
> /etc/init.d/postgresql start
> chmod 777 /var/log/postgresql/postgresql-9.3-main.log
> psql -U postgres -c "ALTER USER xxxx WITH PASSWORD 'XXXX';"
> psql -U postgres xxxx -c "CREATE EXTENSION dblink;"
> root(at)p2prddnmdbc:~#
>
>
> But during the day when the user are using the new database we got
> error like this :
>
> 2015-06-25 16:20:58 CEST ERROR: could not read block 257985 in file
> "base/16386/14064061.1": read only 0 of 8192 bytes
> 2015-06-22 15:21:11 CEST ERROR: could not read block 256801 in file
> "base/16386/14064061.1": read only 0 of 8192 bytes
>
> I have check the : filesystem on the vm, on the HW SAN,...
>
> Any idea to fix this problem?
>
> Thanks
>
> Matthieu
>
>