Backup Exec 2010 R3 SP2 PostgreSQL service fails to start

Article:TECH187299  |  Created: 2012-04-25  |  Updated: 2013-08-14  |  Article URL http://www.symantec.com/docs/TECH187299
Article Type
Technical Solution


Issue



Media Server Deduplication (MSDP) PostgreSQL service fails to start
 


Error



 PostgreSQL.log shows the following error: [Location of postgreSQL log is : Drive:\Deduplication_Database_Folder\log\pddb\postgresq-]

2012-04-13 07:49:09 CDT LOG:  database system was interrupted; last known up at 2012-03-21 13:38:20 CDT

2012-04-13 07:49:09 CDT LOG:  could not open file "pg_xlog/0000000100000076000000A4" (log file 118, segment 164): No such file or directory
2012-04-13 07:49:09 CDT LOG:  invalid primary checkpoint record
2012-04-13 07:49:09 CDT LOG:  could not open file "pg_xlog/0000000100000076000000A0" (log file 118, segment 160): No such file or directory
2012-04-13 07:49:09 CDT LOG:  invalid secondary checkpoint record
2012-04-13 07:49:09 CDT PANIC:  could not locate a valid checkpoint record

 

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
2012-04-13 07:49:09 CDT LOG:  startup process (PID 4452) exited with exit code 3
2012-04-13 07:49:09 CDT LOG:  aborting startup due to startup process failure
 


Cause



Service fails to start due to missing PostgreSQL transaction log file " pg_xlog/0000000100000076000000A4" (Log File is subject to change depending on database)
 


Solution



1. First make a backup copy of the dedup database directory (Windows <dedup_database_path>\databases\pddb). The backup copy may be needed in the event step 2 does not resolve the issue.

2. Open command prompt and change directory to Drive:\Program Files\Symantec\Backup Exec\pddb\bin\

Run the command below to reset the transaction log: pg_resetxlog.exe -f Drive:\Deduplication_Database_Folder\databases\pddb\data

3. Restart Backup Exec and Deduplication Services.

If the above command fails please also run CHKDSK to confirm the file system is healthy. If there are disk corruptions these need to be fixed prior to contacting technical support.






Article URL http://www.symantec.com/docs/TECH187299


Terms of use for this information are found in Legal Notices