Fixed content storage within a partitioned content platform, with disposition service
First Claim
1. A method of operating a physical archive cluster instance, the cluster instance comprising a redundant array of independent nodes, wherein each node comprises a processor, a data store coupled to the processor, and a local file system, and an application instance stored in the data store and executed by the processor, the method comprising:
- logically partitioning the archive cluster into a set of one or more namespaces, wherein a namespace comprises a collection of data objects;
enabling disposition with respect to a given namespace of the set of one or more namespaces;
for the given namespace, and for a data object under retention, determining whether a retention time associated with the data object has reached a predetermined time; and
if the retention time associated with the data object has reached a predetermined time, automatically deleting the data object from the namespace.
3 Assignments
0 Petitions
Accused Products
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. Preferably, the disposition service deletes objects that do not have a “retention hold” associated therewith. The service enables the content platform to automatically reclaim cluster capacity while minimizing external involvement and archive load.
-
Citations
18 Claims
-
1. A method of operating a physical archive cluster instance, the cluster instance comprising a redundant array of independent nodes, wherein each node comprises a processor, a data store coupled to the processor, and a local file system, and an application instance stored in the data store and executed by the processor, the method comprising:
-
logically partitioning the archive cluster into a set of one or more namespaces, wherein a namespace comprises a collection of data objects; enabling disposition with respect to a given namespace of the set of one or more namespaces; for the given namespace, and for a data object under retention, determining whether a retention time associated with the data object has reached a predetermined time; and if the retention time associated with the data object has reached a predetermined time, automatically deleting the data object from the namespace. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A method of operating a physical archive cluster instance, the cluster instance comprising a redundant array of independent nodes, wherein each node comprises a processor, a data store coupled to the processor, and a local file system, and an application instance stored in the data store and executed by the processor, the method comprising:
-
logically partitioning the archive cluster into a set of namespaces, wherein each namespace of the set of namespaces comprises a set of data objects, and each namespace is managed independently with respect to any other namespace in the set of namespaces; and configuring a disposition service to execute with respect to a given namespace, the disposition service automatically deleting data objects within the given namespace whose retention has expired and that do not have a retention hold parameter associated therewith. - View Dependent Claims (8, 9, 10, 11)
-
-
12. Apparatus for use in a redundant array of independent nodes networked together as an archive cluster, wherein each node executes an instance of an application that provides fixed content-based object storage, comprising:
-
a processor; computer memory holding computer program instructions that, when executed by the processor, perform a method comprising; logically partitioning the archive cluster into a set of one or more namespaces, wherein a namespace comprises a collection of data objects; enabling disposition with respect to a given namespace of the set of one or more namespaces; for the given namespace, and for a data object under retention, determining whether a retention time associated with the data object has reached a predetermined time; and if the retention time associated with the data object has reached a predetermined time, automatically deleting the data object from the namespace. - View Dependent Claims (13, 14, 15, 16, 17, 18)
-
Specification