Data Deduplication encountered a corrupted metadata file. To correct the problem, schedule or manually run a Garbage Collection job on the affected volume with the -Full option. %1
Data Deduplication detected a new container could not be created in a chunk store because it ran out of available container ...
Data Deduplication detected an insecure internal folder. To secure the folder, reinstall deduplication on the volume again. ...
Data Deduplication detected job type "%1" on volume "%2" page fault rate has lowered to desirable level. The rate is %3 page ...
Data Deduplication detected job type "%1" on volume "%2" page fault rate is high. The rate is %3 page faults per second. ...
Data Deduplication encountered a corrupted metadata file. To correct the problem, schedule or manually run a Garbage Collection ...
Data Deduplication encountered a IO device error while accessing a file on the volume. This is likely a hardware fault in ...
Data Deduplication encountered an error while attempting to resume processing. Please consult the event log parameters for ...
Data Deduplication encountered an unexpected error during volume scan of volumes mounted at "%1" ("%2"). To find out more ...
Data deduplication encountered an unexpected error. Check the Data Deduplication Operational event log for more information. ...