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
  • Standard file attributes
  • Additional metadata
  • File metadata
  • Task metadata

Was this helpful?

  1. DATA MOVER

Metadata Management

Standard file attributes

Nodeum prioritizes the preservation of metadata throughout all data movement operations.

With our metadata mapping feature, you can be confident that your content, no matter its format or location, will seamlessly transition and be effectively managed.

Even if the content locates in different storage system, Nodeum manages natively the transition of the metadata. Data movement capabilities ensure the consistency and reliability of the metadata.

The objective is to ensure that no matter how your data is being transferred, the valuable metadata associated with it remains intact.

For file systems, extended attributes are commonly used, while for S3 compatible storage, metadata management is included in the protocol. The same applies to tape storage, where LTFS specifies how metadata should be handled.

Nodeum keep the traditional "attributes" :

POSIX:

modeMetaKey = "Mode"
uidMetaKey = "Uid"
gidMetaKey = "Gid"
atimeMetaKey = "Atime"
mtimeMetaKey = "Mtime"
ctimeMetaKey = "Ctime"

S3, metadata are set as x-amz-meta-key:

x-amz-meta-mode
x-amz-meta-uid
x-amz-meta-gid
x-amz-meta-atime
x-amz-meta-mtime
x-amz-meta-ctime

Additional metadata

To organize and bring more structure to unstructured data, user needs to add specific business attributes.

These additional metadata created by the users are kept during each data movement. The preservation is full and secure.

Example :

A file mytestextwhich has an extended attribute defined:

root@srv1:~# getfattr mytestext -d
# file: mytestext
user.ship="boat 1"

Nodeum moves the file into a S3 compatible Object Storage, the following metadata will be defined: x-amz-meta-custom-ship=”boat 1”. Additional Metadata are always following the files.

File metadata

Extend the capability to handle additional metadata. The solution enables users to define additional metadata that can be utilized for tagging each file. Furthermore, these additional tags can accelerate the content search process.

Task metadata

Metadata can be set to task to classify and organize the defined tasks. It enables the expansion of tasks by incorporating specific metadata. This additional information is easily accessible within the task management and reporting modules.

You can utilize these metadata to facilitate filtering, searching, and reporting functionalities.

Last updated 1 year ago

Was this helpful?