Not Applicable
This is 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.
There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. However, the issue has been addressed in the revision of the product specified at the end of this article.
Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.
Customers experiencing this issue are advised to upgrade to DLO 9.8.3 version.