pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: Robert Treat <xzilla@users.sourceforge.net>
To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
Subject: Re: Hot Backup
Date: Tue, 08 Oct 2002 19:21:55 +0530
Message-ID: <3DA33053.10064.158E04DA@localhost> (raw)
In-Reply-To: <1034084444.6801.12.camel@camel>
References: <3DA323B1.3732.155CAB4F@localhost>

On 8 Oct 2002 at 9:40, Robert Treat wrote:
> Is it me or do doomsdays scenarios sometimes seem a little silly? I'd
> like to ask just where are you storing your "incremental backups" with
> Oracle/m$ sql ?? If it's on the same drive, then when you drive craps
> out you've lost the incremental backups as well.  Are you putting them
> on a different drive (you can do that with the WAL) you'd still have the
> problem that if the building went up in smoke you'd lose that
> incremental backup. Unless you are doing "incremental backups" to a
> computer in another physical location, you still fail all of your
> scenarios.

Well, all I can say is having a sync'ed and replicated database ssytem is good. 
Either from load sharing point of view or from fail over point.

Forget backup. If you are upto restoring from backup, doesn't matter most of 
the times whether you are restoring from dump or cycling thr. thousands of WAL 
files..

> This type of scenario sounds as good as the above mentioned methods for
> oracle/m$ server. Could you post your pdf? Seems like it might be worth
> adding to the techdocs site.

Well, I found it googling around. Se if this helps...I have posted this before 
dunno which list. This crosposting habit of PG lists made me to lose tracks of 
where things originated and where they ended.. Not that it's bad..

HTH
Bye
 Shridhar

--
like:	When being alive at the same time is a wonderful coincidence.

Attachments:

  johnson_darren.zip (application/zip, 37.3K) download

view thread (18+ messages)  latest in thread

Message-ID: <3DA33053.10064.158E04DA@localhost>
Permalink:  ../3DA33053.10064.158E04DA@localhost/
Also on:    postgresql.org/message-id/3DA33053.10064.158E04DA@localhost

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: shridhar_daithankar@persistent.co.in, xzilla@users.sourceforge.net, pgsql-general@postgresql.org
  Subject: Re: Hot Backup
  In-Reply-To: <3DA33053.10064.158E04DA@localhost>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox