In our enviroment, we have hundreds of copy jobs that run everyday except Thursday, this is by design, so if the server is rebooted, or is down for a day, the copy job will resume when it left off or start from the beginning. The issues is if a copy job takes longer than 2 days, when the second one is launched while the first one is running it generates a copy error, there should be a configuation to change this from an error to successful. With over 5,000 clients the failed copy jobs have to be validated and it is a huge waste of time. There should be similar options to the copy job when there are no object to copy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.