That was way too simple, I was apparently overthinking it. Thanks, Joel. :)
The bad news is: there were no active handles displayed for the drive in question.
The good news is: I found the culprit.
The [expletive deleted] Windows recycle bin. Apparently the default setting for the recycle bin...
Unfortunately, no. I'm not too familiar with the usage of Handle or Process Explorer. :(
I've never really gotten down beyond the process level in the course of my admittedly limited admin experience.
I poked around with Handle a little bit, but couldn't figure out how to filter the results...
Overwriter:
Thanks for the replies. :)
A) There's nothing on the drive except an MSSQL database backup (*.bak) file (which has not been loaded directly into SQL... see below workflow for explanation).
B) Though there is backup software running on the server (Veritas BackupExec 10.0 Rev5484)...
I had a sneaking suspicion that antivirus might be the culprit, however, I'm still not having any luck.
Running Symantec Corporate v10.1.4.4000: Disabled autoprotect via the gui, no luck. Stopped all Symantec services manually... still no luck. :(
Edit: the reason I correlate this issue with...
Using Eraser 5.86.1 on Windows XP (SP3) and Windows Server 2003 (SP1).
After running a free space wipe using US DoD 5220 22-M (8-306. / E) 3 passes on an external USB hard drive (not flash memory), I am encountering problems using the "safely remove hardware" function to dismount the drive...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.