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

1. A method, comprising:

detecting, by a data protection entity, the occurrence of a data corruption event regarding a backup dataset created by the data protection entity;

transmitting by the data protection entity, to a data integrity check entity, a request to perform a data integrity check with respect to the backup dataset, and the backup dataset comprises a backup of an entity other than the data integrity check entity and the data protection entity, and as between the data protection entity and the data integrity check entity, no portion of the data integrity check is performed by the data protection entity;

receiving, from the data integrity check entity, results of the data integrity check, and the results of the data integrity check identify a data integrity problem that resulted from the data corruption event involving the backup dataset; and

taking an action, based on the results of the data integrity check, to resolve the identified data integrity problem.

2. 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.

3. The method as recited in claim 1 , further comprising creating and storing, by the data protection entity, an information set associated with the backup dataset.

4. The method as recited in claim 3 , 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.

5. The method as recited in claim 3 , wherein the information set is stored in a failure domain that is different from a failure domain in which the data protection VM operates.

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

7. The method as recited in claim 1 , further comprising supplying, by the data protection entity, a data access credential to the data integrity check entity.

8. The method as recited in claim 1 , further comprising creating, by the data protection entity, the backup dataset.

9. The method as recited in claim 8 , wherein the data protection entity creates the backup dataset using a data path that is not employed by the data integrity check entity.

10. The method as recited in claim 1 , wherein the method is performed by the data protection entity at a cloud datacenter.

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

detecting, by a data protection entity, the occurrence of a data corruption event regarding a backup dataset created by the data protection entity;

transmitting by the data protection entity, to a data integrity check entity, a request to perform a data integrity check with respect to the backup dataset, and the backup dataset comprises a backup of an entity other than the data integrity check entity and the data protection entity, and as between the data protection entity and the data integrity check entity, no portion of the data integrity check is performed by the data protection entity;

receiving, from the data integrity check entity, results of the data integrity check, and the results of the data integrity check identify a data integrity problem that resulted from the data corruption event involving the backup dataset; and

taking an action, based on the results of the data integrity check, to resolve the identified data integrity problem.

12. 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.

13. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise creating and storing, by the data protection entity, an information set associated with the backup dataset.

14. The non-transitory storage medium as recited in claim 13 , 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.

15. The non-transitory storage medium as recited in claim 13 , wherein the information set is stored in a failure domain that is different from a failure domain in which the data protection VM operates.

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

17. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise supplying, by the data protection entity, a data access credential to the data integrity check entity.

18. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise creating, by the data protection entity, the backup dataset.

19. The non-transitory storage medium as recited in claim 18 , wherein the data protection entity creates the backup dataset using a data path that is not employed by the data integrity check entity.

20. The non-transitory storage medium as recited in claim 11 , wherein the non-transitory storage medium is performed by the data protection entity at a cloud datacenter.