We have a problem with our Duplicate Jobs.
Sometimes when he wants to start an Duplicate job he stay's queued.. And after (the max configured time) 4 Hours he automatic canceled.
And after that he starts a new duplicate job, with the same problem...
I was wondering what i can do about this, because it happens sometimes:
Have you confirmed that the destination device (tape or disk) is not being used by any other resources when this duplicte starts??
If the device is busy for 4 hours then the job will be in queued state.
You can also increae the time maximum time configured from 4 hours to something more.