Abstract: A storage system comprises: a controller; a memory; one or more objects, each object having content data and metadata which includes system metadata; and a policy which governs writing of the content data and metadata of the one or more objects from the storage system to an external storage. The policy includes a configurable criterion for decoupling of the content data and the metadata of a given object and a rule for determining storage locations for the content data and the metadata between the storage system and the external storage in a decoupled manner if the content data and the metadata of the object are decoupled. The configurable criterion is based on an attribute of the metadata of the object. The controller is operable to execute the policy against the objects and to apply the rule to determine storage locations for the content data and metadata of a decoupled object.

Abstract: A method, of managing storage of content of a system in storage units including run units which do not allow spin-down functionality and spin-down units which allow spin-down functionality, comprises: establishing a storage tiering rule which sets a policy indicating what content is eligible to be stored on a run unit and what content is eligible to be stored on a spin-down unit, the storage tiering rule being applicable to at least a group of the contents in the content system to determine stored content eligibility thereof for storage in the storage units and migration between the storage units; and identifying candidates of contents to migrate between the storage units, based on the storage tiering rule, state of the content system, and the stored content eligibility of the at least a group of the contents.

Abstract: A method, of managing storage of content of a system in storage units including run units which do not allow spin-down functionality and spin-down units which allow spin-down functionality, comprises: establishing a storage tiering rule which sets a policy indicating what content is eligible to be stored on a run unit and what content is eligible to be stored on a spin-down unit, the storage tiering rule being applicable to at least a group of the contents in the content system to determine stored content eligibility thereof for storage in the storage units and migration between the storage units; and identifying candidates of contents to migrate between the storage units, based on the storage tiering rule, state of the content system, and the stored content eligibility of the at least a group of the contents.

Abstract: A method, of managing storage of content of a system (400) in storage units (430) including run units which do not allow spin-down functionality and spin-down units which allow spin-down functionality, comprises: establishing a storage tiering rule (702) which sets a policy indicating what content is eligible to be stored on a run unit and what content is eligible to be stored on a spin-down unit, the storage tiering rule being applicable to at least a group of the contents in the content system to determine stored content eligibility thereof for storage in the storage units and migration between the storage units; and identifying candidates of contents to migrate between the storage units (706), based on the storage tiering rule, state of the content system, and the stored content eligibility of the at least a group of the contents.

Abstract: A storage system comprises: a controller; a memory; one or more objects, each object having content data and metadata which includes system metadata; and a policy which governs writing of the content data and metadata of the one or more objects from the storage system to an external storage. The policy includes a configurable criterion for decoupling of the content data and the metadata of a given object and a rule for determining storage locations for the content data and the metadata between the storage system and the external storage in a decoupled manner if the content data and the metadata of the object are decoupled. The configurable criterion is based on an attribute of the metadata of the object. The controller is operable to execute the policy against the objects and to apply the rule to determine storage locations for the content data and metadata of a decoupled object.

Abstract: A method, of managing storage of content of a system (400) in storage units (430) including run units which do not allow spin-down functionality and spin-down units which allow spin-down functionality, comprises: establishing a storage tiering rule (702) which sets a policy indicating what content is eligible to be stored on a run unit and what content is eligible to be stored on a spin-down unit, the storage tiering rule being applicable to at least a group of the contents in the content system to determine stored content eligibility thereof for storage in the storage units and migration between the storage units; and identifying candidates of contents to migrate between the storage units (706), based on the storage tiering rule, state of the content system, and the stored content eligibility of the at least a group of the contents.

Abstract: Archive management is enhanced by logically partitioning a physical cluster. Using an interface, an administrator defines “tenants” within the cluster. A namespace is a logical partition of the cluster for a collection of objects. Each namespace has a private file system. This approach enables a user to segregate cluster data into logical partitions. Using the interface, a namespace for a tenant is configured without affecting a configuration of another namespace. One configuration option is “versioning,” by which an administrator can elect to enable multiple versions of a same data object to be stored in association with a namespace. Once versioning is enabled for a namespace, the administrator can set a configuration parameter identifying a time period for maintaining a version. Preferably, versioning is dasabled for a data object under retention.

Abstract: A content platform (or “cluster”) that comprises a redundant array of independent nodes is logically partitioned. Using a web-based interface, an administrator defines one or more “tenants” within the cluster, wherein a tenant has a set of attributes: namespaces, administrative accounts, data access accounts, and a permission mask. A namespace is a logical partition of the cluster that serves as a collection of objects typically associated with at least one defined application. Each namespace has a private file system with respect to other namespaces. This approach enables a user to segregate cluster data into logical partitions. Using the administrative interface, a namespace associated with a given tenant is selectively configured without affecting a configuration of at least one other namespace in the set of namespaces. One configuration option is a “disposition service” that, once enabled for a namespace, automatically deletes objects that were once under retention and whose retention time has expired.

Abstract: A content platform (or “cluster”) that comprises a redundant array of independent nodes is logically partitioned. Using a web-based interface, an administrator defines one or more “tenants” within the cluster, wherein a tenant has a set of attributes: namespaces, administrative accounts, data access accounts, and a permission mask. A namespace is a logical partition of the cluster that serves as a collection of objects typically associated with at least one defined application. Each namespace has a private file system with respect to other namespaces. This approach enables a user to segregate cluster data into logical partitions. Using the administrative interface, a namespace associated with a given tenant is selectively configured without affecting a configuration of at least one other namespace in the set of namespaces. One configuration option is a “disposition service” that, once enabled for a namespace, automatically deletes objects that were once under retention and whose retention time has expired.

Abstract: Archive cluster management is enhanced by logically partitioning a physical cluster that comprises a redundant array of independent nodes. Using a web-based interface, an administrator defines one or more “tenants” within the archive cluster, wherein a tenant has a set of attributes: namespaces, administrative accounts, data access accounts, and a permission mask. A namespace is a logical partition of the cluster that serves as a collection of objects typically associated with at least one defined application. Each namespace has a private file system with respect to other namespaces. This approach enables a user to segregate cluster data into logical partitions. Using the administrative interface, a namespace associated with a given tenant is selectively configured without affecting a configuration of at least one other namespace in the set of namespaces.