On 2008-04-23 17:22, Terry Lee Tucker wrote:
> On Wednesday 23 April 2008 11:14, Gabor Siklos wrote:
>> The advantage of the first method would be that I would not have to wait
>> for pg_dump (it takes quite long on our 60G+ database) and would just be
>> able to configure the backup agent to monit
On Wednesday 23 April 2008, "Gabor Siklos" <[EMAIL PROTECTED]> wrote:
> I need to back up our database off-site for disaster recovery. If I just
> back up the entire database data directory (i.e. /var/lib/pgsql/data)
> will I be able to restore from there?
Technically you can do this, if you do it
For a database that big, you might consider using the WAL archiving
strategy and shipping the WAL files offsite:
http://www.postgresql.org/docs/8.3/interactive/continuous-
archiving.html
On Apr 23, 2008, at 8:14 AM, Gabor Siklos wrote:
I need to back up our database off-site for disaster r
"Gabor Siklos" <[EMAIL PROTECTED]> writes:
> I need to back up our database off-site for disaster recovery. If I just
> back up the entire database data directory (i.e. /var/lib/pgsql/data) will I
> be able to restore from there?
This will not work. Please read
http://www.postgresql.org/docs/8.3/
On Wednesday 23 April 2008 11:14, Gabor Siklos wrote:
> I need to back up our database off-site for disaster recovery. If I just
> back up the entire database data directory (i.e. /var/lib/pgsql/data) will
> I be able to restore from there? Or should I instead just dump the data,
> using pg_dump, a
I need to back up our database off-site for disaster recovery. If I just
back up the entire database data directory (i.e. /var/lib/pgsql/data) will I
be able to restore from there? Or should I instead just dump the data, using
pg_dump, and back up the dump?
The advantage of the first method would b
