Critical business app identification in CMDB relationship while performing a disaster recovery

[Namita Mishra]

Hi Community Members!

Need your help in taking a decision.

I would like to know how can a critical business app is identified in CMDB relationship while performing a disaster recovery activity.

 For example: ABC business application has 10 applications related as dependent, however only 4 out of 10 are critical. When I perform disaster recovery for ABC it should point to these 4 critical dependent application.

For this example, do we need to create a new relation called critically dependent in CMDB Relation table to achieve the same, or is there some OOTB method?

Appreciate your prompt response.

Thanks in advance.

Thank You!

Namita Mishra

[Cindy Trieu · Accepted solution]

Hi Namita,

There is no such logic for the status of relationships such as critical, at risk, etc. You will have to build something like this yourself, as far as I'm aware. Is the "critical" status based on some conditions, on some table, etc.?

What CMDB has that can be close is the CMDB Relationship Health Dashboard, but it is based on relationship rules that are missing or rules that aren't being followed correctly. These rules are legacy features though and aren't being kept up to date, so you may see some mismatches here and there. For an example of how the relationship health dashboard works, if you have a rule which says Computers have to have a Contains : Contained by rule with Applications, then any computers that deviate from this rule will be reported on the dashboard as a failure.