Deduplication requires Content Router Queue Processing (CRQP) to be run on a regular Interval to ensure the internal databases are in sync with the Backend Storage. If this is not run or does not run, then a backlog of transaction logs will be generated and eventually (after 30 days by default) the Dedupe Storage will refuse new data. The CRQP is initated by the Backup Exec DeDuplication Manager service executing "BE Install Path\crcontrol --processqueue", if this fails then the CRQP will not run
Error from sched_QueueProcess.log from BackupExecDeduplicationStorageFolder\log\spad folder :
January 31 00:20:01 INFO [00000000025A4E90]: START: "C:\Program Files\Symantec\Backup Exec\crcontrol" --processqueue
January 31 00:20:01 ERR [00000000025A4E90]: 4: Create Process failed: "C:\Program Files\Symantec\Backup Exec\crcontrol" --processqueue
A 0kb file was found in BE Install Path called "crcontrol" which was incorrectly being picked up by the Deduplication Manager rather than Crcontrol.exe
Remove the crcontrol file which is 0kb in size and CRQP should run now.
Note : Ensure the queue is being processed Daily. By default the CRQP runs twice a day. One way to check the queue is being processed daily is to make a note of the oldest tlog present in Dedupe Storage location\queue folder and ensuring it goes away the next day. The auto CRQP triggers are logged in sched_QueueProcess.log located at BackupExecDeduplicationStorageFolder\log\spad folder.
To check if the queueprocess is running or not check the "storaged.log" located in BackupExecDeduplicationStorageFolder\log\spoold folder.