Crcontrol --dsstat reports usage that does not match the Windows Explorer usage for the Drive on which the Deduplication folder is created.

Problem

Crcontrol --dsstat reports usage that does not match the Windows Explorer usage for the Drive on which the Deduplication folder is created.

Cause

 

Explanation about the statistics shown in the following screenshot is as follows:

  1. Number of containers [Total number of containers in the Deduplication folder].
  2. Space allocated for containers [Total space occupied on the volume where the Deduplication Folder is created].
  3. Space used within containers [Total space used on the volume where the Deduplication Folder is created].
  4. Space available within containers [Total space which can be re used on the volume where the Deduplication Folder is created].
  5. Space needs compaction [Total space which can be freed up using the compaction command on the volume where the Deduplication Folder is created.

 

Solution

Deduplication folder does not delete or truncate empty containers. The space seems consumed from Windows Explorer but it is available for use.
Note : The Space available within the containers will be reused by the Backup Jobs which are targeted to the Deduplication Storage Folder.

 

 


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)