In fact, I performed 3 RSG operations in the last seven days. All were successfull. That's the good part. I did have to redo one RSG so that may count as 4 operations, with a 3/4 success rate. The problem is that I cannot delete the log folder associated with one of these RSG operations. It may be that I planned to remove the RSG after dismounting and then, the following day, went ahead and deleted the associated folders and files anyway. At any rate, when I attempt to delete the folder, the operation fails because the restore.env file inside the RSG folder is supposedly in use. Database Recovery Manager currently shows no option to Remove an RSG so I'm wondering if in fact I did remove it correctly after all. This is a screenshot of the error message (yes, I could delete the log files themselves): http://hvjbtw.blu.livefilestore.com/y1pS_Q17OxdIPsSfoeArb_OlpLn3rZeu0Yx9gVkjnNZrC2kbqKF1pMGdLKTmPBao79_tLBu0YcZoZ5PlsgpqOXAmObGRoDXxMrL/LOG-Cannot-Delete.JPG?psid=1 So, if you are guessing that I would like to know how to delete this file, you've guessed right. I want to keep my Exchange server as clean as possible. Files/folders associated with all other RSG were deleted without a problem after removal of the corresponding RSG. This one, though, is giving me grief!

What are you using for restores and backups? Can you stop the service associated with the backup software and try again? Process Monitor should show what is holding that file if you dont want to reboot and see if you can remove after that :P http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

UltraBac It is stopping me from disconnecting (properly that is...) the external HD I used for the latest RSG operation. Very nice reporting in the Windows 2008 (SP2) Event Viewer. Tells the Process ID and everything. I stopped the service but that did not help there. So I think it may be involved with the other file (mentioned in my 1st post). Do you think I can just kill the offending process - there are two corresponding to ub.exe ? Because yes (not wanting to reboot), a full restart seems like overkill.

I contacted the vendor and double-checked I could kill the process in Task Monitor without causing problems. For Ultrabac users: ub.exe should not continue running after the backup/restore operation. It can safely be stopped when such an operation is not taking place. So I killed the process (two in fact) and was able to delete the files in question.