Nodeum Docs
HomepageBlog
  • ✨What is Nodeum?
    • Data Management Software
  • 👣GETTING STARTED
    • Step by Step
  • 🏨ARCHITECTURE
    • Standalone
    • High Availability
    • Fully Scalable & Resilience
  • Install and Deploy Nodeum
    • Platform Support
    • Nodeum v1
      • Ansible based installation
    • Nodeum v2 - Data Mover
      • Ansible based Installation
        • Customize your Installation
      • Docker Based Deployment
    • SLURM Integration
    • Software License Application
  • Interfaces
    • ND Client
    • Console
      • Manual for Administrator
        • Login
        • Dashboard & Reports
        • Catalog
        • Data Mover Management
        • Advanced Task Management
        • Data Container
        • Primary Storage Configuration
        • Pool Management
        • TCO Calculator
        • Toolbox
        • System Settings
          • Information
          • Configuration
          • Date & Time
          • Backup
          • Services
          • Hostname and DNS Configuration
          • NAS Storage Configuration
          • Object Storage Configuration
          • Tape Library Configuration
          • User Management
          • Audits
      • Manual for End User
    • For Developers
      • RESTful API
      • Configuration through RestAPI Console
      • Software Developement Kits (SDK)
      • Nodeum API
        • API Terms of Use
        • release v1.x
        • release v2.x
  • DATA MOVER
    • Policy-Based Task orchestration
      • Pool Management
      • Scheduler
      • Data Integrity
      • Priority Management
      • Filtering (Basic or Advanced)
      • Hook service (callback)
    • Content traceability
    • Metadata Management
  • IDENTITY MANAGEMENT
    • Right - Authentication & Authorization
    • LDAP Plugin for JWT Token
  • Container Configuration
    • Prerequisites
    • About Container
    • Authorization and Authentication
    • Access your Container
  • HYBRID STORAGE MANAGEMENT
    • File System Managment
    • Object Storage Management
      • Customize your S3 connection
    • Tape Library Management
      • Tape Writing Format : LTFS
      • Tape Compression
      • Tape Rehydratation
      • Import a LTFS Tape
      • Task Maintenance for Tapes
  • ⏰Alert & Monitoring
    • Alerts
    • Monitoring
    • Log Management
  • 🏥Recover after Hardware Failure
    • Failover - Active/Passive
    • Failover Procedure - One Site
    • Backup & Restore
  • 🔐Security Guide
    • Advanced Network Configuration
    • Add a SSL Certificate on Web Console
    • Enable SSL Certificate Container accessible on S3 Protocol
  • Compatibility guide
    • Software requirement
    • Supported Storage
  • PRODUCT SPECIFICATIONS
    • Character Set Support
    • Limitations
    • Files Status
    • Task Status
Powered by GitBook
On this page

Was this helpful?

  1. HYBRID STORAGE MANAGEMENT
  2. Tape Library Management

Tape Compression

Due to tape compression capabilities, volume size on tape can be different to the volume size of data ingested.

Last updated 1 year ago

Was this helpful?

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.