[postgis-users] Problems with backing up and restoringTiger Geocoder database

[Paragon Corporation]

Another tip. for restore you want to use
the --jobs option

e.g. 

--jobs=3

to have 3 parallel loads happening.

(forgot that in our cheatsheet)

It will do restore of several tables at once thus running faster if you have
the processors to support.

Another reason to not bother with sql backups since you can't take advantage
of parallel restore with sql backups.



> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net 
> [mailto:postgis-users-bounces at postgis.refractions.net] On 
> Behalf Of Paragon Corporation
> Sent: Wednesday, November 09, 2011 5:07 PM
> To: 'PostGIS Users Discussion'
> Subject: Re: [postgis-users] Problems with backing up and 
> restoringTiger Geocoder database
> 
> Rene,
> 
> My guess is you probably did an SQL backup instead of a 
> compressed or tar backup.
> 
> I've had this issue before when backing up with pgAdmin and 
> the reason is because it defaults to sql backup I think.  I 
> forget what the switch is you can check our backup /restore 
> cheatsheet for reference.
> 
> http://www.postgresonline.com/downloads/special_feature/postgr
> esql90_pg_dump
> restore_cheatsheet.pdf
> 
> (you want -F c -b
> 
> pg_restore can only be used to restore tar or compressed backups.
> 
> We restore the tiger data all the time to various servers so 
> no issue there.
> 
> 
> Leo and Regina
> http://www.postgis.us
> 
> 
> 
> > -----Original Message-----
> > From: postgis-users-bounces at postgis.refractions.net
> > [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of 
> > René Fournier
> > Sent: Wednesday, November 09, 2011 2:10 PM
> > To: PostGIS Users Discussion
> > Subject: [postgis-users] Problems with backing up and 
> restoring Tiger 
> > Geocoder database
> > 
> > Since building the Tiger Geocoder database from the source 
> data is so 
> > time-consuming, I'm trying to capture the result (the ~90GB 
> spatially 
> > aware database) so that I can simply restore, in case I need to 
> > rebuild the server. Should be simple, but every time I pg_dump and 
> > attempt to pg_restore, I get
> > 
> > 	pg_restore: [archiver] input file does not appear to be a valid 
> > archive
> > 
> > So, just wondering what I'm doing wrong? Or, put another 
> way, what are 
> > the steps to dump the given database and restore it to 
> another server 
> > running Postgresql90 and PostGIS 1.5.3? Thanks!
> > 
> > 
Rene
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> > 
> 
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>