Aux copy jobs are stuck on 99%

Hi @Mike Struening , thanks for the explanation. I simply let the job running and after some time the backup task was completed.

Great, thanks for the confirmation!

I am dealing with this now- at what point will it stop? Hate to think of jobs queued because this is still running. What changes have you both made to keep this from happening?

Hi @Matthew M. Magbee , as far as I remember, we let the backup jobs running and after some time, they were finished. What to do from happenig this… In our case we had a lot of backup jobs to do/copy, because there were performance issues on the switch/storage array.

@Matthew M. Magbee , I believe this is what you are looking for:

https://documentation.commvault.com/2022e/expert/11545_auxiliary_copy_faq.html#how-do-i-prevent-data-of-ongoing-backup-jobs-from-being-copied

How do I prevent data of ongoing backup jobs from being copied?

For auxiliary copy operation with Use Scalable Resource Allocation option not selected, all eligible data even from the backups that have finished after the auxiliary copy operation has started are selected to be copied. However, you can prevent this data of ongoing backup jobs from being copied by adding the AUXCOPY_NOT_PICK_NEW_BACKUPS additional setting.

• On the CommServe computer, add the AUXCOPY_NOT_PICK_NEW_BACKUPS additional setting with value 1.

  For instructions on adding the additional setting from the CommCell Console, see Add or Modify an Additional Setting.

  Refer to the following table for applicable values:

Im actually running it that way now. while it eventually ends without issue- its delayed quite a bit. 

@Matthew M. Magbee , hmmmm…..is the job sitting at 100% for a while and eventually finishes, or does the aux just take a while to run?

How long are we talking start to finish and how much data?

Not sure how i missed this question, the job does not hit 100% - 99% then can run for addtional days