If the services starts up, it is also important to note that the queue processing in dedupe is working. If tlogs ( inside dedupe\queue) are older than a couple of days and are not going away then this could mean there may be something wrong with the internal queue process.
This would help to determine the root cause of why these files went missing. Event viewer should be looked at to determine when the error started and what issue was encountered on that day. Some root causes already known (AV quaratined the files, disk issues ). Even after the tool is run, it is important the root of why these files went missing should be investigated so that the Issue does not recur in future. Please contact Tech Support if unable to find that bin or bhd since a tool will then need to be run to bring dedupe in a consistent state and for the dedupe engine service to start.
The container number is reported in the event viewer (application section). (It could be the AV quarantined these files or disk Issues or abrupt reboots). The Data folder contains all containers (bin and bhd) which houses the unique segments).
This can be compared with another working system if available:īackup Exec Deduplication Engine may not start if any bin or bhd file goes missing from Dedupe\Data folder.
PostgreSQL or any other deduplication service startup issues due to registry set incorrectly. Confirm ImagePath is accurate. If any one does not start, then following can be checked: Deduplication Engine, Deduplication Manager, Postgres, are all run under local system account. Deduplication folder credential in Backup Exec (BE) have changed and not updated on the Deduplication SPA databaseĮnsure all Dedupe services can be started. Ensure an AV exclusion is set for the drive on which Deduplication Folder is created.ĭeduplication folder in Backup Exec may show offline due to any of the following:. Ensure Windows indexing is unchecked for this drive. Run a CHKDSK to ensure the drive on which the Deduplication Folder is hosted is free from any corruption. 
It is important to start your checks by making sure the disk is healthy.
Restore from a deduplication device does not work.ĭedupe service not starting, Dedupe credentials not correct, Dedupe folder corruption. Backup fails when targeted to a deduplication device but works on a regular disk storage. Backup Exec 20 does not use PostgreSQL, so some commands that are suited for Backup Exec version 2014, 15, 16 may not apply to Backup Exec version 20 deduplication storage. Note: Backup Exec version 2014, 15, 16 utilize PostgreSQL as the backend database in deduplication storage folder. This is a troubleshooting article showing some of the Issues that one might encounter when working with the Deduplication storage and how to go about solving them or collect info that would help Veritas Technical Support to solve it quicker for you.
0 kommentar(er)
