Skip to main content

Backup PostGRE Database and 'rsync' to Another Server with Password-less Entry


We had a requirement that we need to create a backup of postGre Database,
And rsync it to Another server. Here is How we did it.

BACK UP DATABASE
Here is the script to take backup of PostgreSQL Database.

BACKUP_DIR_PATH="/backup/myDB/Here"
PGUSER_DB="username"
export PGPASSWORD="password"
time=`date '+%d'-'%m'-'%H':'%M':'%S' `
/usr/pgsql-9.0/bin/pg_dump --host localhost --port 5432 --username $PGUSER_DB --format custom --blobs --verbose --file "$BACKUP_DIR_PATH/backup-databaseName-$time.backup" "database_name_here"


'rsync' DATA TO ANOTHER SERVER
Here is the script to sync backed-up data to another Server

DIR_LOCAL="/backup/myDB/Here"
DIR_REMOTE="/home/user/db_backup_from_dev"
REMOTE_USER="username"
REMOTE_SERVER="192.168.0.8"
rsync -avzh -e ssh $DIR_LOCAL  $REMOTE_USER@$REMOTE_SERVER:$DIR_REMOTE

To Complete rsync we need to create a secure channel (PASSWORDLESS Entry) to the Destination Server.

creating a secure channel PASSWORD-LESS Entry to the Destination Server.
Sync between two hosts source_machine and destination_machine.

On source_machine.
$ ssh-keygen -t rsa

This will prompt for a passphrase. Just press the enter key. 
It'll then generate an identification (private key) and a public key. 
Do not ever share the private key with anyone! 
ssh-keygen shows where it saved the public key. 
This is by default ~/.ssh/id_rsa.pub:
Your public key has been saved in /.ssh/id_rsa.pub

Transfer the id_rsa.pub file to destination_machine.

On destination_machine.
Login as the remote user which you plan to use when you run rsync on source_machine.
Copy the contents of id_rsa.pub to ~/.ssh/authorized_keys

$ cat id_rsa.pub >> ~/.ssh/authorized_keys
$ chmod 700 ~/.ssh/authorized_keys

If this file does not exists, then the above command will create it. 
Make sure you remove permission for others to read this file.
 
If its a public key, why prevent others from reading this file? Probably, the owner of the key has distributed it to a few trusted users and has not placed any additional security measures to check if its really a trusted user.
Note that ssh by default does not allow root to log in.
Labels:

Comments

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n
2 comments
Read more

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa
Post a Comment
Read more