Event based retention of read only files
Systems and methods are disclosed for implementing an event based retention schedule for a read only file. When a regular file is to be converted to an event based retention read only file, an “event-retain” property may be enabled on the file allowing the feature to be implemented. Then, that file may have its permissions changed to read only. This will allow the file to be changed to a read only file without using a default retention time. Then, once the event is triggered, the retention time may be set so the file can be scheduled for automatic deletion.
1. A method comprising:
transitioning a data structure to a write once read many (WORM) state to create an event-retained data structure comprising a last access time directory field, wherein the data structure is committed to the WORM state prior to a retention end date being stored within the last access time directory field and without triggering a default retention time or setting the retention end date to infinity;
in response to an event occurring, overriding current content of the last access time directory field with the retention end date; and
in response to the retention end date being stored into the last access time directory field, retaining the event-retained data structure for a retention period based upon the retention end date stored within the last access time directory field.
2. The method of claim 1 , comprising:
triggering the override of the last access time directory field based upon the occurrence of the event.
3. The method of claim 1 , comprising:
protecting the event-retained data structure until expiration of the retention end date set based upon a point in time of the event occurring.
4. The method of claim 1 , comprising:
protecting the event-retained data structure from being deleted while no retention end date is stored within the last access time directory field.
5. The method of claim 1 , comprising:
constraining the retention end date based upon a number of bits of the last access time directory field.
6. The method of claim 1 , comprising:
protecting the event-retained data structure from being deleted before the occurrence of the event.
7. The method of claim 1 , comprising:
protecting the event-retained data structure from being deleted before the retention end date is stored into the last access time directory field to overwrite the current content of the last access time directory field.
8. A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to perform operations comprising:
transitioning a data structure to a write once read many (WORM) state to create an event-retained data structure comprising a last access time directory field, wherein the data structure is committed to the WORM state prior to a retention end date being stored within the last access time directory field and without triggering a default retention time or setting the retention end date to infinity;
in response to an event occurring, overriding current content of the last access time directory field with the retention end date; and
in response to the retention end date being stored into the last access time directory field, retaining the event-retained data structure for a retention period based upon the retention end date stored within the last access time directory field.
9. The non-transitory machine readable medium of claim 8 , wherein the operations comprise:
triggering the override of the last access time directory field based upon the occurrence of the event.
10. The non-transitory machine readable medium of claim 8 , wherein the operations comprise:
protecting the event-retained data structure until expiration of the retention end date set based upon a point in time of the event occurring.
11. The non-transitory machine readable medium of claim 8 , wherein the operations comprise:
protecting the event-retained data structure from being deleted while no retention end date is stored within the last access time directory field.
12. The non-transitory machine readable medium of claim 8 , wherein the operations comprise:
constraining the retention end date based upon a number of bits of the last access time directory field.
13. The non-transitory machine readable medium of claim 8 , wherein the operations comprise:
protecting the event-retained data structure from being deleted before the occurrence of the event.
14. The non-transitory machine readable medium of claim 8 , wherein the operations comprise:
protecting the event-retained data structure from being deleted before the retention end date is stored into the last access time directory field to overwrite the current content of the last access time directory field.
15. A computing device comprising:
a memory comprising machine executable code for performing a method; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to perform operations comprising:
transitioning a data structure to a write once read many (WORM) state to create an event-retained data structure comprising a last access time directory field, wherein the data structure is committed to the WORM state prior to a retention end date being stored within the last access time directory field and without triggering a default retention time or setting the retention end date to infinity;
in response to an event occurring, overriding current content of the last access time directory field with the retention end date; and
in response to the retention end date being stored into the last access time directory field, retaining the event-retained data structure for a retention period based upon the retention end date stored within the last access time directory field.
16. The computing device of claim 15 , wherein the operations comprise:
triggering the override of the last access time directory field based upon the occurrence of the event.
17. The computing device of claim 15 , wherein the operations comprise:
protecting the event-retained data structure until expiration of the retention end date set based upon a point in time of the event occurring.
18. The computing device of claim 15 , wherein the operations comprise:
protecting the event-retained data structure from being deleted while no retention end date is stored within the last access time directory field.
19. The computing device of claim 15 , wherein the operations comprise:
constraining the retention end date based upon a number of bits of the last access time directory field.
20. The computing device of claim 15 , wherein the operations comprise:
protecting the event-retained data structure from being deleted before the occurrence of the event.