ECLAIREURS

Configuring Hot physical backup for PITR with continuous archiving: The hot backup with continuous archiving help us to allow to recover the database point in time(PITR) from the time of database backup. Make sure to complete the basic requirement before starting the backup configuration, like where to store the base backup, WAL archives etc. So, My environment contains the following, pg01 --> PostgreSQL database server pg03 --> Backup server PGDATA --> Path to postgresql data directory /u01/backups/base --> for storing the database base backup /u01/backups/archive --> for storing WAL archives. BACKUP_NAME--> Backup file name Steps to configure the backup as follows, 1.) Create the backup and archive directories on backup server, if not already created. Here /u01/backups/base and /u01/backups/archive. 2.) Configure the passwordless ssh connectivity between database and backup server. 3.) Configure the database server, set the below parameters in postgr...

PostgreSQL physical database backup (Hot) on local or shared filesystem. Physical backup is copying of all the required database files to secondary location using OS command or any other available utility. Physical backup can be taken as hot or cold. The cold backup will be done while database or processes are completely stopped and the database files or directories will be copied to secondary or secure location. On the other hand, the Hot backup will be done while the database and processes are up and running, application will be connected and using the database. user or application sessions might be doing either DDL or DML operations. So lets get set go and configure the Hot backup for postgreSQL database on local file system. Environment details: I have two machines currently configured. pg01 -> postgreSQL database. pg03 -> Used in future for pushing the database backup to remote. Postgresql version -> 9.6.5 PGDATA = /u01/app/postgres/data (Database file loc...

I have wasted hour to figure out why i am getting issue while configuring the passwordless ssh connectivity between Linux7.2 nodes(pg01 and pg02) for PostgreSQL backup configuration with BARMAN. Even google didn't helped me much to figure out what went wrong in configuration. I am getting permission denied while transferring the authorized_keys file from pg01 server to pg03. I have gone through multiple blogs and tried almost all of the solutions but nothing worked for me. There will be multiple reason for the same issue. But in my case, this is something not working for me even all the permissions are correct for files and directories. [postgres@pg01 .ssh]$ scp authorized_keys pg03:/home/postgres/.ssh Permission denied (publickey,gssapi-keyex,gssapi-with-mic). lost connection Finally, I have enabled the SCP in debug mode to see more details as below. [postgres@pg01 .ssh]$ scp -v authorized_keys pg03:/home/postgres/.ssh Executing: program /usr/bin/ssh host pg03, user ...