thanks for your answer.
Yes, you are right, but I created a script that enables the copy jobs after a backup is done and disables them after they have "completed" most of work.
I do this because I have many copy jobs and each holds some memory even when it is idle, but releases it when disabled.
As I said I monitor the log for understanding if a copy job completed most of the work. This seem to be failing sometime.
Most of the times (monitoring the log) I can successfully disable the job, but from time to time I get a warning status that I think is caused because I disabled the job before it completed some phase like health check or compact backup.
So I would like a way (if it exists) to understand if the copy job completed the work in this interval and will stay IDLE until the next.
I understand, I am possibly distorting the original logic behind the back copy job, but I need that in the environment I have
Thanks and regards