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
  • Handle multiple copies to tape
  • Get tape offsite
  • Multiple tape copies

Was this helpful?

  1. Interfaces
  2. Console
  3. Manual for Administrator

Advanced Task Management

Utilize Task Management for various scenarios by configuring it to meet your specific needs. Here are a few potential setups for achieving your goals.

Handle multiple copies to tape

Get tape offsite

Implement workflow to get a set of tape offsite.

We recommend to define the two following workflows:

  • Two tasks to perform the two copies on tape for the same dataset. The execution of two different tasks has the benefit to avoid a 'y' copy ; and perform two independent read/write operations.

  • In addition, on the of the copy can be externalized ; this bring the benefit to get an offline copy of the contents and eventually yield this copy to a third party location.

Multiple tape copies

Implement specific workflow and deal with multiple tape copies

First scenario

Define two different workflows for data protection. This will ensure that the two copies are separate and that if one is damaged, the other will not be.

Specify a different "offline archive" pool for each workflow and associate tapes with each pool or let Nodeum retrieve tapes from the scratch pool.

For the 2 workflows: Select a primary storage: S3 or NAS as a source and select a tape pool as destination.

Second scenario

If your contents are in a container. You can protect your container on tapes too.

For this, you have to create a data protection workflow to copy the container data to a pool "offline archive" and associate tapes for each pool or let Nodeum get tapes from the Scratch pool.

The setting for this workflow is Select data protection from source (container) to destination (tape). Dedicate an "Offline Archive" pool for each workflow and associate a set of tapes to each pool or let Nodeum automatically retrieve tapes from the Scratch pool.

Then you define a second workflow "Data Archiving" to archive the data of your Container to an Active Archive Pool of tapes. The contents will remain accessible from the Container even if the contents are stored in a pool of tape(s).

The setting for this workflow is Select Data Archiving from Source (Container) to Destination (Tape). Dedicate a pool "active archive" for each workflow and associate for a set of tapes in each pool or let Nodeum automatically retrieve tapes from the Scratch pool.

Last updated 3 months ago

Was this helpful?