Hitachi Data Systems Corporation

Matthew Michael McDonald

Benjamin Isherwood

David B Pinkney

Richard Rogers

Donald P Pannese

Christopher S Lacasse

Vitaly Zolotusky

Jack A Orenstein

David P Pinkney

A redundant array of independent nodes are networked together. Each node executes an instance of an application that provides object-based storage. The nodes are grouped into a plurality of systems each having multiple nodes. A data protection level method comprises setting a numerical value of a system dynamic data protection level for each system of nodes; and in response to user input, setting a value of a data protection level for one or more data objects in a system, the value being a fixed numerical value or a dynamic value. If the one or more data objects have a dynamic value of the data protection level in a system, the one or more data objects inherit the system dynamic data protection level of the system in which the one or more data objects reside. The value of the data protection level represents a number of copies of data of the one or more data objects to be kept where the one or more data objects reside.

System and method for optimizing protection levels when replicating data in an object storage system

A content platform cluster that comprises an array of nodes is logically partitioned. Using a web-based interface, an administrator defines '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. Tenant information, including all associated namespaces, in the cluster (the 'source cluster') is replicated to at least one target cluster over a replication link. Preferably, replication is available for multiple tenants in the source cluster, and a replication algorithm ensures that a particular tenant can be added to the replication link without stalling the progress of other tenants.

Fixed content storage within a partitioned content platform, with replication

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.

Fixed content storage within a partitioned content platform using namespaces, with versioning

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 &#x201c;disposition service&#x201d; that, once enabled for a namespace, automatically deletes objects that were once under retention and whose retention time has expired. Preferably, the disposition service deletes objects that do not have a &#x201c;retention hold&#x201d; associated therewith. The service enables the content platform to automatically reclaim cluster capacity while minimizing external involvement and archive load.

Fixed content storage within a partitioned content platform, with disposition service

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. According to this disclosure, tenant information, including all associated namespaces, in the cluster (the &#x201c;source cluster&#x201d;) is replicated to at least one target cluster over a replication link. Preferably, replication is available for multiple tenants in the source cluster, and a replication algorithm ensures that a particular tenant can be added to the replication link without stalling the progress of other tenants.

Growing community of inventors

Quincy, MA, United States of America

Matthew Michael McDonald