LYNIO
← Terug naar alle documentatie
StorageDoor LYNIO Support

Object Storage Auto-Tiering & Lifecycle Management

Data access patterns naturally change over time. When files are freshly uploaded, they are frequently accessed and modified. After 30 to 90 days, access drops significantly, yet the data must remain durable and accessible for compliance, auditing, or disaster recovery.

LYNIO Object Storage features an automated Auto-Tiering Lifecycle Engine that optimizes storage costs without requiring administrative intervention or changing application endpoints.

Storage Classes Explained

Every object in LYNIO Object Storage resides in one of two storage classes:

Storage TierBackend TechnologyBest ForRelative Cost
STANDARD (Hot Pool)High-Performance Active Storage PoolActive application workloads, web assets, active database backupsBaseline (~€0.0219/GB/mo)
ARCHIVE (Cold Pool)Deduplicated & Compressed High-Density PoolRegulatory archives, historical versions, compliance records75% discount (€0.0051/GB/mo)

How Auto-Tiering Works

When Auto-Tiering is enabled on a bucket:

  1. Activity Tracking: The storage gateway monitors the access time of every object. Read operations (GET requests) update the object's last_accessed_at metadata timestamp. Metadata inspection (HEAD requests) does not reset the timer.
  2. Scheduled Background Scanning: A lightweight lifecycle daemon continuously scans the filesystem on the storage nodes.
  3. Automatic Demotion: Any object whose inactivity exceeds the bucket's configured inactivity threshold (default: 30 days) is atomically moved from the standard storage pool to the archive pool.
  4. Historical Version Migration: The auto-tiering engine is version-aware. When an object is demoted, or when historical versions in .versions/ exceed the inactivity threshold, the previous versions are also migrated to the archive pool to eliminate unnecessary active storage spend.

Seamless Rehydration on Read

Unlike traditional cold archives that require hours of delayed batch retrieval, LYNIO provides zero-touch instant streaming:

  • Instant First-Byte Delivery: When an application or user requests a GET operation on an ARCHIVE object, the gateway streams the data immediately over HTTP with zero wait time.
  • Background Rehydration: Simultaneously, the gateway enqueues a background promotion job that moves the object back to the STANDARD Hot tier.
  • No Code Changes: Client applications do not need to call specialized restore APIs. The rehydration happens transparently at the protocol level.

Versioning & Retention Policies

In addition to tiering, buckets support automated Version Retention Rules:

  • Version Retention Days: When versioning is active, previous revisions are kept for a user-specified retention window (e.g., 30, 60, or 90 days).
  • Automatic Pruning: Historical versions that exceed the retention period are permanently removed by the gateway's background pruner, preventing runaway storage growth from repeated overwrite operations.
  • Non-Current Version Transitions: If you want to keep non-current versions indefinitely but avoid paying for active hot storage, combining Versioning with Auto-Tiering ensures old versions are stored at Cold Pool archive pricing.

Configuring Auto-Tiering in the Console

To configure lifecycle rules on an existing bucket:

  1. Go to Storage > Object Storage.
  2. Click the Options menu (...) on your bucket and select Settings.
  3. Toggle Auto-Tiering:
    • Switch the toggle to Enabled.
    • Specify the Inactivity Threshold (e.g., 30 days).
  4. Configure Versioning & Retention:
    • Enable Object Versioning.
    • Specify the Version Retention Days (e.g., 30 days).
  5. Click Save Changes.

The lifecycle engine will automatically pick up the new configuration on its next scheduled scan cycle.