EnterpriseDB BART Configuration

-

Setp:1. Bart tool use pg_basebackup utility tool so we can all basebackup configuration (postgresql.conf, pg_hba.conf) files.(you will try basebackup).

Setp:2.
Normal ssh for postgresql server and backup server

Step:3. Yum install edb-bart

Step:4. bart default path :
/usr/edb/bart/bin           -----àbart tool path
/usr/edb/bart/etc           -----à configuration Path

Step:5. Go to bart configcuration path and change bart.cfg.sample file rename to bart.cfg

Step:6. edit bart.cfg file

[BART]
bart_host= enterprisedb@192.168.1.202
backup_path = /opt/backups
pg_basebackup_path = /opt/edb/as10/bin/pg_basebackup
logfile = /usr/edb/bart/bart.log
scanner_logfile = /usr/edb/bart/bart_scanner.log
thread_count = 5

[siva]
host = 192.168.1.123
port = 5444
user = enterprisedb
xlog_method = stream
#wal_compression = enabled
archive_command = 'cp %p %a/%f'
cluster_owner = <cluster_owner>
description = "PPAS 96 Server"
allow_incremental_backups = enabled

you will change all folders and files in enterprisedb user

USE Backup And Recovery Tool

Step:7. Make backup
-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg BACKUP -Ft -s siva

Step:8. Show-Backups

-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg SHOW-BACKUPS  -s siva

Step:9. Show-Servers
-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg SHOW-SERVERS

Laste level you maintain this level:

Step:10. Manage
-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg MANAGE -s siva

Step:11. Check-Config
-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg CHECK-CONFIG

Step:12. Restore
./bart RESTORE -s siva -i 1551333978616 -p /zzz -w 5

Step:13. Point in Time Recovery
-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg RESTORE -s s1 -i 1551337259279 -p /yyy -g '28-FEB-19 12:35:54'
Step:14. INCREMENTAL BACKUP:
                First you run bart-scanner file in bart bin path
-bash-4.1$ ./bart-scanner -c /usr/edb/bart/etc/bart.cfg --daemon
And you type incremental backup command
-bash-4.1$ ./bart -c /usr/edb/bart/etc/bart.cfg BACKUP -Fp -s siva --parent 1551333978616

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