Database backup mechanism - Mailing list pgsql-hackers

From RaviKumar.Mandala@versata.com
Subject Database backup mechanism
Date
Msg-id OFED7CC96C.6C7BD5CC-ON8625727D.0026DFB1-6525727D.0027B5D6@trilogy.com
Whole thread Raw
Responses Re: Database backup mechanism  (Heikki Linnakangas <heikki@enterprisedb.com>)
Re: Database backup mechanism  (Doug Knight <dknight@wsi.com>)
Re: Database backup mechanism  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
<br /><font face="sans-serif" size="2">Hi Folks,</font><br /><br /><font face="sans-serif" size="2">We have a
requirementto deal with large databases of the size Terabytes when we go into production. What is the best database
back-upmechanism and possible issues?</font><br /><br /><font face="sans-serif" size="2">pg_dump can back-up database
butthe dump file is limited by OS file-size limit. What about the option of compressing the dump file? How much time
doesit generally take for large databases? I heard, that it would be way too long (even one or days). I haven't tried
itout, though.</font><br /><br /><font face="sans-serif" size="2">What about taking zipped back-up of the database
directory?We tried this out but the checkpoint data in pg_xlogs directory is also being backed-up. Since these logs
keepson increasing from day1 of database creation, the back_up size if increasing drastically.</font><br /><font
face="sans-serif"size="2">Can we back-up certain subdirectories without loss of information or consistency..?</font><br
/><br/><font face="sans-serif" size="2">Any quick comments/suggestions in this regard would be very helpful.</font><br
/><br/><font face="sans-serif" size="2">Thanks in advance,</font><br /><font face="sans-serif" size="2">Ravi Kumar
Mandala</font>

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Variable length varlena headers redux
Next
From: Kris Jurka
Date:
Subject: Re: Proposal: Commit timestamp