Message-ID: <5294E957.1000802@comcast.net>
Date: Tue, 26 Nov 2013 13:32:55 -0500
From: AJ Weber <aweber@comcast.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: Re: Backup of database
References: 
 <CANGhxCgYrQbvegp1MbjbQ0SLpoVOC1TSqZYBObgE9pO4_N+Dbw@mail.gmail.com>
 <B00D83F7-38D0-4643-BE17-C8F8AB1DDB10@elevated-dev.com>
In-Reply-To: <B00D83F7-38D0-4643-BE17-C8F8AB1DDB10@elevated-dev.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


On 11/26/2013 11:56 AM, Scott Ribe wrote:
> On Nov 26, 2013, at 9:28 AM, joka veera Venkataramana<ramanajvv@gmail.com>  wrote:
>
>> I know all my questions are basic, why we are asking here is  previously we were in DB2 now we moved our database to Postgre (Its new for us). Please help us.
> <http://www.postgresql.org/docs/9.3/interactive/backup.html>
>
> Personally, for daily backups, I like pg_dumpall | bzip2.
If you're using some kind of rsync or rsnapshot to help with backups, 
check-out "gzip --rsyncable".  It purports to keep the compressed 
archive in a better format for rsync-type (changed-block-only) 
transfers, at the expense of not using the most advanced algorithm.

I have a script that dumps my db to a local gz file, and alternates 
naming it with a .0 or .1 so I always have the last two backups (and 
then those backup/archive files are rsync'ed to another machine).

-AJ


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin