The issue maybe encountered when two jobs were running on the same media server, and were concurrently transferring data from one Deduplication device to another.  However it was also found that if two jobs  on one media server were running concurrently from any source to two separate Deduplication devices the same condition could be met that would cause the write operation to truncate data on one of the Deduplication devices.

In both scenarios the corruptions happens when both of the Deduplication devices attempt to mount media at the same time.

Here are the requirements for this situation to occur:
 

1. There must be two deduplication devices actively in-use on the same media server.  The types of deduplication devices include any combination of:
 

a. One or more Deduplication Storage Folders
 

b. One or more supported OST/deduplication hardware appliances. Example: PureDisk, DataDomain or ExaGrid
 

2. The two deduplication devices must be changing media at the same time.  The media change operation happens by default every 50 GB or when a new job starts that uses an OST device.