> For the complete documentation index, see [llms.txt](https://docs.nodeum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodeum.io/data-archiving/hybrid-storage-management/tape-library-management/tape-compression.md).
# Tape Compression
Due to tape compression capabilities, volume size on tape can be different to the volume size of data ingested.
After a workflow execution, you can see a difference between the volume size of what is stored on tape and the capacity processed by the workflow.
The reason is that the Tape Drive has compression capabilities ; and this hardware compression process can be significant. The hardware compression is much faster than software compression, it is transparent to the operating system, and data is compressed “on the fly”.
Usually, the compression ratio for magnetic tape drives is maximum 2:1. In fact, the compression ratio of 2:1 may be really equal to **1.2:1** or **1.6:1.** That depends on the type of data that you are writing onto tape. If the data are already compressed or not.
To know more about the level of compression of your tapes, you can check if the tape drive compression setting is activated. You can also see the compression status of each tape, for that, you can access the Nodeum Tape reporting to see the level of compression of each media:
If you want to verify if each file has been well copied to tape; we recommend to activate the Checksum Integrity verification during the workflow execution.
Nodeum supports the two main algorithms: md5-hash and xxhash-64be.
And then you have also the option to compare each checksum and then validate if all files have been well copied on the tape.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nodeum.io/data-archiving/hybrid-storage-management/tape-library-management/tape-compression.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
