We do see aux copy completed with error because of skipped jobs But we dont see the job id gui not even in the logs. is there any way to see the job when it say job is skipped ?
Solved
Aux copy finished with completer error
+4Best answer by Mike Struening RETIRED
Sharing the Closure Pending reason:
Finding Details:
Based off your previous update, we see this error, as you suspected, when the job would have already met the secondary copy retention.
This can happen when the aux copy has not run, causing a delay of the backups being copied over to the secondary. Once they are, they would have already met retention and are skipped.
When checked the CSDB, we see below parameter is enabled: Based off your previous update, we see this error, as you suspected, when the job would have already met the secondary copy retention.
This can happen when the aux copy has not run, causing a delay of the backups being copied over to the secondary. Once they are, they would have already met retention and are skipped.
When checked the CSDB, we see below parameter is enabled:
"Disabling Jobs for an Auxiliary Copy that meets the Retention Criteria"
Disabled the parameter and escalated the case to Dev
Solution:
Synth full jobs on Weekend is failing and getting marked as Do not Copy causing the aux copy to complete with the message
+23- Vaulter
- 4996 replies
Hey
I looked around and don’t see anywhere the jobs are documented. The error is essentially saying that if you copied these jobs over, they would age right away (so why bother wasting the time).
With that in mind, I don’t think we document the job list, they are just skipped/not collected via your rules.
This was discussed well in this post here:
And there’s a KB for a similar error (same idea) here:
+4+23- Vaulter
- 4996 replies
- Answer
Sharing the Closure Pending reason:
Finding Details:
Based off your previous update, we see this error, as you suspected, when the job would have already met the secondary copy retention.
This can happen when the aux copy has not run, causing a delay of the backups being copied over to the secondary. Once they are, they would have already met retention and are skipped.
When checked the CSDB, we see below parameter is enabled: Based off your previous update, we see this error, as you suspected, when the job would have already met the secondary copy retention.
This can happen when the aux copy has not run, causing a delay of the backups being copied over to the secondary. Once they are, they would have already met retention and are skipped.
When checked the CSDB, we see below parameter is enabled:
"Disabling Jobs for an Auxiliary Copy that meets the Retention Criteria"
Disabled the parameter and escalated the case to Dev
Solution:
Synth full jobs on Weekend is failing and getting marked as Do not Copy causing the aux copy to complete with the message
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.