From: | joka veera Venkataramana <ramanajvv(at)gmail(dot)com> |
---|---|
To: | AJ Weber <aweber(at)comcast(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Backup of database |
Date: | 2013-11-26 20:58:28 |
Message-ID: | CANGhxCjHNF8+3S-f6nwJ-6S7_Q-sOwDOTpE6Prgehojbh2o1eg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thank You All...It Worked
On Tue, Nov 26, 2013 at 1:32 PM, AJ Weber <aweber(at)comcast(dot)net> wrote:
>
> On 11/26/2013 11:56 AM, Scott Ribe wrote:
>
>> On Nov 26, 2013, at 9:28 AM, joka veera Venkataramana<ramanajvv(at)gmail(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marcello Lorenzi | 2013-11-27 15:57:45 | Postgres 9.2 pg_xlog cleanup |
Previous Message | AJ Weber | 2013-11-26 18:32:55 | Re: Backup of database |