Fried HD, database backup won't restore

[DerekG]

Hi Pat,

Long time, no hear! Just in time for taxes, I managed to fry one of my HD partitions containing PSQL and all my databases. I'm trying to recover it but so far things aren't looking good. I used the BugsBunny script from the old PSQL forum to cluster, analyze, and backup my databases into .backup files but I was fortunate enough to never have to restore them until now.

Ideally, I'd like to restore the database then convert it into PT3. Using PGAdmin I created a new database and selected SQL_ASCII encoding, however when I tried to restore I got about 30 ignored error messages and an exit code of 1 so I assume it was unsuccessful. I don't have PT2 installed on this computer but PT3 is still saying there are no PT2 databases to convert. In addition, the PT2 databases were created and backed up using PSQL v8.2 whereas only PSQL v8.3 is installed on this computer. I hope that doesn't hurt my chances. I can send you a log of the restore messages if you want.

What do you suggest?

[ptrack pat]

PT3 is looking for the registry entries PT2 uses so you are still going to have to install PT2 on this computer. If you need a new code after this, send me the PT2 product ID using the online support system and I'll send a code...
http://www.pokertracker.com/support/?cat_id=2

Once you do that, I would recommend you also reinstall PostgreSQL 8.2 - directions for that are here
http://www.pokertracker.com/products/PT ... nstallSQL2

Note that since you have PT3 installed you'll probably have to change the port # from 5432 to 5433 when you install 8.2.

When that is done, enter your settings on the Utilities > PostgreSQL Settings window.
Then try to use the Utilities > PostgreSQL Database Functions window to try to do the restore.

[DerekG]

Ok, code accepted for PT2.

Tried to see if the database would load, both the one installed manually into 8.3 and by using PT2 to restore into another database. Both times I got an "Error retrieving from the VERSION_INFO table, 7-SQLSTATE=42P01, version_info does not exist" error message. I assume that's why I need to reinstall PSQL v8.2? Reinstalling PSQL 8.2 now.

[ptrack pat]

The times I've seen this kind of error is when the restore didn't work either because the .backup is corrupted/incomplete or the use didn't allow the restore to finish (i.e. closed the DOS window manually instead of letting it close on it's own when it's done). Are you sure you let it finish?

[DerekG]

Yeah, I'm sure. At least I know I saw the DOS window close on its own and I didn't mess with it. I just assumed things weren't working because I was using 8.3 for the restore. You don't think so?

Running into another problem installing 8.2. I thought I had it uninstalled. Don't see it in Add/Remove Programs window, just 8.3. When I peek in the 8.2 directory, all I see is the /data subfolder so I assume this was uninstalled. However, when I open PGAdmin I still see servers listed for both 8.2 and 8.3.

I'm saying this because I cannot reinstall 8.2 right now. It hangs on the Service Configuration screen. After I enter a pw it says "Invalid Username specified: unknown username or bad password". Changing to a different password didn't help. I wonder if this is because I still have a Server/Service name called PostgreSQL Database Server 8.2 showing up in PGAdmin. Perhaps the service is still installed for some reason?

What do you suggest?

[ptrack pat]

The /data folder remains on your hard drive after you uninstall it. So you would have to delete that folder before installing 8.2 again.

The other error with the password, on the first window where you are prompted to enter a user name that starts the service, use "postgres_82" instead of the default "postgres". Then enter whatever password you want and it should work.

[DerekG]

The hits keep coming. Now it's saying on the Initialise Database Cluster window that the data directory needs to be on a NTFS formatted drive. This beater is still using FAT32 but back when PT3 was doing the PSQL installations automatically it seemed to work ok (as evidenced by the fact I just deleted the /data subfolder.)

[ptrack pat]

Maybe 8.3 doesn't require NTFS, although I would think it does. You can convert it to NTFS as described here, it's a relatively simple procedure...

http://support.microsoft.com/kb/307881

[DerekG]

Drive converted to NTFS with no apparent errors but I still have problems with PSQL. Info entered into PT2 but it's giving pw authentication errors for both PSQL 8.2 and now 8.3 when I open the Database Maintenance window.

I stopped and restarted service on both 8.2 and 8.3. 8.3 in particular takes forever to start. The DOS window remains open for minutes with it saying ............ but I'm not sure it ever starts. I go into PGAdmin and attempt to start the database server but I get a Server Doesn't Listen window that pops up now. I know the pw I entered was correct.

As far as 8.2 is concerned, the installation went smooth. I entered the same pw in all screens but I get an authentication failed error message. I opened PGAdmin and see the 8.2 and 8.3 servers listed, however both are showing 5432 as the port and the 8.2 server still has the old settings -- i.e. default database name postgres, not the one I used when I installed. I changed the port to what I used for installation (5482) and changed the maintenance database and username to my installation settings (postgres82). I left the Service at default (pgsql-8.2). Attempt to connect but I still get the Error Connecting to Server: pw authentication failed error message. Again, I know I entered the correct password during installation. Restarting windows and trying again doesn't work either. Help!

Congrats to PSQL, they created a program that's even more annoying than Windows.

[ptrack pat]

Go to the Start > Programs > PostgreSQL 8.2 > Configuration Files > Edit pg_hba.conf

At the bottom of the file there are 2 places that say "md5". Change them both to say "trust" and save the file.

Now try PT2 again and see if it still gives the password error.