Data integrity and preservation is designed in.

Allow — Specific rules on what actions are allowed are embedded with each object stored in CAStor. Specify a list of methods at the object level for total behavioral control. New!

Append — Add on new content to existing content. Once content is written it cannot be changed, just appended with the latest version. New!

Copy — Change or add new metadata to an object without affecting the actual object. Change life points to extend retention date, add new tags for search and other content services. New!

Content-MD5 — End-to end integrity checking of all content as it travels over the wire from the client to the storage cluster. New!

Immutability Override — Secured admins can override an Allow header and make an immutable anchor stream mutable. New!

Synchronous Writes. — CAStor now supports synchronous writes to a local and remote cluster. New!

Data Protection

Validate data integrity. Be assured your data remains unchanged. A cryptographic hash is used to establish and continuously validate data integrity, which cannot be compromised due to degradation on disk.

Background integrity checking. Data is continously monitored to assure it is intact, available and protected at all times. CAStor's Health Processor is a background process that is continuously checking data integrity and cardinality (number of replicas) and will automatically heal any degradation or non-conformity. Metadata life point rules are also checks and enforced.

Transmission integrity. Verifies intact object transmission from source to destination. MD5 hash digest of the file can be included in the object header. Ensures that there is no corruption of file data during transmission on the wire enhancing integrity and authenticity features in an archive to meet compliance considerations.

Transparently upgradeable hash. Update your hash protection without impacting your applications. Stay up-to-date with most current hashing algorithms before it becomes compromised. A content integrity seal is created with each hash upgrade to verify authenticity.

Object-level retention. Retain content for a specified period of time to meet regulatory or governance policies. Set retention time on a per object basis and the system will ensure it remains available and unchanged until it expires.

WORM-like storage. CAStor addresses regulatory mandates that content be stored on non-erasable, non-rewriteable media. True to Write-Once-Read-Many (WORM) storage media, once an object is written it cannot be changed or deleted until a predefined retention period has expired.

Lifecycle Management

Life point support. Set the retention, preservation, replication rules for an object and enforce policies at specified times without intervention. Define full lifecycle within the object metadata.

Content integrity seal. CAStor establishes content authenticity for evidentiary purposes by creating and storing content integrity seals. Seals are requested and stored by the application at time of write on a per object basis, computed on the content only not the metadata.

Custom metadata. Applications or admins can define specific metadata elements that describe individual objects and their desired behavior. Custom metadata is stored with the object and can be used to uniquely describe and manage industry or company specific content life cycles.