PostgreSQL Point In Time Recovery (PITR)

-
need: one last basebackup and also enable archive before basebackup

how to setup basebackup

step1: edit pg_hba.conf and postgresql.conf file

goto data directory

vi pg_hba.conf

 # TYPE  DATABASE        USER            ADDRESS                 METHOD
# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             192.168.1.221/32        trust
host    all             all             127.0.0.1/32            ident
# IPv6 local connections:
host    all             all             ::1/128                 ident
# Allow replication connections from localhost, by a user with the
# replication privilege.
local   replication     all                                     peer
host    replication     all             192.168.1.222/32        trust

 vi postgresql.conf

    listern_address=*
   archive_mode=on
   archive_command='cp %p /arch/%f'
   wal_level=replica
   full_page_writes=on
   max_wal_sender=6
   wal_keep_segement=500
   max_replication_slot=2
   log_statement='all'

STEP3: restart the server

  su - postgres
  cd /usr/pgsql-11/bin
  ./pg_ctl -D /var/lib/pgsql/11/data restart

step4: run pg_basebackup utility tool

  without tablespace:
 
  ./pg_basebackup -h 192.168.1.21 -p 5432 -P -v -X stream or fetch  -c fast -R -Fp -D /backup/bk_1
 
  with tablespace
 
  ./pg_basebackup -h 192.168.1.221 -p 5432 -P -v -c fast -X stream -R -T /tbs_1=/tbs_new1 -T /tbs_2=/tbs_new2mn  -Fp -D /backup/bk_`date +%d%m%y%H%M%S`
 
  -P progres
  -v verbose
  -c checkpoint
  -X wals
  -R create recovery.conf file
  -T tablespace
      -T curent_tablespace_directory=backup_tablespace_directory

step5: create some tables and drop tables

step6: take last basebackup and edit recovery.conf file,postgresql.conf file

 goto backup directory

  vi recovery.conf

   restore_command = 'cp /arch/%f %p'
   recovery_target_time = '2020-04-16 19:34:24.31'
   trigger_file = '/etc/error.conf'
 
  vi postgresql.conf

   port=3456 //change only same machine
   #archive_command='cp %p /arch/%f'  //disable archive_command
   hot_standby=on  //enable (remove # )

step7:start the backup server

 su - postgres
  cd /usr/pgsql-11/bin
  ./pg_ctl -D /backup/bk_1 start
  ./psql
  postgres=#select pg_is_in_recovery();  //check t=true f=false
  t 
step8:take particular table dump backup and restore main server

Comments

Post a Comment

Popular posts from this blog

PostgreSQL pg_pool-II Installation and Configuration

-
Image
Pgpool-II Pgpool-II is a proxy software that sits between PostgreSQL servers and a PostgreSQL database client.  It provides the following features: 1.Connection Pooling:     Pgpool-II maintains established connections to the PostgreSQL servers, and reuses them whenever a new connection with the same properties (i.e. user name, database, protocol version, and other connection parameters if any) comes in. It reduces the connection overhead, and improves system's overall throughput.   2.Load Balancing:     If a database is replicated (because running in either replication mode or master/slave mode), performing a SELECT query on any server will return the same result. Pgpool-II takes advantage of the replication feature in order to reduce the load on each PostgreSQL server.  It does that by distributing SELECT queries among available servers, improving the system's overall throughput. In an ideal scenario, read performance could improve proportion...
Read more

PostgreSQL Pages and Tuples

-
Image
INTERNAL LAYOUT: a tuple or an item is a synonym for a row a relation is a synonym for a table a filenode is an id which represent a reference to a table or an index. a block and page are equals and they represent a 8kb segment information the file storing the table. a heap refer to heap file . Heap files are lists of unordered records of variable size. Although sharing a similar name, heap files are different from heap data structure. CTID represent the physical location of the row version within its table. CTID is also a special column available for every tables but not visible unless specifically mentioned. It consists of a page number and the index of an item identifier. OID stands for Object Identifier. database cluster , we call a database cluster the storage area on disk. A database cluster is a collection of databases that is managed by a single instance of a running database server. Page:            Inside the data file (heap table and index,...
Read more

PostgreSQL Reporting Tools(Pgbadger) Installation & Configuration

-
PgBadger:                 The PostgreSQL log analyzer “pgBadger” is an open source “fast PostgreSQL log analysis report” program written in Perl that takes the log output from a running PostgreSQL instance and processes it into an HTML file.                  The report it generates shows all information found in a nice and easy to read report format.  These reports can help shed light on errors happening in the system, checkpoint behavior, vacuum behavior, trends, and other basic but crucial information for a PostgreSQL system. FEATURES:  pgBadger reports everything about your SQL queries:         Overall statistics.         The most frequent waiting queries.         Queries that waited the most.         Queries generating the most temporary files.         Queries generating the largest temporar...
Read more