Method of tracking and analyzing data integrity issues by leveraging cloud services

1. A method, comprising:

receiving, by a data integrity check entity, a request from a data protection entity to perform a data integrity check with respect to a backup dataset, and the backup dataset comprises a backup of an entity other than the data integrity check entity and the data protection entity;

accessing, by the data integrity check entity, an information set created by the data protection entity concerning the backup dataset;

performing, by the data integrity check entity, a data integrity check process that comprises analyzing the backup dataset and information contained in the information set and, based on the analyzing, identifying a data integrity problem that resulted from a data corruption event involving the backup dataset, and as between the data integrity check entity and the data protection entity, only the data integrity check entity checks the integrity of data in the backup dataset; and

reporting, by the data integrity check entity, results of the analysis of the backup dataset and the information set.

2. The method as recited in claim 1 , wherein the data integrity check performed by the data integrity check entity is a read-only process.

3. The method as recited in claim 1 , wherein the information set includes any one or more of checksum information, time stamp, logical block addressing (LBA) range or information identifying a data offset within an object, identity of an application that created data included in the backup dataset, and application specific data.

4. The method as recited in claim 1 , wherein the analyzing comprises performing a checksum process with respect to information in the information set and/or data included in the backup dataset.

5. The method as recited in claim 1 , wherein the data integrity check is performed by the data integrity check entity on a per-object basis.

6. The method as recited in claim 1 , wherein the data integrity check entity obtains a data access credential from the data protection entity as a prerequisite to performing the data integrity check.

7. The method as recited in claim 1 , wherein the data integrity check entity communicates with the data protection entity by way of an RPC or RESTful API.

8. The method as recited in claim 1 , wherein a data path used by the data integrity check entity is separate from a data path associated with a backup process of the data protection entity.

9. The method as recited in claim 1 , further comprising bringing up, by the data integrity check entity, a shadow file system, and the data integrity check is performed at a file system level.

10. The method as recited in claim 1 , wherein the data protection entity is a data protection VM and/or the data integrity check entity is a data integrity check VM.

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

receiving, by a data integrity check entity, a request from a data protection entity to perform a data integrity check with respect to a backup dataset, and the backup dataset comprises a backup of an entity other than the data integrity check entity and the data protection entity;

accessing, by the data integrity check entity, an information set created by the data protection entity concerning the backup dataset;

performing, by the data integrity check entity, a data integrity check process that comprises analyzing the backup dataset and information contained in the information set and, based on the analyzing, identifying a data integrity problem that resulted from a data corruption event involving the backup dataset, and as between the data integrity check entity and the data protection entity, only the data integrity check entity checks the integrity of data in the backup dataset; and

reporting, by the data integrity check entity, results of the analysis of the backup dataset and the information set.

12. The non-transitory storage medium as recited in claim 11 , wherein the data integrity check performed by the data integrity check entity is a read-only process.

13. The non-transitory storage medium as recited in claim 11 , wherein the information set includes any one or more of checksum information, time stamp, logical block addressing (LBA) range or information identifying a data offset within an object, identity of an application that created data included in the backup dataset, and application specific data.

14. The non-transitory storage medium as recited in claim 11 , wherein the analyzing comprises performing a checksum process with respect to information in the information set and/or data included in the backup dataset.

15. The non-transitory storage medium as recited in claim 11 , wherein the data integrity check is performed by the data integrity check entity on a per-object basis.

16. The non-transitory storage medium as recited in claim 11 , wherein the data integrity check entity obtains a data access credential from the data protection entity as a prerequisite to performing the data integrity check.

17. The non-transitory storage medium as recited in claim 11 , wherein the data integrity check entity communicates with the data protection entity by way of an RPC or RESTful API.

18. The non-transitory storage medium as recited in claim 11 , wherein a data path used by the data integrity check entity is separate from a data path associated with a backup process of the data protection entity.

19. The non-transitory storage medium as recited in claim 11 , further comprising bringing up, by the data integrity check entity, a shadow file system, and the data integrity check is performed at a file system level.

20. The non-transitory storage medium as recited in claim 11 , wherein the data protection entity is a data protection VM and/or the data integrity check entity is a data integrity check VM.