Backup Exec Deduplication SPAD service is seen to crash and get in a loop trying to start
|Article:TECH212803|||||Created: 2013-11-26|||||Updated: 2014-01-17|||||Article URL http://www.symantec.com/docs/TECH212803|
Backup Exec Deduplication folder is unable to be accessed due to deduplication service that are no longr able to load and SPAD service getting stuck in a crashing loop. The Backup Exec Deduplication services fail to start and the Deduplication folder will not come online.
From the Application Event log:
26016: Spad: checkUpdateCRMode failure
Stop Backup Exec Deduplication Enginer service, along with the Backup Exec Deduplication manager service and Postgresql service so that they are no longer tying to start. Target backups to a B2D (Backup To Disc) or Tape target. If the retention period is somewhat short on the Deduplication folder, like two weeks, and not overly large in capacity, one might consider creating a new Deduplication folder and use that. Once the retention period passes for the original Deduplication folder, if it is no longer needed, it could be be deleted and that space freed up.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned in this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
When SPAD starts, it shuts down right away and gets caught in crashing loop
Article URL http://www.symantec.com/docs/TECH212803