restoring database on 2nd computer

[djfl]

Hi. I followed the FAQ and vacuum/analyzed, then backed up the database on my desktop. I followed the FAQ to restore the database on my laptop, and the pgAdmin III and the restore screen have been hung for around an hour now. The backup file was 792ish MBs. Is this delay normal?


Edit: While I'm typing this, the process completed. It still seems like a long time. I'm using postgre 8.3 that I downloaded from the HEM site if that helps.
Anyway, when I clicked OK to roger the restoration, a popup asked if I was sure if I wanted to "restore from this database again". I clicked no, so it brought me back to the restore database screen. I clicked OK again, and I again got the popup. I clicked OK this time, and it's now doing another restore. After this restore is completed, should I just hit the Cancel button?


FWIW, the last line of code after the restore was completed was:
WARNING: errors ignored on restore:1

After I clicked to rerestore, the code says:
Process returned exit code 1.

It then references the pg_restore.exe file path with something afterwards that I can't read...since restore is going on and the box isn't responding.



Anyway, apologies for the long post, but 'm hoping to have this fixed tonight as I'm leaving on vacation tomorrow morning.

Thanks in advance.

[fozzy71]

Hi. I followed the FAQ and vacuum/analyzed, then backed up the database on my desktop. I followed the FAQ to restore the database on my laptop, and the pgAdmin III and the restore screen have been hung for around an hour now. The backup file was 792ish MBs. Is this delay normal?

It depends on your machines performance, but yes.



....
Anyway, when I clicked OK to roger the restoration, a popup asked if I was sure if I wanted to "restore from this database again". I clicked no, so it brought me back to the restore database screen. I clicked OK again, and I again got the popup. I clicked OK this time, and it's now doing another restore. After this restore is completed, should I just hit the Cancel button?


Yes. Not sure what will happen from having run the restore again, but I would assume it is just doing the exact same thing. Probably nothing more than some wasted time for you.

This is from the backup/restore FAQ:


7) In the Filename field, click on the ellipsis button and go to the location where the backup file is located and click Open.

8) Leave all the default settings as is and click OK.

9) The restoring process might end with an error, just click cancel and do not click Ok to restore again.

The selected database is now restored.

[bpran]

I clicked cancel, then I opened HM, and nothing in the database ( 0 hand, 0 player)

What did I do wrong?

[fozzy71]

It would be next to impossible for me to say without having seen all the steps you did. The backup/restore process is not 100% reliable. That is why it is important to backup your archive folder and export your database to text files as well as a SQ: backup.

[bpran]

It would be next to impossible for me to say without having seen all the steps you did. The backup/restore process is not 100% reliable. That is why it is important to backup your archive folder and export your database to text files as well as a SQ: backup.


I did what the FAQ instructed me to do.
At the end, there was error message, I just clicked cancel (Faq number 9)

[netsrak]

What size is your Backup file? Which version of Postgresql?

[bpran]

What size is your Backup file? Which version of Postgresql?

backup size 520MB, Postgres 8.3

[netsrak]

And how long did the restore last? It should be some hours with this size.

[bpran]

And how long did the restore last? It should be some hours with this size.

the backup took around 20 - 30 minutes, and the restore took about the same time too.

[netsrak]

Thats to fast for the restore. I suggest you start again with the backup and please make sure you follow the FAQ exactly

[bpran]

Thats to fast for the restore. I suggest you start again with the backup and please make sure you follow the FAQ exactly

Start the restore only, or backup again too?

[netsrak]

I would suggest you start with the backup again

[bpran]

I would suggest you start with the backup again

This is the message after I finish the new backup.
What do you think?

D:\Program Files\PostgreSQL\8.3\bin\pg_dump.exe -h localhost -p 5432 -U postgres -F c -b -v -f "E:\HM backup Note 090703\PGbackupHM20090715.backup" "BP 2009"
pg_dump: reading schemas
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined text search parsers
pg_dump: reading user-defined text search templates
pg_dump: reading user-defined text search dictionaries
pg_dump: reading user-defined text search configurations
pg_dump: reading user-defined operator families
pg_dump: reading user-defined conversions
pg_dump: reading user-defined tables
pg_dump: reading table inheritance information
pg_dump: reading rewrite rules
pg_dump: reading type casts
pg_dump: finding inheritance relationships
pg_dump: reading column info for interesting tables
pg_dump: finding the columns and types of table "gametypes"
pg_dump: finding default expressions of table "gametypes"
pg_dump: finding the columns and types of table "selectedplayer"
pg_dump: finding the columns and types of table "actiontypes"
pg_dump: finding the columns and types of table "pokersites"
pg_dump: finding the columns and types of table "handhistories"
pg_dump: finding the columns and types of table "specialholecardactions"
pg_dump: finding the columns and types of table "importedfiles"
pg_dump: finding default expressions of table "importedfiles"
pg_dump: finding the columns and types of table "playerhandscashkeycolumns"
pg_dump: finding the columns and types of table "playerhandstourneykeycolumns"
pg_dump: finding the columns and types of table "allinsituations"
pg_dump: finding the columns and types of table "playerhandscashmisc"
pg_dump: finding the columns and types of table "playerhandstourneymisc"
pg_dump: finding the columns and types of table "playerhandsflop"
pg_dump: finding the columns and types of table "playerhandsturn"
pg_dump: finding the columns and types of table "playerhandsriver"
pg_dump: finding the columns and types of table "players"
pg_dump: finding default expressions of table "players"
pg_dump: finding the columns and types of table "playervsplayer"
pg_dump: finding the columns and types of table "pokerhands"
pg_dump: finding default expressions of table "pokerhands"
pg_dump: finding the columns and types of table "compiledplayerresults"
pg_dump: finding the columns and types of table "compiledplayerresultspositionaction"
pg_dump: finding the columns and types of table "postflopactions"
pg_dump: finding the columns and types of table "compiledresults"
pg_dump: finding default expressions of table "compiledresults"
pg_dump: finding the columns and types of table "tourneydata"
pg_dump: finding the columns and types of table "tourneyplayerdata"
pg_dump: finding the columns and types of table "tables"
pg_dump: finding default expressions of table "tables"
pg_dump: finding the columns and types of table "bonuses"
pg_dump: finding default expressions of table "bonuses"
pg_dump: finding the columns and types of table "manuallyenteredsession"
pg_dump: finding default expressions of table "manuallyenteredsession"
pg_dump: finding the columns and types of table "rakeback"
pg_dump: finding default expressions of table "rakeback"
pg_dump: finding the columns and types of table "aliases"
pg_dump: finding the columns and types of table "settings"
pg_dump: finding the columns and types of table "tourneynotes"
pg_dump: finding the columns and types of table "hemplayernotes"
pg_dump: finding default expressions of table "hemplayernotes"
pg_dump: finding the columns and types of table "compiledplayerresults_month"
pg_dump: finding the columns and types of table "compiledplayerresultspositionaction_month"
pg_dump: finding the columns and types of table "postflopactions_month"
pg_dump: finding the columns and types of table "compiledresults_month"
pg_dump: finding default expressions of table "compiledresults_month"
pg_dump: finding the columns and types of table "optimizedplayers"
pg_dump: finding the columns and types of table "unoptimizedheros"
pg_dump: finding the columns and types of table "specialholecardactions_hero"
pg_dump: finding the columns and types of table "playerhandscashkeycolumns_hero"
pg_dump: finding the columns and types of table "playerhandstourneykeycolumns_hero"
pg_dump: finding the columns and types of table "allinsituations_hero"
pg_dump: finding the columns and types of table "playerhandscashmisc_hero"
pg_dump: finding the columns and types of table "playerhandstourneymisc_hero"
pg_dump: finding the columns and types of table "playerhandsflop_hero"
pg_dump: finding the columns and types of table "playerhandsturn_hero"
pg_dump: finding the columns and types of table "playerhandsriver_hero"
pg_dump: finding the columns and types of table "playervsplayer_hero"
pg_dump: finding the columns and types of table "pokerhands_hero"
pg_dump: finding the columns and types of table "holecards"
pg_dump: flagging inherited columns in subtables
pg_dump: reading indexes
pg_dump: reading indexes for table "gametypes"
pg_dump: reading indexes for table "actiontypes"
pg_dump: reading indexes for table "pokersites"
pg_dump: reading indexes for table "handhistories"
pg_dump: reading indexes for table "specialholecardactions"
pg_dump: reading indexes for table "importedfiles"
pg_dump: reading indexes for table "playerhandscashkeycolumns"
pg_dump: reading indexes for table "playerhandstourneykeycolumns"
pg_dump: reading indexes for table "allinsituations"
pg_dump: reading indexes for table "playerhandscashmisc"
pg_dump: reading indexes for table "playerhandstourneymisc"
pg_dump: reading indexes for table "playerhandsflop"
pg_dump: reading indexes for table "playerhandsturn"
pg_dump: reading indexes for table "playerhandsriver"
pg_dump: reading indexes for table "players"
pg_dump: reading indexes for table "playervsplayer"
pg_dump: reading indexes for table "pokerhands"
pg_dump: reading indexes for table "compiledplayerresults"
pg_dump: reading indexes for table "compiledplayerresultspositionaction"
pg_dump: reading indexes for table "postflopactions"
pg_dump: reading indexes for table "compiledresults"
pg_dump: reading indexes for table "tourneydata"
pg_dump: reading indexes for table "tourneyplayerdata"
pg_dump: reading indexes for table "tables"
pg_dump: reading indexes for table "bonuses"
pg_dump: reading indexes for table "manuallyenteredsession"
pg_dump: reading indexes for table "rakeback"
pg_dump: reading indexes for table "aliases"
pg_dump: reading indexes for table "tourneynotes"
pg_dump: reading indexes for table "hemplayernotes"
pg_dump: reading indexes for table "compiledplayerresults_month"
pg_dump: reading indexes for table "compiledplayerresultspositionaction_month"
pg_dump: reading indexes for table "postflopactions_month"
pg_dump: reading indexes for table "compiledresults_month"
pg_dump: reading indexes for table "specialholecardactions_hero"
pg_dump: reading indexes for table "playerhandscashkeycolumns_hero"
pg_dump: reading indexes for table "playerhandstourneykeycolumns_hero"
pg_dump: reading indexes for table "allinsituations_hero"
pg_dump: reading indexes for table "playerhandscashmisc_hero"
pg_dump: reading indexes for table "playerhandstourneymisc_hero"
pg_dump: reading indexes for table "playerhandsflop_hero"
pg_dump: reading indexes for table "playerhandsturn_hero"
pg_dump: reading indexes for table "playerhandsriver_hero"
pg_dump: reading indexes for table "playervsplayer_hero"
pg_dump: reading indexes for table "pokerhands_hero"
pg_dump: reading indexes for table "holecards"
pg_dump: reading constraints
pg_dump: reading triggers
pg_dump: reading dependency data
pg_dump: saving encoding = SQL_ASCII
pg_dump: saving standard_conforming_strings = off
pg_dump: saving database definition
pg_dump: dumping contents of table actiontypes
pg_dump: dumping contents of table aliases
pg_dump: dumping contents of table allinsituations
pg_dump: dumping contents of table allinsituations_hero
pg_dump: dumping contents of table bonuses
pg_dump: dumping contents of table compiledplayerresults
pg_dump: dumping contents of table compiledplayerresults_month
pg_dump: dumping contents of table compiledplayerresultspositionaction

[bpran]

pg_dump: dumping contents of table compiledplayerresultspositionaction_month
pg_dump: dumping contents of table compiledresults
pg_dump: dumping contents of table compiledresults_month
pg_dump: dumping contents of table gametypes
pg_dump: dumping contents of table handhistories
pg_dump: dumping contents of table hemplayernotes
pg_dump: dumping contents of table holecards
pg_dump: dumping contents of table importedfiles
pg_dump: dumping contents of table manuallyenteredsession
pg_dump: dumping contents of table optimizedplayers
pg_dump: dumping contents of table playerhandscashkeycolumns
pg_dump: dumping contents of table playerhandscashkeycolumns_hero
pg_dump: dumping contents of table playerhandscashmisc
pg_dump: dumping contents of table playerhandscashmisc_hero
pg_dump: dumping contents of table playerhandsflop
pg_dump: dumping contents of table playerhandsflop_hero
pg_dump: dumping contents of table playerhandsriver
pg_dump: dumping contents of table playerhandsriver_hero
pg_dump: dumping contents of table playerhandstourneykeycolumns
pg_dump: dumping contents of table playerhandstourneykeycolumns_hero
pg_dump: dumping contents of table playerhandstourneymisc
pg_dump: dumping contents of table playerhandstourneymisc_hero
pg_dump: dumping contents of table playerhandsturn
pg_dump: dumping contents of table playerhandsturn_hero
pg_dump: dumping contents of table players
pg_dump: dumping contents of table playervsplayer
pg_dump: dumping contents of table playervsplayer_hero
pg_dump: dumping contents of table pokerhands
pg_dump: dumping contents of table pokerhands_hero
pg_dump: dumping contents of table pokersites
pg_dump: dumping contents of table postflopactions
pg_dump: dumping contents of table postflopactions_month
pg_dump: dumping contents of table rakeback
pg_dump: dumping contents of table selectedplayer
pg_dump: dumping contents of table settings
pg_dump: dumping contents of table specialholecardactions
pg_dump: dumping contents of table specialholecardactions_hero
pg_dump: dumping contents of table tables
pg_dump: dumping contents of table tourneydata
pg_dump: dumping contents of table tourneynotes
pg_dump: dumping contents of table tourneyplayerdata
pg_dump: dumping contents of table unoptimizedheros

Process returned exit code 0.

[netsrak]

Exit code 0 means everything is fine, no errors occured.

Could you please post screenshots of your backup screen with your settings and your restore screen with your settings if you still have problems.