Granular Recovery Technology (GRT) enabled backup of Exchange Information Store reclaims space from Expired IMG folders but does not remove the expired IMG folder completely.

Article:TECH66499  |  Created: 2009-01-07  |  Updated: 2013-11-22  |  Article URL
Article Type
Technical Solution


IMG folder is not removed after GRT enabled backup of Exchange Information Store reclaims space from Expired IMG folders.


A GRT backup to Disk always writes the backup information into an IMG folder within the Backup to Disk folder (B2D) . These IMG folders are then retained on the system depending on the Overwrite Protection Period that was set on the Media Set configured in the backup job.

Starting from Backup Exec 12.0, whenever a GRT backup starts, it looks for the expired IMG media under the specified B2D folder. If it finds an expired IMG media then it reclaims space on the hard disk by deleting this IMG folder and then creates a new IMG folder for the current backup operation. If there is no expired IMG media it proceeds to create a new IMG. This way the space on the B2D volume is maintained depending on the Overwrite Protection Period applied on these IMG media.

Whenever space from an IMG media is reclaimed by a GRT backup job an Alert is logged in Backup Exec as shown below.(Figure 1)
Figure 1.

In certain cases it has been observed that the space from the expired IMG media is being reclaimed however the IMG folder itself are not completely removed from the B2D volume. When Backup Exec attempts to remove the expired IMG folder, it cannot do so because the "WMIPRVSE.EXE" process has a lock on certain files inside the expired IMG folder and Backup Exec cannot delete them.  Running a process explorer for ese.dll shows the following(Figure 2)

Figure 2.

The above mentioned issue is mainly seen in but may not be limited to Windows Small Business Server 2003.


The expired IMG folder cannot be deleted unless the "WMIPRVSE.EXE" process is stopped. To delete the expired IMG media please follow the steps mentioned below:

Workaround 1
1. On the Backup Exec server, stop the Windows Management Instrumentation (WMI) service.
Note: There will be other services dependent on the WMI service, which also will be stopped.
2. Delete all the expired IMG folders that have been left behind and have only the ESE.DLL file in it.
3. Start the Windows Management Instrumentation (WMI) service.
Workaround 2
Leave the IMG folders on the server until the lock is released and then delete them (after planned reboots etc). This as minimal space is used for this and that it does not cause any issue with Backup Exec functionality.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices