/home/postgresql_backup$ pg_basebackup -D postgresql_backup -Ft -z -P

1279 postgres   20   0 1918M 18916 17404 S  0.0  0.0  0:20.92 postgres: startup process   waiting for 0000000600000C050000005F

/postgresql/9.1/main# /etc/init.d/postgresql start
 * Starting PostgreSQL 9.1 database server                                    [ OK ]

Host key verification failed.
Host key verification failed.
2013-11-13 10:46:42 MSK LOG:  streaming replication successfully connected to primary
2013-11-13 10:46:42 MSK FATAL:  could not receive data from WAL stream: FATAL:  requested WAL segment 0000000600000C1500000044 has already been removed

# - Standby Servers -

# These settings are ignored on a master server

#hot_standby = off<----><------><------># "on" allows queries during recovery
<------><------><------><------><------># (change requires restart)
#max_standby_archive_delay = 30s<------># max delay before canceling queries
<------><------><------><------><------># when reading WAL from archive;
<------><------><------><------><------># -1 allows indefinite delay
#max_standby_streaming_delay = 30s<----># max delay before canceling queries
<------><------><------><------><------># when reading streaming WAL;
<------><------><------><------><------># -1 allows indefinite delay
#wal_receiver_status_interval = 10s<---># send replies at least this often
<------><------><------><------><------># 0 disables
#hot_standby_feedback = off<---><------># send info from standby to prevent
<------><------><------><------><------># query conflicts


# - Settings -

#wal_level = minimal<--><------><------># minimal, archive, or hot_standby
<------><------><------><------><------># (change requires restart)
#fsync = on<---><------><------><------># turns forced synchronization on or off
#synchronous_commit = on<------><------># synchronization level; on, off, or local
#wal_sync_method = fsync<------><------># the default is the first option
<------><------><------><------><------># supported by the operating system:

wal_level = minimal
hot_standby = off
hot_standby_feedback = off

2013-11-13 11:14:32 MSK LOG:  received fast shutdown request
2013-11-13 11:14:32 MSK LOG:  shutting down
2013-11-13 11:14:32 MSK LOG:  database system is shut down
2013-11-13 11:14:36 MSK LOG:  database system was shut down in recovery at 2013-11-13 11:14:32 MSK
Host key verification failed.
2013-11-13 11:14:36 MSK LOG:  starting archive recovery
Host key verification failed.
2013-11-13 11:14:36 MSK LOG:  redo starts at C15/43C346A8
Host key verification failed.
2013-11-13 11:14:36 MSK LOG:  consistent recovery state reached at C15/442ACD20
2013-11-13 11:14:36 MSK LOG:  invalid record length at C15/442ACD20
2013-11-13 11:14:36 MSK LOG:  redo done at C15/442ACCE0
2013-11-13 11:14:36 MSK LOG:  last completed transaction was at log time 2013-11-12 02:07:13.004621+04
2013-11-13 11:14:36 MSK LOG:  incomplete startup packet
Host key verification failed.
2013-11-13 11:14:36 MSK LOG:  selected new timeline ID: 7
Host key verification failed.
2013-11-13 11:14:36 MSK LOG:  archive recovery complete
2013-11-13 11:14:37 MSK LOG:  autovacuum launcher started
2013-11-13 11:14:37 MSK LOG:  database system is ready to accept connections

/etc/postgresql/9.1/main$ /usr/bin/pg_basebackup  -D /home/local_backup -Ft -z -P
pg_basebackup: could not connect to server: FATAL:  
no pg_hba.conf entry for replication connection from host "[local]", user "postgres", SSL off

local all all  127.0.0.1/32 trust

local all trust

#local   replication     postgres                                trust
#host    replication     postgres        127.0.0.1/32            trust
#host    replication     postgres        ::1/128                 trust

local all all trust
host all all 127.0.0.1/32 trust

listen_addresses = 'localhost'

host     replication     postgres        192.168.1.203           trust

$ /usr/bin/pg_basebackup  -h 192.168.1.17 -D /home/base_backup/

pg_basebackup: could not connect to server: could not connect to server: Connection refused
        Is the server running on host "192.168.1.17" and accepting
        TCP/IP connections on port 5432?

# create user replica with replication password 'secret'; 

create user replica with replication password 'secret';
No command 'create' found, did you mean:
 Command 'mcreate' from package 'lustre-utils' (universe)
create: command not found

psql
psql (9.1.9)
Type "help" for help.

postgres=# create user replica with replication password 'replica';
ERROR:  cannot execute CREATE ROLE in a read-only transaction

host     replication     postgres        192.168.1.203           trust

host     replication     postgres        192.168.1.203/32           trust

 /usr/bin/pg_basebackup -U base_backup_user -h 192.168.1.11 -c fast -D /home/base_backup/

Chained replication is supported on PostgreSQL 9.2.

9.1 does not support chained replication. You will need to either take the base backup from the master, or:

Stop the replica
Copy the replica manually
Start the replica back up

 pg_basebackup -D /home/base_backup -U replica -h 127.0.0.1 -P

WARNING:  skipping special file "./server.key"
WARNING:  skipping special file "./server.crt"
WARNING:  skipping special file "./server.key"
WARNING:  skipping special file "./server.crt"
1369558/1369558 kB (100%), 1/1 tablespace
NOTICE:  pg_stop_backup cleanup done, waiting for required WAL segments to be archived
WARNING:  pg_stop_backup still waiting for all required WAL segments to be archived (60 seconds elapsed)
HINT:  Check that your archive_command is executing properly.
  pg_stop_backup can be canceled safely, but the database backup will not be usable without all the WAL segments.
WARNING:  pg_stop_backup still waiting for all required WAL segments to be archived (120 seconds elapsed)
HINT:  Check that your archive_command is executing properly.
  pg_stop_backup can be canceled safely, but the database

 pwd
/var/lib/postgresql/9.1/main/archive

archive_command = '/var/lib/postgresql/9.1/main/archive'