I've done something similar. What I do may not be the most ideal, but it works. I have a job that runs once a day to move logs from Directory A on a specific server and moves them to a central log repository on another server (this runs on several servers). When the job starts, it reads in a file that contains a list of the logs that have already been moved. Then it gets a list of files in the directory and moves anything that is not on the list. Not perfect since it relies on an external file, but it works pretty nicely. What you might want would be a list of files that have already been processed stored in some sort of Perl data structure.