Symptoms
The migration job fails with the following error message in the job log:
<IP> <time stamp> SNBJH_3069E *** Job jobid(ID number) tgid(1) node(node name) disk(drive letter:) was not cataloged ***
Resolution
The expiration time of the migration job is counted from the start time of the original backup job. If the expiration time of the migration job has already passed using this start time marker, and the original backup job has a longer expiration time set, the migration job is immediately expired. The above error message displays.
For example, an original backup job has a 100 day expiration policy, while the migration job has a 90 day expiration policy. When the migration job was running, the 90 days had already passed if counted from the start of the original backup job and the migration job was immediately expired.
To resolve this issue, set the migration job’s expiration time to a number larger than the amount of days that have passed since the start of the original backup job and the current date.