Groups of storage media, magnetic HDDs or flash SSDs / NVMe, can be configured to isolate particular traffic or objects from others. Data can be moved from one pool to another with simple operations or through automated tasks, enabling automated tiering.
Groups of storage media, magnetic HDDs or flash SSDs / NVMe, can be configured to isolate particular traffic or objects from others. Data can be moved from one pool to another with simple operations or through automated tasks, enabling automated tiering.
Data can be automatically moved across different storage pools thanks to an elaborate lifecycle management rules system (based on metadata, size, tags, prefixes, ect). This simplifies data movements in the system, leaving faster resources ready for new hot data.
Data can be compressed synchronously or asynchronously to select the best tradeoff among data footprint reduction, i/o ops optimization, and CPU consumption.
Time-based policies can be set to compress data that has not been read for some time, improving space efficiency and $/GB for cold data.
OpenIO supports S3 object life-cycle management, allowing end users to set up time-based rules and trigger actions accordingly.
Automations can be set to move, compress, delete data by age, last modified date and many other characteristics, improving system efficiency and data placement for best performance and capacity utilization.
Container snapshots enable to make quick copies of entire containers for backup, to create data sets for big data analytics or test applications. That speeds up backup operations and offloads large data copies to the storage backend.
Write Once Read Many can be enabled on containers, disabling the ability to modify or delete objects. It allows to keep data safe from deletion and comply to regulations that need this requirement.
