File lifetime tracking for cloud-based object stores

Patent metadata

Field	Value
Publication number	US-12056105-B2
Application number	US-202218091766-A
Country	US
Kind code	B2
Filing date	Dec 30, 2022
Priority date	Sep 17, 2020
Publication date	Aug 6, 2024
Grant date	Aug 6, 2024

Abstract

Tracking changes to a document by defining a document record having a unique document record and comprising an index and a file name of the document, and defining a backup record for the document in a series of backups, which includes a timestamp for each backup, and a bitmask for the document. The bitmask has a single bit position for each document in the container which is set to a first binary value to indicate that the corresponding document is unchanged and a second binary value to indicate whether the document is changed or deleted. A primary query is received and resolved for the document by analyzing the document record to find the file name. A secondary query using the document record ID is resolved to find all tracked versions of the document, and the results are returned to the user in the form of a version history list.

First claim

What is claimed is:

1. A method of tracking version history of a stored document comprising:
storing documents in a container along with selected metadata;
creating a Document Record for each document and including a unique document ID for each respective document and a Container Record for the document;
receiving a primary query from a user to return all versions of the document, the primary query including a specified filename;
searching the Document Record to find a filename match for the primary query;
returning a list of all matching documents for the specified filename with a number of versions for each matching document;
receiving a secondary query from the user specifying a particular document from the list of all matching documents; and
returning a list of all versions of the specified particular document in response to the second query, and wherein a response to the primary query returns a list of all documents having the filename and a number of versions for the document.

2. The method of claim 1 further comprising specifying a creation and deletion time of the document in at least one of the primary or secondary query.

3. The method of claim 1 wherein the tracked versions of the document are generated by at least one of a document modification, movement, or renaming.

4. The method of claim 1 wherein the filename specified in the primary query comprises a partial filename, and wherein the filename comprises a directory path name including the filename and a present storage location of the document, as defined by a file system or operating system.

5. The method of claim 4 wherein the results are displayed to the user in a list in which the tracked versions are indexed within containers by a time of document modification, movement or renaming.

6. The method of claim 1 wherein the document record comprises one of: a unique document record ID (DRid) specifying a version, path and filename of a respective document, a container ID of the container, a start date indicating document creation time, an end date specifying a last date the version of the document existed in the path, an index, or a hash value of the document.

7. The method of claim 1 wherein the stored document comprises a document created by a cloud-based application program, and is stored in an object store.

8. A non-transitory computer program product storing executable program instructions, which when executed by a processor, execute a method of tracking version history of a document comprising:
storing documents in a container of a plurality of containers along with selected metadata;
creating a Document Record for each document and including a unique document ID for each respective document and a Container Record for the document;
receiving a primary query from a user to return all versions of the document, the primary query including a specified filename;
searching the Document Record to find a filename match for the primary query;
returning a list of all matching documents for the specified filename with a number of versions for each matching document;
receiving a secondary query from the user specifying a particular document from the list of all matching documents; and
returning a list of all versions of the specified particular document in response to the second query, and wherein a response to the primary query returns a list of all documents having the filename and a number of versions for the document.

9. The non-transitory computer program product of claim 8 wherein tracked versions of the document are generated by at least one of a document modification, movement, or renaming, and wherein the filename specified in the primary query comprises a partial filename, and wherein the filename comprises a directory path name including the filename and a present storage location of the document, as defined by a file system or operating system.

10. The non-transitory computer program product of claim 9 wherein the-results are displayed to the user in a list in which the tracked versions are indexed by a time of document modification, movement or renaming.

11. The non-transitory computer program product of claim 10 wherein the document record comprises one of: a unique document record ID (DRid) specifying a version,-path and filename of a respective document, a container ID of the container, a start date indicating document creation time, an end date specifying a last date the version of the document existed in the path, an index, or a hash value of the document.

12. The non-transitory computer program product of claim 8 wherein the stored document comprises a document created by a cloud-based application program, and is stored in an object store.

13. The non-transitory computer program product of claim 8 wherein a creation and deletion time of the document is specified in at least one of the primary or secondary query.

Assignees

• Emc Ip Holding Co Llc

Inventors

• Malamut Mark
• Brenner Adam
• Murti Arun

Classifications

• G06F9/30038

  using a mask · CPC title

• G06F9/30018

  Bit or string instructions · CPC title

• G06F16/2255

  Hash tables · CPC title

• G06F16/38

  Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title

• G06F16/289

  Object oriented databases · CPC title