Business rule to stop discovery updating operational status

[Doraemon]

Hi Experts,

I have a requirement to create a Business rule to stop api discovery updating the operational status of the mssql instances if the status is non-operational/Retired. 

Please provide me guidance on how to achieve this?

Background:

When Rubrik API discovery is running and finding the mssql instance in rubrik,  it is updating the operational status from Non-operational to operational. If the server is going to be retired, DB team is marking it as non-operational in CMDB But since the same instance is backed up in rubrik it is updating the status of the instance again back to operational. 

[kamlesh kjmar · Accepted solution]

Hi @Doraemon ,

You can write a simple before update BR in MSFT SQL Instance table as shown below, just replace the 'rubarik_user_id' in the below screen shot with the user id of the Rubarik user account in your instance:

When to Run section :

Actions Section:

I hope this helps.

Regards,

Kamlesh

[Doraemon]

Thanks a lot Kamalesh 🙂 , This helps my requirement. Appreciate your quick response for my question!

[kamlesh kjmar]

You are most welcome, I am glad I could help 🙂

Regards,

Kamlesh

[Doraemon]

Hi, Is there any way to still update the MSFT CI via discovery without touching the operational status using the above business rule you provided?