Unable to restart the deduplication folder after a power failure on the media server because the postgresql-8.3 service will not start.

Article:TECH136974  |  Created: 2010-01-25  |  Updated: 2012-02-10  |  Article URL http://www.symantec.com/docs/TECH136974
Article Type
Technical Solution


Issue



Unable to restart the deduplication folder after a power failure on the media server because the postgresql-8.3 service will not start.


Error



Windows could not start the postgresql-8.3 service on Local Computer.

Error 1053: The service did not respond to the start or control request in a timely fashion.


Cause



If the machine is powered down while the postgresql-8.3 service is still running, it is possible that the file that postgresql uses to determine if there is already an instance running is still on the system.  The presence of this file prevents the postgres service from starting up because it thinks it is already running.


Solution



1. Search for the <Storage>\databases\pddb\data\Postmaster.pid file.  Where <Storage> is the path of the deduplication folder.

2. Use the Windows Services Control Panel to make sure that the postgresql-8.3 service is not running.  If it is not running, delete the <Storage>\databases\pddb\data\Postmaster.pid file.

3. Start the Backup Exec Deduplication Manager service.
 

Supplemental Materials

SourceUMI
ValueV-370-59792-40000
Description

Backup Exec Support Tool Report - "Is Backup Exec Deduplication service, postgresql-8.3, failing to start due to a left over postmaster.pid file?"


SourceEvent ID
ValueError 1053
Description

The service did not respond to the start or control request in a timely fashion.


Legacy ID



358058


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


Terms of use for this information are found in Legal Notices