Method, system, and program implementing retention policies to archive records

• US 8,281,087 B2
• Filed: 01/07/2009
• Issued: 10/02/2012
• Est. Priority Date: 09/08/2003
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Marek, Toby Lyn, Hochberg, Avishai Haim, Cannon, David Maxwell, Martin, Howard Newton, Stuart, Alan
• Primary Examiner(s): ELMORE, STEPHEN C
• Application Number:
  US12/350,198
• Publication Number:
  US 20090119354A1
• Time in Patent Office: 1,364 Days
• Field of Search: 711/159, 711/160, 711/161, 711/133, 711/134, 711/154, 707/662, 707/666
• US Class Current: 711/159
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/185 Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

Provided are a method, system, and program for receiving a request to remove a record. A determination is made as to whether a state associated with the record includes at least one hold state and whether the state associated with the record includes at least a retention period that has not expired. The request to remove the record is denied in response to determining that the state associated with the record includes at least one of at least one hold state and one retention period that has not expired.

Claims

1. A computer implemented method, comprising:

receiving a request by a computer to remove a record stored in a storage server;

determining whether a state associated with the record includes at least one hold state;

determining whether the state associated with the record includes at least one retention period that has not expired; and

denying the request to remove the record in response to determining that the state associated with the record includes at least one state comprising;

the at least one hold state and/or the at least one retention period that has not expired.

2. The method of claim 1, wherein the at least one hold state includes at least one of an audit state, a legal state, and a permanent hold state, wherein the audit state is applied if the record is involved in an organizational audit, wherein the legal state is applied if the record is involved in a regulatory action, and wherein the permanent hold state applies once specified.

3. The method of claim 1, wherein at least one state capable of being associated with the record includes both the at least one retention period and the at least one hold state.

4. The method of claim 1, further comprising:

determining whether the state associated with the record includes an event state specifying an event condition, wherein the request is denied if the state associated with the record includes the event state whose event condition has not been satisfied.

5. The method of claim 4, wherein at least one state includes at least two of the states comprising:

the event state, the at least one hold state, and the at least one retention period.

6. The method of claim 5, further comprising:

receiving indication that the event condition for the event state associated with the record is satisfied; and

initiating a retention period for the record associated with the event state in response to detecting the satisfaction of the event condition, wherein the record is associated with the at least one state including the retention period in response to satisfying the event condition.

7. The method of claim 1, further comprising:

receiving a request to purge metadata associated with one record;

determining whether the record subject to the requested purge is associated with one state where the record was removed; and

allowing the purging of the metadata if the record subject to the purge is associated with one state where the record was removed.

8. A data storage system in communication with a data storage device, comprising:

a processor;

a computer readable storage medium tangibly embodying code executed by the processor to cause operations to be performed, the operations comprising;

receiving a request to remove one of a plurality of records from the data storage device;

determining whether a state associated with the record includes at least one hold state;

determining whether the state associated with the record includes at least one retention period that has not expired; and

denying the request to remove the record in response to determining that the state associated with the record includes at least one of the states comprising;

the at least one hold state and the at least one retention period that has not expired.

9. The system of claim 8, wherein the at least one hold state includes at least one of an audit state, a legal state, and a permanent hold state, wherein the audit state is applied if the record is involved in an organizational audit, wherein the legal state is applied if the record is involved in a regulatory action, and wherein the permanent hold state applies once specified.

10. The system of claim 8, wherein at least one state capable of being associated with the record includes both the at least one retention period and at least one hold state.

11. The system of claim 8, wherein the operations further comprise:

determining whether the state associated with the record includes an event state specifying an event condition, wherein the request is denied if the state associated with the record includes the event state whose event condition has not been satisfied.

12. The system of claim 11, wherein at least one state includes at least two of the states comprising:

the event state, the at least one hold state, and the at least one retention period.

13. The system of claim 12, wherein the operations further comprise:

receiving indication that the event condition for the event state associated with the record is satisfied; and

initiating a retention period for the record associated with the event state in response to detecting the satisfaction of the event condition, wherein the record is associated with one state including the retention period in response to satisfying the event condition.

14. An article of manufacture comprising a tangible medium tangibly embodying code executable by a computer and in communication with a data storage device to cause operations to be performed by a computer with respect to managing a retention policy with respect to records, the operations comprising:

receiving a request to remove one record from the data storage device;

determining whether a state associated with the record includes at least one hold state;

determining whether the state associated with the record includes at least one retention period that has not expired; and

denying the request to remove the record in response to determining that the state associated with the record includes at least one state comprising;

the at least one hold state and the at least one retention period that has not expired.

15. The article of manufacture of claim 14, wherein the at least one hold state includes at least one of an audit state, a legal state, and a permanent hold state, wherein the audit state is applied if the record is involved in an organizational audit, wherein the legal state is applied if the record is involved in a regulatory action, and wherein the permanent hold state applies once specified.

16. The article of manufacture of claim 14, wherein at least one state capable of being associated with the record includes both the at least one retention period and at least one hold state.

17. The article of manufacture of claim 14, wherein the operations further comprise:

determining whether the state associated with the record includes an event state specifying an event condition, wherein the request is denied if the state associated with the record includes the event state whose event condition has not been satisfied.

18. The article of manufacture of claim 17, wherein at least one state includes at least two states comprising:

the event state, at least one hold state, and the at least one retention period.

19. The article of manufacture of claim 18, wherein the operations further comprise:

receiving indication that the event condition for the event state associated with the record is satisfied; and

initiating a retention period for the record associated with the event state in response to detecting the satisfaction of the event condition, wherein the record is associated with one state including the retention period in response to satisfying the event condition.

20. The article of manufacture of claim 14, wherein the operations further comprise:

receiving a request to purge metadata associated with one record;

determining whether the record subject to the requested purge is associated with one state where the record was removed; and

allowing the purging of the metadata if the record subject to the purge is associated with one state including the removal of the record.