Deleting Users or Computers from the DLO Administration Console can take a long time to complete

Problem

User or Computer deletions, carried out from the DLO Administration Console, can take a long time to complete;  i.e. days\weeks.

While they are being processed or waiting to be processed, the User or Computer will show as 'Delete Pending' in the DLO Console, but will be removed once the deletion has completed.

Note: While deletions are being processed, Automated Integrity Checker (AIC) and Garbage Collection processes will not be able to run.

Error Message

Not Applicable

Cause

This is still being investigated, but appears to be due to the number of dedupe chunk records that need to be processed in the user's UserHashStore.db. 

Dedupe in DLO only stores unique chunk data once and any other user that shares that same data, adds to the reference count for that chunk, in the dedupedb.
When a user or computer is marked to be deleted and uses a Dedupe enabled DLO Profile, their backup data has to be individually reviewed, to remove their association to the data chunks and if they are the only user associated, that data chunk can then be flagged to be deleted. This process can take an extended period of time, if users have a lot of data stored in dedupe, as chunks are reviewed one-by-one and, if multiple users or computers are marked to be deleted, data for only one user or computer can be processed at a time.

Solution

This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.
 
Note: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.