Vinod V wrote:
> We need to implement incremental backup (PITR) in our environment, since our production database is in
> high risk.
>
> We are running with PostgreSQL 9.1
>
> We need to implement this on both Windows7 and Linux platforms.
You are not trying to restore WAL files from Windows on Linux
or vice versa, are you? Because that wouldn't work.
> We were able to get the WAL files generated on Windows platform but the recovery from the log files
> are not happening. Below were the error messages that we were getting when trying to restore it (while
> restarting the server).
>
>
>
> 2013-01-10 01:58:46 PST LOG: could not bind IPv6 socket: No error
> 2013-01-10 01:58:46 PST HINT: Is another postmaster already running on port 5432? If not, wait a few
> seconds and retry.
Is there something else blocking port 5432?
> 2013-01-10 01:58:46 PST LOG: could not bind IPv4 socket: No error
> 2013-01-10 01:58:46 PST HINT: Is another postmaster already running on port 5432? If not, wait a few
> seconds and retry.
> 2013-01-10 01:58:46 PST WARNING: could not create listen socket for "*"
> 2013-01-10 01:58:46 PST FATAL: could not create any TCP/IP sockets
>
> The system cannot find the file specified.
[...]
> Below are the archive_command and restore_command,which I am using (on Windows7).
>
> wal_level = archive
> archive_mode = on
> archive_command = 'copy "%p" "C:\\Program Files\\PostgreSQL\\9.1\\data\\wals\\%f"'
>
> restore_command=’copy ‘C:\\Program Files\\PostgreSQL\\9.1\\data\\wals\\%f %p’
What are these non-ASCII characters doing in restore_command?
That doesn't look right to me.
Use double quotes like in archive_command.
Yours,
Laurenz Albe