Best pratices for [DR provided by::Provides DR for] relationship type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We have a service that provides recovery for business application data. I'm trying to determine the correct relationship between the service and the business application. Based on my research, I believe that the following is the correct relationship: RECOVERY_SERVICE {parent} [DR provided by::Provides DR for] BUSINESS_APPLICATION {child}. However, when reading this relationship it looks like the BUSINESS_APPLICATION is providing data recovery for the RECOVERY_SERVICE. Have I got this correct or do I need to flip the relationship? Also, if you would provide a link to ServiceNow documentation to support your answer I would greatly appreciate it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey Steve,
Interesting question. I checked and could not find any concrete ServiceNow documentation, but i will try to make a clear answer - however it might be related to a different scenario.
Data recovery is provided on a operational level between two application instances. The relationship you refer to I have used in only that application instance to application instance level OR business application to business application level. Why is that?
On an operational level, my interest lies with the impact of the data recovery to its related application instances. If i have an application instance which requires a backup to be done (or recover one) I want to see which application instance holds that backup. The other way around: if a recovery application instance/recovery service is compromised, i want to understand which related application instances are impacted by that.
On the business application level i need the architectural insight. I want to understand which recovery tool is used to provide backup for certain business applications. The goal here is to make sure every business application does have another business application which provides a backup. This architectural planning then should be reflected on an application instance level (as described in my first point) as well.
Now here is the thing where I cannot find the specific use-case you are referencing. If both types are modeled as i've described, then the only relationship between the Business Application level & the Application Instances are the normal "consumes" relationships between the BA & AI. What i see as quite unusual is the relationship on the operational level being mixed with that on the architectural level. In short: I personally would not see the need to add the specific relationship you have highlighted, if the relationships i have highlighted are present.
Do you have more context & maybe a clear use-case to give me a bit of insight to understand the need of the relationship?
Regards
Fabian
