Media Server Deduplication (MSDP) fails to work / start due to the Postgres ( postgresql-8.3 ) not starting

Problem

Issues with MSDP, being caused by the Postgres database is not starting.

Cannot start the Postgres service ( postgresql-8.3 ) will impact the ability to use the NetBackup Deduplication option.  The problem has occurred after a restart of the NetBackup services or a reboot or the media server.

No errors appear in the Postgres logging ( <Storage>/log/pddb/<logs> ), and no errors appearing the system logging.  The Postgres service starts and stops immediately.

Error Message

The services produce the following messages in the Event logs; “Service started and then stopped. Some services stop automatically if they are not in use by other services or programs “.

- There are no logs being created for the Postgres database on Windows.

- Postgres will not start from the command line, and this is TRUE even if there are no problems.  If attempted the following message is seen;

 "<Install_Path>\Veritas\pdde\pddb\bin\pg_ctl.exe" runservice -N postgresql-8.3 -D "<Database_Location>\Database\databases\pddb\data" -w

pg_ctl: could not start service "postgresql-8.3": error code 1063


- However, if an attempt to start the Postgres service from the command, use the example below.  The key response indicating an issue is, ' Does not exist ';

"<Install_Path>\Veritas\pdde\pddb\bin\pg_ctl.exe" start -N postgresql-8.3 -D "<Database_Location>\databases\pddb\data" -w
waiting for server to start...2011-09-20 10:29:49 GMT FATAL: data directory "<Database_Location>/databases/pddb/data" does not exist

- The data folder does exist, and can be accessed and viewed without issues.

- Postgres error ' 58P01 'may appear, indicating an Undefined File

NB: LOGGING:
The verbose ' pg_ctl.exe ' command on Windows and Postgres logging, edit the ' postgresql.conf ' file in  ' <Database_Location>\databases\pddb\data ' directory and change the log location and verbosity. Look for the section: "ERROR REPORTING AND LOGGING", however, these extra logging levels DID  NOT  HELP.

Solution

Investigate the disk where the NetBackup MSDP programs are installed ( C\: for example ), and if there is a file or directory called ' Program ', then please move, rename or remove it.   Now attempt to restart the Postgres database.

Applies To

NetBackup 7.1
Operating system Version : Windows 2008