pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shoaib Mir <shoaibmir@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: problem backup/restore PSQL DB
Date: Tue, 25 Jul 2006 22:35:35 +0500
Message-ID: <bf54be870607251035t2845de04n6fcd3d46fdcffdbc@mail.gmail.com> (raw)
In-Reply-To: <75c69f690607250937m7c5c2f59o631d3b3f919f3f13@mail.gmail.com>
References: <75c69f690607241726r1a640b2excab3439485cdff63@mail.gmail.com>
	<5478199.post@talk.nabble.com>
	<bf54be870607250145w18af0d2ay8be879e123287d69@mail.gmail.com>
	<75c69f690607250937m7c5c2f59o631d3b3f919f3f13@mail.gmail.com>

Yes, that is possible to take the backup from one instance and restore that
in another postgresql instance and for that purpose you use pg_dump (for
taking full dump use pg_dumpall) and pg_restore utilities.

Thanks,

Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 7/25/06, JieJun Xu <jiejun83@gmail.com> wrote:
>
> Thanks for helping. My postgresql DB is actually part of the OME system
> which stores Image Metadata. The system overview is as following:
> http://www.openmicroscopy.org/system-overview/.
>
> So I am actually using the option provided by OME to backup/restore my
> system.
> http://www.openmicroscopy.org/system-admin/backup_restore.html
>
> Part of the backup code in perl is as following:
>
>     print "    \\_ Backing up postgress database ome\n";
>     my $dbConf = $environment->DB_conf();
>     my $dbName = 'ome';
>     $dbName = $dbConf->{Name} if $dbConf->{Name};
>
>     my $flags = '';
>     $flags .= '-h '.$dbConf->{Host}.' ' if $dbConf->{Host};
>     $flags .= '-p '.$dbConf->{Port}.' ' if $dbConf->{Port};
>     $flags .= '-U '.$dbConf->{User}.' ' if $dbConf->{User};
>     $flags .= '-Fc'; # -F (format).
>                      # -p: use the plain text SQL script file this should
> be the most portable
>                      # -c: custom archive suitable for input into
> pg_restore
>     print STDERR "su $postgress_user -c '".$prog_path{'pg_dump'}." $flags
> -o $dbName > /tmp/omeDB_backup'\n";
>
>     # backup database and watch output from pg_dump
>     foreach (`su $postgress_user -c '$prog_path{'pg_dump'} $flags -o
> $dbName > /tmp/omeDB_backup' 2>&1`) {
>         print STDERR "\nDatabase Backup Failed: $_" and die if $_ =~
> /pg_dump/ or $_ =~ /ERROR/ or $_ =~ /FATAL/;
>     }
>     # check the size of omeDB_backup
>     if (stat("/tmp/omeDB_backup")->size < 1024) {
>         print STDERR "\nDatabase Backup Failed: /tmp/omeDB_backup is less
> than 1024 bytes in size \n";
>         die;
>     }
>     # log version of backup
>     open (FILEOUT, "> /tmp/OMEmaint") or die "Couldn't open OMEmaint for
> writing\n";
>     print FILEOUT "version=$dbAdmin_version\n";
>     close (FILEOUT);
>
> I will try modify the 'pg_dump' to 'pg_dumpall' and see if it works..
> But is it even possible to backup one system and restore it in another?  I
> just don't want to go into a deadend. Many thanks!!
>
> Jun
>
>
>
>
> On 7/25/06, Shoaib Mir <shoaibmir@gmail.com> wrote:
> >
> > You can also try using 'pg_dumpall' (http://www.postgresql.org/docs/8.1/static/app-pg-dumpall.html)
> > that will take the dump of all the users, groups and databases.
> >
> > Thanks,
> >
> > Shoaib Mir
> > EnterpriseDB
> >
> >
> > On 7/25/06, Paul S <plabrh1@gmail.com> wrote:
> > >
> > >
> > > It looks like it's a user configuration issue.  I have hit user setup
> > > issues
> > > while restoring DB's before and generally I find it useful to create
> > > the
> > > Users and/or Groups manually on the new server first before restoring
> > > the
> > > DB's whenever I hit problems like that.  Try syncing the users
> > > manually,
> > > (assuming that there are only a few and that it could be done manually
> > > with
> > > some level of ease) and then try restoring again.
> > >
> > > -Paul
> > > --
> > > View this message in context:
> > > http://www.nabble.com/problem-backup-restore-PSQL-DB-tf1995768.html#a5478199
> > > Sent from the PostgreSQL - admin forum at Nabble.com.
> > >
> > >
> > > ---------------------------(end of
> > > broadcast)---------------------------
> > > TIP 1: if posting/reading through Usenet, please send an appropriate
> > >        subscribe-nomail command to majordomo@postgresql.org so that
> > > your
> > >        message can get through to the mailing list cleanly
> > >
> >
> >
>

view thread (5+ messages)

Message-ID: <bf54be870607251035t2845de04n6fcd3d46fdcffdbc@mail.gmail.com>
Permalink:  ../bf54be870607251035t2845de04n6fcd3d46fdcffdbc@mail.gmail.com/
Also on:    postgresql.org/message-id/bf54be870607251035t2845de04n6fcd3d46fdcffdbc@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: shoaibmir@gmail.com
  Subject: Re: problem backup/restore PSQL DB
  In-Reply-To: <bf54be870607251035t2845de04n6fcd3d46fdcffdbc@mail.gmail.com>
  References: <75c69f690607241726r1a640b2excab3439485cdff63@mail.gmail.com> <5478199.post@talk.nabble.com> <bf54be870607250145w18af0d2ay8be879e123287d69@mail.gmail.com> <75c69f690607250937m7c5c2f59o631d3b3f919f3f13@mail.gmail.com> <bf54be870607251035t2845de04n6fcd3d46fdcffdbc@mail.gmail.com>

* 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