Smart datastore selection for protection engines based on uncertainty quantification
One example method includes collecting respective data for each datastore in a group of datastores, clustering the data, based on the clustering, applying one of two different mutually exclusive labels to each of the datastores, applying an uncertainty quantifier to determine, for each datastore, a confidence level that the label assigned to that datastore is the correct label, ranking the datastores according to their respective label and confidence level, and presenting, to a user, a list that includes at least a datastore with a highest confidence level.
1. A method, comprising:
for each datastore in a group of datastores:
collecting data;
clustering the data based on parameters;
based on the clustering, applying one of two different mutually exclusive labels to the datastore based on a determination of whether or not a protection engine is to be deployed to protect the data;
performing a credibility assessment with respect to the data, and assigning a credibility score to each dataset by determining whether or not the parameters are related to health of each dataset;
applying an uncertainty quantifier to determine, for the datastore, a confidence level that the label assigned to the datastore is correct;
ranking the datastores of the group of datastores according to respective label and confidence level; and
presenting, to a user, a list that includes whichever of the datastores has a highest confidence level.
2. The method as recited in claim 1 , wherein one of the two different mutually exclusive labels is a HIGH label, and the other of the two different mutually exclusive labels is a LOW label, and the HIGH label indicates a healthy datastore, and the LOW label indicates an unhealthy datastore.
3. The method as recited in claim 1 , wherein the data that is collected for one of the datastores comprises data indicative of a health of that one datastore.
4. The method as recited in claim 1 , wherein the clustering clusters the data into two clusters that collectively contain all the datastores, and a first one of the two different mutually exclusive labels is assigned to datastores in a first cluster of the two clusters, and a second one of the two different mutually exclusive labels is assigned to datastores in a second cluster of the two clusters.
5. The method as recited in claim 1 , wherein the clustering is performed using HDBSCAN (Hierarchical Density-Based Spatial Clustering of Applications with Noise).
6. The method as recited in claim 1 , wherein the label on the datastore with the highest confidence level is HIGH.
7. The method as recited in claim 1 , further comprising receiving a user selection of a datastore with the label HIGH and a highest confidence level of any of the datastores.
8. The method as recited in claim 1 , further comprising receiving a user command to restore protected data to a datastore with the label HIGH and a highest confidence level of any of the datastores.
9. The method as recited in claim 1 , further comprising receiving a user command to deploy a data protection resource to a datastore with the label HIGH and a highest confidence level of any of the datastores.
10. The method as recited in claim 1 , wherein, when the credibility score is low indicating that the parameters are not related to the health of each datastore, the method further comprising:
collecting additional data to obtain an updated credibility.
11. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
for each datastore in a group of datastores:
collecting data;
clustering the data based on parameters;
based on the clustering, applying one of two different mutually exclusive labels to the datastore based on a determination of whether or not a protection engine is to be deployed to protect the data;
performing a credibility assessment with respect to the data, and assigning a credibility score to each dataset by determining whether or not the parameters are related to health of each dataset;
applying an uncertainty quantifier to determine, for the datastore, a confidence level that the label assigned to the datastore is correct;
ranking the datastores of the group of datastores according to respective label and confidence level; and
presenting, to a user, a list that includes whichever of the datastores has a highest confidence level.
12. The non-transitory storage medium as recited in claim 11 , wherein one of the two different mutually exclusive labels is a HIGH label, and the other of the two different mutually exclusive labels is a LOW label, and the HIGH label indicates a healthy datastore, and the LOW label indicates an unhealthy datastore.
13. The non-transitory storage medium as recited in claim 11 , wherein the data that is collected for one of the datastores comprises data indicative of a health of that one datastore.
14. The non-transitory storage medium as recited in claim 11 , wherein the clustering clusters the data into two clusters that collectively contain all the datastores, and a first one of the two different mutually exclusive labels is assigned to datastores in a first cluster of the two clusters, and a second one of the two different mutually exclusive labels is assigned to datastores in a second cluster of the two clusters.
15. The non-transitory storage medium as recited in claim 11 , wherein the clustering is performed using HDBSCAN (Hierarchical Density-Based Spatial Clustering of Applications with Noise).
16. The non-transitory storage medium as recited in claim 11 , wherein the label on the datastore with the highest confidence level is HIGH.
17. The non-transitory storage medium as recited in claim 11 , further comprising receiving a user selection of a datastore with the label HIGH and a highest confidence level of any of the datastores.
18. The non-transitory storage medium as recited in claim 11 , further comprising receiving a user command to restore protected data to a datastore with the label HIGH and a highest confidence level of any of the datastores.
19. The non-transitory storage medium as recited in claim 11 , further comprising receiving a user command to deploy a data protection resource to a datastore with the label HIGH and a highest confidence level of any of the datastores.
20. The non-transitory storage medium as recited in claim 11 , wherein, when the credibility score is low indicating that the parameters are not related to the health of each datastore, the operations further comprise:
collecting additional data to obtain an updated credibility.