03-29-2016 11:50 PM
The other day after a reboot of the backup exec server the dedup service would not start again, se below error info:
C:\Program Files\Symantec\Backup Exec> spad --trace -v
Info: set entire process max log size to 0
Info: set entire process max log size to 0
Error: 25017: DaemonLockSimpleTestW: pipe already exists
Trace: CRMapError: called by SDDaemonActive (../common.c:79), errno = 231
Error: 25001: spad: a conflicting instance is currently active.
Error: 26016: Symantec PureDisk Storage Pool Authority: Bootstrap failure.
Trace: EventSystem::EventStorage::loadLimits Loading event storage limits
Trace: EventSystem::EventStorage::loadLimits Original age limit: 0. New age lim
it: 0
Trace: EventSystem::EventStorage::loadLimits Original count limit: 10000. New c
ount limit: 10000
Info: EventSystem::SpaDBEventStorage::SpaDBEventStorage Events table missing. A
dding from ini file: C:\Program Files\Symantec\Backup Exec\spadb.ini
Error: 25004: failed to create schema file: \spa\schema\events
Error: 25004: creat schema error [events]
Error: 25004: EventSystem::SpaDBEventStorage::SpaDBEventStorage Failed to add th
e events table in SpaDB
Info: EventSystem::SpaDBEventStorage::SpaDBEventStorage EventProperties table mi
ssing. Adding from ini file: C:\Program Files\Symantec\Backup Exec\spadb.ini
Error: 25004: failed to create schema file: \spa\schema\eventproperties
Error: 25004: creat schema error [eventproperties]
Error: 25004: EventSystem::SpaDBEventStorage::SpaDBEventStorage Failed to add th
e eventproperties table in SpaDB
Error: 25003: no such file [\spa\schema\eventproperties]
Error: 25003: Can't get table
Error: 25004: EventSystem::SpaDBEventStorage::SpaDBEventStorage Failed to add in
itial values for eventproperties
Info: EventSystem::EventManager::newEvent Adding new event. type:1
Trace: EventSystem::SpaDBEventStorage::writeEvent Event storage wasn't initializ
ed properly. Returning.
Info: EventSystem::EventManager::newEvent Adding new event. type:4
Trace: EventSystem::SpaDBEventStorage::writeEvent Event storage wasn't initializ
ed properly. Returning.
We have tried:
https://www.veritas.com/support/en_US/article.TECH222766 -> no luck
https://www.veritas.com/support/en_US/article.000082460 -> no luck
http://www.symantec.com/docs/TECH170960 -> no luck
03-29-2016 11:56 PM
Hi, I just stumbled accross this: https://www.veritas.com/support/en_US/article.000008062
Step 7) If Dcscan reports errors in the container then the bin file is corrupted and needs to be removed.
Please contact Backup Exec Support since a Internal Symantec Utility needs to be run to recreate the missing/corrupt bin file and confirm the Integrity of Content Router Database (crdb ). This is an Important procedure which needs to be carried out to ensure some backup set which are affected due to the missing/corrupt bin file (which contains dedupe segments) are identified.
So we need to have a support guy on our system.