From: Gerardo Herzig <gherzig@fmed.uba.ar>
To: Jyoti Seth <jyotiseth2001@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: backup and restore
Date: Fri, 08 May 2009 08:44:15 -0300
Message-ID: <4A041B0F.2020103@fmed.uba.ar> (raw)
In-Reply-To: <004201c9cfbf$b6becab0$243c6010$@com>
References: <4A03C276.9050007@postnewspapers.com.au>
<004201c9cfbf$b6becab0$243c6010$@com>
Jyoti Seth wrote:
> Hello,
>
> I have two databases db1 and db2 with the same database structure on
> different systems with no network connection. In the first system with the
> db1 database user updates the master data. At the end of every day, the user
> needs to take the backup of updated data of master tables on db1 and update
> the data on another system with db2 database.
>
> We can't use WAL as in this as we want to take incremental backup of few
> tables only and can't use slony as there is no network connection between
> the systems.
>
> Please suggest some solution.
>
> Thanks,
> Jyoti
>
>
I guess you are triyng to avoid the 'pg_dump - save_to_floppy -
walk_to_db2_place - pg_restore' pattern. Well, can you save `pg_dump' in
some middle place? One place which machine1 and machine2 have access to?
If so, you can kind of automate the job using two programs, one (in the
master) who 'upload' (via ftp maybe, scp or whatever) in this middle
place, ando other in the slave who 'download' and process the file using
pg_restore.
HTH
Gerardo
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-sql@postgresql.org
Cc: gherzig@fmed.uba.ar, jyotiseth2001@gmail.com
Subject: Re: backup and restore
In-Reply-To: <4A041B0F.2020103@fmed.uba.ar>
* 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