Deduplication Storage Folder shows "Offline"
storaged.log from the deduplication folder reports the following error:
Query : INSERT INTO objects2 SELECT * FROM objects WHERE (key > %b) ORDER BY key;
Called by : pqObjects2CopyFromObjects
Reason : ERROR: could not extend relation 1663/3007121/4342349: No space left on device
HINT: Check free disk space.
10 ERR : 25004: TlogProcessLog: Commit to storage database failed: unknown error
WARNING : 25000: Transaction log B:\B2D\queue\sorted-965847-965851.tlog failed: TlogProcessLog: Commit to storage database failed: unknown error
Transaction will be retried.
- Ensure there is enough free space on the volume where the Deduplication Storage folder resides.
- Ensure there is enough free space on the volume where the Deduplication Database resides.
- It is recommended to have a Dedicated Volume for the Deduplication Folder.
Inorder to check the accurate space used by deduplication device please run the "crcontrol" command with option dsstat
e.g, c:\proram files\symantec\backup exec\crcontrol --dsstat.
For more details on getting the deduplication folder statistics, refer the article http://www.veritas.com/docs/000012160
To free up space on deduplication storage folder please refer the article ttp://www.veritas.com/docs/000007234
Note:- Deduplication Storage folder and the Deduplication Database reside on different volumes only till Backup Exec 2010 R2 and if upgraded from Backup Exec 2010 R2 to R3. For a new installation of Backup Exec 2010 R3, the Deduplication Storage folder and the Deduplication Database cannot reside on different volumes.