The problem is that a Working set will work for a whole day (or days) period. But not for a user defined number of hours.
What I want to achieve is to create a "full" backUp of ONLY the files created or modified during an specified period of time, such as the last four hours previous to the back-up's job launch time.
I am not able to do an initial "full" backUp of the whole data since my current storage has about 8TB of data, so performing an initial full back-up will take prohibitibely long.
Besides, in this scenarrio the back-up is intended not for restoring the data in case of failure, but to be able to recover files modified during that period.
I think that if I elaborate on my scenario that will be clear.
This is a call center application, which records the conversation to HDD in WAV format. Each conversation correspond to a single file, and they are related to the information store via a SQL DB. The requirement is to be able to recover a single conversation in case it is necessary (mostly by a court rule). These conversations should be kept for up to two years.
As you can see, it is not a situation where the back-ups are inteded for recovering the state of the application. This conversations take up HDD storage so quickly that only a few weeks worth of data could be retained in the main storage, forcing the sysadmin to regularly delete "old" files.
A typical shift (about 8 hours) will generate about a 100 GB of voice data. Which should be backed up to tape before the next shift ends.
It is important to send to tape a whole shift of data, because that´s the way that it will be retrieved.. since a 100 GB of data could be stored in a single tape. So, if needed, a single tape would be required to retieve a particular conversation.
The whole schema depends on being able to back-up the data files generated during a particular shift. This why I need to be able to "select" only files created during that particular shift. thus the working set setting won´t do the trick.