This is a quick one.
When applying the below key to disable Auto Discover of Instances, is there a way to limit that to only one client instead of at a Global level?
In my case, I have MySQL DBA’s who want Auto Discover on and the Oracle DBA’s who want it off. They don’t want to manually turn it off every time an Instance is added.
Best answer by Orazan
Good afternoon. This global parameter should disable auto discover for Oracle:
Here is a document on auto discovery for MySQL. Please let me if you have any quesitons:
https://documentation.commvault.com/2022e/expert/19239_advanced_configuration_for_mysql.html#b19258_enabling_automatic_discovery_of_mysql_instances
Good afternoon. This global parameter should disable auto discover for Oracle:
Here is a document on auto discovery for MySQL. Please let me if you have any quesitons:
https://documentation.commvault.com/2022e/expert/19239_advanced_configuration_for_mysql.html#b19258_enabling_automatic_discovery_of_mysql_instances
Good afternoon. This global parameter should disable auto discover for Oracle:
Here is a document on auto discovery for MySQL. Please let me if you have any quesitons:
https://documentation.commvault.com/2022e/expert/19239_advanced_configuration_for_mysql.html#b19258_enabling_automatic_discovery_of_mysql_instances
Hi Orazan
Thank you so much for both links.
Definitely will be useful to us.
Regards,
Mauro
+16Dear
I recently encountered some unexpected behavior while deploying Oracle agents on an Oracle RAC (Exadata) cluster.
Immediately after the agent installation, Commvault not only automatically discovered and created the RAC instance (including connection strings), but it also automatically assigned it to a Storage Policy. This resulted in backups starting automatically the very next day without manual intervention from Commvault admins!
In our experience with Oracle RAC, we typically configure instances manually to ensure all specific parameters are correct. While I understand the "Auto-Discover" feature exists, I have two main concerns:
Auto-Discovery Accuracy: Is it standard for Commvault to fully populate connection strings for Exadata RAC environments so seamlessly?
Automatic Policy Assignment: Is it expected behavior for Commvault to automatically associate a newly discovered instance with a Storage Policy and begin scheduling backups without an administrator's approval? Could the reason for this automatic assignment be because a "Plan" was selected during the initial Oracle agent installation process?
I’d appreciate your insights on whether this is a specific default setting for newer Commvault versions (11.40+) or if there is a way to "discover only" without the automatic policy assignment.
Please for your feedback!
Regards,
Nikos
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
