Running a Phase 2 following a successful Phase 2 Fails with a Media Timeout or another reason.
You then try to run the Phase 2 again, launching it from the previous Phase 2 that failed, same as you would a failed backup job.
The Phase 2 launched from the failed Phase 2 fails instantly with no reason.
This is identified as BUG-3625
The scheduler is unable to locate (in its db table 'jobinstance') the correct instance to use as the origin/source for the duplication phase, and hence the issue.
Workaround:
If you need to re-run the Phase 2 an additional time, make sure it is run from the first successful Phase 2 instance.
If the Phase 2 fails after the Phase 1 backup, you will not experience this issue, it will try to re-run as expected
Status:
