Content indexed integrated copy data by integrating elastic search and storage system snapshot differential data

1. A non-transitory storage medium having stored therein instructions which are executable by one or more hardware processors to perform operations comprising:

creating a copy of a dataset, wherein the dataset comprises data generated by one or more applications at a host device;

mounting the entire copy at a proxy host;

after the copy is mounted at the proxy host, creating an index by indexing the entire mounted copy;

associating the index with a portion of data in the copy by creating a reference object between the index and the portion of data;

storing the index;

storing the reference object with either the index or the copy;

obtaining a data differential between the copy and a subsequent copy created after the copy, the data differential identifying one or more changed blocks that have changed between the copy and the subsequent copy;

mapping the data differential to an affected database region and/or file system volume, and the mapping comprises a reverse mapping process comprising using respective IDs of the changed blocks to identify a portion of the index affected by changes associated with the changed blocks, and the respective IDs are obtained from a storage array at which the dataset is stored; and

updating the index to map to the changed blocks.

2. The non-transitory storage medium as recited in claim 1 , wherein the dataset that is copied is a deduplicated dataset.

3. The non-transitory storage medium as recited in claim 1 , wherein the copy is one of: an incremental backup; a snapshot; a full backup; a partial backup; or, a clone.

4. The non-transitory storage medium as recited in claim 1 , wherein the reference object comprises the information ‘path+copy data identifier’.

5. The non-transitory storage medium as recited in claim 1 , wherein updating the index is performed with respect only to regions of a database that include one or more of the changed blocks.

6. The non-transitory storage medium as recited in claim 1 , wherein except for mounting of the copy at a proxy host, the operations are performed at a storage array.

7. The non-transitory storage medium as recited in claim 1 , wherein creation of the copy is based on a Recovery Time Objective (RTO) and/or a Recover Point Objective (RPO).

8. The non-transitory storage medium as recited in claim 1 , wherein the operations further comprise:

in response to a user query specifying the portion of data, using the index and the reference object to identify, in the copy and/or the subsequent copy, a copy data grouping that includes the portion of data;

creating a list that includes the copy data grouping;

presenting the list to the user;

receiving an indication of a user selection of the copy data grouping; and

providing, to a host, the copy data grouping selected by the user.

9. The non-transitory storage medium as recited in claim 1 , wherein the data differential indicates that some data in the copy has been deleted in the subsequent copy, and the operations further comprise marking, for deletion, an index that refers to copy data volumes that held the deleted data.

10. A method, comprising:

creating a copy of a dataset, wherein the dataset comprises data generated by one or more applications at a host device;

mounting the entire copy at a proxy host;

after the copy is mounted at the proxy host, creating an index by indexing the entire mounted copy;

associating the index with a portion of data in the copy by creating a reference object between the index and the portion of data;

storing the index;

storing the reference object with either the index or the copy;

obtaining a data differential between the copy and a subsequent copy created after the copy, the data differential identifying one or more changed blocks that have changed between the copy and the subsequent copy;

mapping the data differential to an affected database region and/or file system volume, and the mapping comprises a reverse mapping process comprising using respective IDs of the changed blocks to identify a portion of the index affected by changes associated with the changed blocks, and the respective IDs are obtained from a storage array at which the dataset is stored; and

updating the index to map to the changed blocks.

11. The method as recited in claim 10 , wherein the dataset that is copied is a deduplicated dataset.

12. The method as recited in claim 10 , further comprising:

in response to a user query specifying the portion of data, using the index and the reference object to identify, in the copy and/or the subsequent copy, a copy data grouping that includes the portion of data;

creating a list that includes the copy data grouping;

presenting the list to the user;

receiving an indication of a user selection of the copy data grouping; and

providing, to a host, the copy data grouping selected by the user.

13. The method as recited in claim 10 , wherein the data differential indicates that some data in the copy has been deleted in the subsequent copy, and the method further comprises marking, for deletion, an index that refers to copy data volumes that held the deleted data.

14. The method as recited in claim 10 , wherein the copy is one of: an incremental backup; a snapshot; a full backup; a partial backup; or, a clone.

15. The method as recited in claim 10 , wherein the reference object comprises the information ‘path+copy data identifier’.

16. The method as recited in claim 10 , wherein indexing is performed by an elastic search indexing tool.

17. The method as recited in claim 10 , wherein updating the index is performed with respect only to regions of a database that include one or more of the changed blocks.

18. The method as recited in claim 10 , wherein except for mounting of the copy at a proxy host, the method is performed at a storage array.

19. The method as recited in claim 10 , wherein creation of the copy is based on a Recovery Time Objective (RTO) and/or a Recover Point Objective (RPO).