Backup Exec Reclaiming space in deduplication folder

Issue

The Deduplication Drive may fill up due to longer retention or increase in the size and kind of data being backed up over a period of time. In this scenario, the Deduplication Storage Folder Drive can be extended or some backup sets can be deleted/expired manually to make some room for newer Backup Sets.

Reclaiming space in a deduplication folder:

1.  Expire the Backup Sets from Storage tab, Backup Sets. Do not attempt to erase IMG media.
2.  To force the deduplication folder to process its queue, open a command prompt (Start -> Run -> cmd) and use the following commands on the media server where the deduplication folder is located.

Default Installation Directory: C:\Program Files\Symantec\Backup Exec

cd “\Program Files\Symantec\Backup Exec”

crcontrol –processqueue
crcontrol –processqueueinfo

Continue to perform the crcontrol –processqueueinfo command periodically until it reports a “No” status for Busy and Pending.

Then repeat the process.

crcontrol –processqueue
crcontrol –processqueueinfo

Then perform garbage collection using the following command:

crcollect -v -m +1,+2

Then make sure the garbage collection commands get processed.

Then repeat the process.

crcontrol –processqueue
crcontrol –processqueueinfo

Then repeat the process.

crcontrol –processqueue
crcontrol –processqueueinfo

Continue to perform the crcontrol –processqueueinfo command periodically until it reports a “No” status for Busy and Pending.

3.  Compact the space in the deduplication folder.

crcontrol –compactstart

crcontrol –compactstate

Continue to perform the crcontrol –compactstate command periodically until it reports a “No” status for Compaction busy.

4.  Verify that space has been made available in the deduplication folder using the following command in the same command box that is already open.

crstats –convert-size

Note: Checking the free space available on the file system will not necessarily show any space has been freed up. This happens because the deduplication folder service does not delete the files it has allocated, but instead will use the free space available within those files.
Even with all of this, one has to remember that the entire purpose of a deduplication folder is to try to keep only one copy of data in the folder no matter how many times it has been backed up.

Example: If there are 5 pieces of media that have full backups of a particular system and the above procedure to delete 4 of those 5 media, very little space will be reclaimed.

This is because all 5 pieces of media reference one copy of the data. A particular chunk of data can’t be erased and the space freed until all references to it have been deleted first.

Note: There are rare circumstances in which some objects cannot be released during the garbage collection phase.  In these cases, it is necessary to stop and restart the Backup Exec Deduplication Services.  In order to restart the BE Deduplication services on the media server, use the following procedure:

Stop the Backup Exec services.

Using the Windows Service Control manager, stop the following services in order.  Keep in mind that these services may be in the middle of processing operations.  If the service does not shutdown, wait until it is not busy and try again.

Backup Exec PureDisk FileSystem Service

Backup Exec Deduplication Engine

Backup Exec Deduplication Manager

postgresql-8.3

Then restart the services in the reverse order, and start the Backup Exec services.

2 Replies to “Backup Exec Reclaiming space in deduplication folder”

Leave a Reply