Is it possible that deleting files from a Windows 2003 R2 command prompt, could be deleting the wrong files?
We have a voice recording server thats sole purpose is to listen in on phone lines and record what it hears to a wave file.
Per client requirements, we are required to keep these calls for 90 days, so every monday, i have a batch job i run (just a simple .bat file) that i increment the files i want to delete (del a_yyyymmdd*) and run it
after years of operating like this, we think windows is deleting the wrong files. for example, this week, i would have deleted feb 09- feb-13 (3 months ago)
but we're finding that it deleted last weeks phone calls
i'm positive my batch job is coded properly, i've been doing this every monday for the last 4 years
we've decided to not run the batch job next monday and see what happens, but has anyone seen this?
a little more specific - there are 10000's of these files in the folder per the call recording software vendor, we do nothing to this server; no service packs, no updates, no antivirus, nothing. its truly, internal, specific purpose.
i think its some sort of file system corruption
any ideas?
-------- the batch file with client names converted to #'s --------------
cd cappman
copy rec_06\a_20110130*####* ####
copy rec_06\a_20110131*####* ####
copy rec_06\a_20110201*####* ####
copy rec_06\a_20110202*####* ####
copy rec_06\a_20110203*####* ####
copy rec_06\a_20110204*####* ####
copy rec_06\a_20110205*####* ####
copy rec_06\a_20110130*####* ####
copy rec_06\a_20110131*####* ####
copy rec_06\a_20110201*####* ####
copy rec_06\a_20110202*####* ####
copy rec_06\a_20110203*####* ####
copy rec_06\a_20110204*####* ####
copy rec_06\a_20110205*####* ####
cd rec_06
del /q a_20110130*
del /q a_20110131*
del /q a_20110201*
del /q a_20110202*
del /q a_20110203*
del /q a_20110204*
del /q a_20110205*
cd..
copy rec_07\a_20110130*####* ####
copy rec_07\a_20110131*####* ####
copy rec_07\a_20110201*####* ####
copy rec_07\a_20110202*####* ####
copy rec_07\a_20110203*####* ####
copy rec_07\a_20110204*####* ####
copy rec_07\a_20110205*####* ####
copy rec_07\a_20110130*####* ####
copy rec_07\a_20110131*####* ####
copy rec_07\a_20110201*####* ####
copy rec_07\a_20110202*####* ####
copy rec_07\a_20110203*####* ####
copy rec_07\a_20110204*####* ####
copy rec_07\a_20110205*####* ####
cd rec_07
del /q a_20110130*
del /q a_20110131*
del /q a_20110201*
del /q a_20110202*
del /q a_20110203*
del /q a_20110204*
del /q a_20110205*
cd ..
cd rec_06
del /q a_20110301*####*
del /q a_20110302*####*
del /q a_20110303*####*
del /q a_20110304*####*
del /q a_20110305*####*
del /q a_20110306*####*
del /q a_20110307*####*
cd..
cd rec_07
del /q a_20110301*####*
del /q a_20110302*####*
del /q a_20110303*####*
del /q a_20110304*####*
del /q a_20110305*####*
del /q a_20110306*####*
del /q a_20110307*####*
just checked event viewer this morning - nothing out of the norm; my recent reboots, group policy syncing, etc...
on top of all of this, the folders listed above aren't the primary recording folder - every 3 weeks or so, i rename the main rec folder to rec_0# to try to cut down on how many files are in the main folder. the recording program is old; it doesn't have a means of retention date so i've had to deal with it on my own; so files being deleted from last week, is absurd because we're not even deleting files from the main rec folder (where those files are) - we're deleting files from these other folders (reason for doing the delete on 06 and 07
like i said, where you see the #### is a client name; the differences in deletes and copies is the difference in keeping some clients calls for a longer time, or a shorter time.
-Mario