# Content traceability

<mark style="color:purple;">**Archiving with Nodeum**</mark>

**Traceability**

Digital archiving requires adherence to strict procedures for scanning, indexing, and storing documents securely and systematically. Nodeum provides comprehensive workflow solutions covering these key aspects.

**Secure Storage & Accessibility**

* **Indexing and Secure Storage**: Digital documents are indexed and stored securely, maintaining the original format to prevent unauthorized alterations.
* **Integrity Checks**: Optional integrity checks can be applied during the archiving process to ensure document authenticity.

**Foolproof Archiving**

* **Metadata Attachment**: Attach metadata to files for controlled and secure lifecycle management.
* **Read-Only Storage**: Archive contents onto read-only storage for additional protection.

**Document Access**

* **Monitoring and Audit Trails**: All operations are monitored, with comprehensive audit trails available.
* **Workflow Reporting**: Nodeum provides detailed reports on archiving workflows and integrity checks.

## Audit Trails for Tasks

Audit trails are critical for tracking the history and accountability of tasks. They record actions taken, by whom, and when they occurred, ensuring transparency and assisting in troubleshooting and compliance.

#### Key Benefits

* **Accountability**: Provides a clear record of who performed actions.
* **Transparency**: Enhances visibility into task progression.
* **Efficiency**: Aids in quickly identifying issues or bottlenecks.

#### Implementation Tips

* Use robust logging systems to capture detailed actions.
* Regularly review audit logs to ensure task integrity.
* Ensure compliance with any relevant regulations or standards.

Incorporating audit trails into task management can improve overall process control and reliability.

### Task Status

Each task concludes with a status, which indicates the processing outcome. Refer to the table below for descriptions of each status type.

| Status              | Definition                                                   | Action to do                                                                                                |
| ------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- |
| Done                | Task is finished with success                                | N/A                                                                                                         |
| Stop by User        | Task is stopped by a user prior to the end                   | N/A                                                                                                         |
| Finish with Warning | Task is finished but some files were not processed correctly | Review the processed files to better understand the root cause of this problem and why the message appears. |
| Stop by System      | The task is stopped by the System                            | Understand why the system stopped the task; going into the task’s log will provide the required details.    |
| Error               | The task is stopped anomaly                                  | Understand why an error occurs; going into the system log will provide the required details.                |

#### Root cause of "Stop by System" status

Below is a list of logs accessible following a system shutdown:

<table><thead><tr><th width="290.3333333333333">Log</th><th width="275">Definition</th><th>Action</th></tr></thead><tbody><tr><td>Drive %s is in Maintenance Mode. Set it Online to Start the Execution of this Task</td><td>Drive N°xx is on maintenance</td><td>Select another drive to run the task</td></tr><tr><td>Error during allocation of a scratch tape to the pool</td><td>impossible to get a tape from de scratch pool</td><td>Check if tape are in the scratch pool</td></tr><tr><td>File is not copied on any Tape on this pool</td><td>When we will reload a file and the files doesn't exist on a tape in the pool choosen</td><td></td></tr><tr><td>Invalid cloud pool</td><td>Cloud pool doesn't exist</td><td>create the cloud pool before to run the task</td></tr><tr><td>Invalid Destination or Task destination is invalid</td><td>The destination choosen doesn't exist or the connection failed</td><td>Check if the destination exist</td></tr><tr><td>Invalid NAS pool</td><td>NAS pool doesn't exist</td><td>create the NAS pool before to run the task</td></tr><tr><td>Invalid Pool</td><td>Pool choosen doesn't exist</td><td>Check if the pool exist. If not create it</td></tr><tr><td>Pool does not have a valid tape and scratch pool is empty</td><td>No tape is in the pool and no tape in scratch pool</td><td>Insert a tape in the pool. Don't forget to format it before to run the task</td></tr><tr><td>Pool does not have a valid tape and unable to get a scratch volume for this task</td><td>No tape is in the pool and impossible to get a tape in scratch pool</td><td>Insert a tape in the pool. Don't forget to format it before to run the task</td></tr><tr><td>Tape %s is not in the library</td><td>Tape Nbre xx is not in the tape library</td><td>Put the tape in the library</td></tr><tr><td>Tape destination is invalid</td><td>barcode doesn't exist. The tape haven't mount and is out of tape library</td><td></td></tr><tr><td>Tape pool destination is invalid</td><td>tape pool doesn't exist</td><td>create the tape pool before to run the task</td></tr></tbody></table>

### Files Status

<table><thead><tr><th width="164.33333333333331">Status</th><th width="307">Definition</th><th>Actions</th></tr></thead><tbody><tr><td>EACCESS</td><td>Permission Denied on File (in Source or Destination).</td><td>Check the privilege.</td></tr><tr><td>EINVAL</td><td>Invalid Argument. The device is not managed, or the device is not well configured.</td><td>Check the Configuration.</td></tr><tr><td>ENOSPC</td><td>Not enough space on the device.</td><td>Move Data from Cache to Secondary Storage</td></tr><tr><td>EROFS</td><td>The problem of writing in the file system.</td><td>Perhaps the file system is in Read-Only</td></tr><tr><td>FAILED</td><td><p>Some special characters in the name of the file could block the process of this file.</p><p>The number of characters (in the file's name) is too long.</p></td><td><p>Rename the file with appropriated character(s) and restart the task.</p><p>Check in the Primary Storage if the file is available.</p></td></tr><tr><td>FATALERR</td><td>The problem of DB update in the LTFS format.</td><td></td></tr><tr><td>GETCACHERR</td><td>The file is removed from secondary storage.</td><td></td></tr><tr><td>LTFSERR</td><td>LTFS error. Mount LTFS ERROR.</td><td>Make a tape Consistency.</td></tr><tr><td>MLERROR</td><td>Error during a data enrichment.</td><td></td></tr><tr><td>NOTEMPTY</td><td>Impossible to delete a folder empty.</td><td></td></tr><tr><td>NOFILE</td><td><ul><li>File source do not exist.</li><li>File source is not available.</li></ul><p>This situation is due because the file(s) are not on the source or the destination.</p></td><td>Check the connectivity of the Storage</td></tr><tr><td>OFFLINE</td><td><ul><li>Storage is not connected to Nodeum.</li><li>Tape barcode is not readable.</li></ul></td><td><ul><li>Connect the Storage.</li><li>Check the barcode of the tape</li></ul></td></tr><tr><td>OK</td><td>Files copy or move with Success.</td><td></td></tr><tr><td>PARTIAL</td><td>Copy did with success on a part of files</td><td></td></tr><tr><td>TAPEERR</td><td>Tape drive or Tape Library on Error.</td><td>Check if the tape library is ready.</td></tr><tr><td>UPTODATE</td><td>The same file(s) already exist in the destination.</td><td></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nodeum.io/data-archiving/console/data-mover-management/content-traceability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.