On Jul 9, 2008, at 1:48 PM, Bell, Charles (Chip) wrote:
... The application (an imaging app) on the host machine writes to a mount point until reaching a 80% utilized threshold, and then begins writing to the next numerical mount point. Last February, they started with mount point 1, and now they are on 12. ...
I would approach a situation like this on a logical basis... In that the app is doing the Mad Hatter's Tea Party thing (abandon the current position and move on to the next clean place at the table), I would have the backup initiate from a script on the client, which would run a backup of only the latest volume, and there use Incrbydate in that the list of Active files is pointless in a case like this. You could run an infrequent, staggered Incremental of the earlier volumes if you felt compelled, just in case. Repeatedly running a backup scan against static volumes is just waste. Richard Sims
