This news concerns unstructured data management. I wrote about Datadobi several times in 2021 and 2022. Not much since. They have released a new version of their StorageMAP, its “heterogeneous unstructured data management solution.”
StorageMAP 7.3 enables organizations to create policy-driven workflows, act on data more precisely, and migrate between S3-compatible platforms while maintaining compliance.
StorageMAP 7.3 introduces policy-driven workflows that allow administrators to define tasks executed by its workflow engine in response to specific triggers, such as a time schedule. A “dry run” feature facilitates reviewing the scope of a policy before full execution.
These new workflows support a wide range of use cases, including periodic automated archival, creating data pipelines to feed GenAI applications, identifying and relocating non-business-related data to a quarantine area, and more. Once policies are published, StorageMAP runs the workflows on schedule without requiring manual supervision.
In addition, StorageMAP 7.3 adds support for granular file-level deletes. Administrators can identify files that match specific criteria and save them as input to a targeted delete job, which StorageMAP will execute. Each delete job generates a report that documents the job’s details and outcome.
This functionality addresses situations where a coarse-grained directory-level deletion is not possible due to the presence of both relevant and disposable data. By enabling precise file selection, StorageMAP ensures that administrators can apply accurate and effective deletion policies.
Object migration enhancements
StorageMAP 7.3 also enhances its core object migration functionality by supporting the migration of locked objects between S3-compatible storage systems. This allows compliant data stored in a Write Once Read Many (WORM) format to be relocated across different vendor platforms while retaining its retention date and legal holds.
To support cost and performance objectives, the solution includes the ability to select the S3 storage class during object migration or replication. By specifying the desired storage class at the time of the job, organizations can avoid unnecessary post-migration lifecycle policies and ensure data is written directly to the appropriate tier.
