Chapter 4
4. Following jobs in Iconik
Open Jobs in Iconik to follow archive and restore work. XenData for Iconik updates these jobs as XenData reports progress.
4.1 What one request creates
Each request creates up to two parent jobs in Iconik.
| Parent job | Contains |
|---|---|
| Processing job | One sub-job for each asset sent to XenData |
| Skipped job | One sub-job for each asset that was skipped |
If no asset was skipped, XenData for Iconik deletes the empty skipped job. If every asset was skipped, the processing job finishes at once with No assets to process - job completed.
Parent jobs use the Iconik job type CUSTOM. Sub-jobs use the type ARCHIVE or RESTORE.
| Sub-job title | Meaning |
|---|---|
XenData Archive - <file name> |
This asset is being archived |
XenData Restore - <file name> |
This asset is being restored |
XenData Skipped - <file name> |
This asset was skipped; read the message for the reason |
4.2 Statuses and progress
| Status | Meaning |
|---|---|
| WAITING | The job is created and waits to go to XenData |
| STARTED | XenData accepted the work |
| FINISHED | The work completed |
| SKIPPED | The asset did not need the work |
| FAILED | The work did not complete; read the message |
Progress starts when XenData accepts the work. It moves between 10% and 90% as XenData reports progress. It shows 100% when the job finishes, fails, or is skipped.
A parent job is FINISHED when each of its sub-jobs is FINISHED or SKIPPED. If one sub-job fails, the parent job shows FAILED. Other sub-jobs in that parent can still finish. Check each sub-job before you run the action again.
4.3 Job messages
| Message | Where | Meaning |
|---|---|---|
| XenData job processing has started | Parent job | XenData accepted the work |
| XenData job in progress (N%) | Parent job | XenData reports this progress |
| XenData archiving completed successfully | Parent job | The archive is complete |
| XenData restore completed successfully | Parent job | The restore is complete |
| XenData job failed: <reason> | Parent job | XenData or XenData for Iconik reported a failure |
A number, such as 12345 |
Sub-job | The XenData job ID; give it to your XenData administrator when you report a problem |
| Error: <reason> | Sub-job | The reason this asset failed |
4.4 Skip reasons
| Message | Meaning |
|---|---|
| Asset is already archived on storage <id> | The asset already has an archive copy |
| ORIGINAL format file set is on storage <x>, not on target ISG storage (<y>) | The original file is on a different storage than the one in Settings |
| ORIGINAL format file set has no storage ID | Iconik has no storage for the original file |
| Asset is not on archive storage | A restore was requested for an asset that is not archived |
| Asset is already restored to target storage | The asset is already on ISG storage |
| Processing error: <reason> | XenData for Iconik could not read the asset details |
A Processing error is not a normal skip. Check the asset in Iconik and the Logs tab.
4.5 Metadata written to assets
After a successful archive, XenData for Iconik writes two fields to the asset in Iconik.
| Field | Value |
|---|---|
| Xendata Archive Template Version | 2 for archives made by version 2.0 and later |
| XenData Tape ID | The barcode of each tape that holds the asset |
Use XenData Tape ID to find the tape for an asset. Do not edit Xendata Archive Template Version. XenData for Iconik uses it to find the correct restore path.
Iconik also shows the asset's archive copy on the archive storage.
4.6 Local job history
XenData for Iconik keeps its own job records for 7 days. It removes older records each time it starts. Iconik keeps its jobs separately, so this does not change what you see in Iconik.
Previous: Archiving and restoring · Contents · Next: Settings