Long duration optimized duplication job when using OST plugin
Question for anyone who's listening...
We have implementanted two OST aware deduplication devices on Backup Exec 2010 R3 and running into unusually long duplication job times between the appliances. There is no network activity on the media server or on the dedup appliance during the jobs. The is also minimal processor and disk activity, so it appears as though nothing is happening. However, at ten minute increments (almost on the nose) the byte count for the job increases and then sits again for 10 minutes. The appears to be no relation to media set file size and duration of increment, a 10GB media set takes as long as a 800GB media set. It is as though it is waiting for a file timeout before moving the the next media set in the backup. We usually have multiple jobs running concurrently, but on dup jobs only one job will increment at each 10 minute interval. Any active backup jobs cease until the dup jobs complete. Add these symptoms together and our "optimzed" duplication jobs take hours to complete and almost always push off our incremental\differential backup schedules.
As anyone seen this behavior or have any idea how to fix it? Since no data is actually being copied between the devices, just pointers and catalogs of the new location creaated, I would think these jobs should run a few minutes, not step on each other and take hours to complete.
Thanks for any help!