Service Mapping - Best Practice for Including "Secondary or Failover" Application Servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2023 11:32 AM
Situation:
We have an Application Service, that we have performed service mapping on using the Top-Down approach. The map has more or less completed successfully. However, we have a secondary APP Server that the Application Service can failover too in the event of a problem with the primary APP Server. The issue we are running into is this secondary APP Server isn't being found and added to the Map.
Question:
We are wondering what the best practice is when it comes to adding this secondary app server to the map. Obviously at the time of Service Mapping it isn't part of the Application Service, however the Application Owner feels it should be represented on the Map as it does make up their App Stack.
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 12:56 PM
Hello, I'm wondering if you came up with a solution to do this. I'm finding myself in the same situation, and I'm not sure how to proceed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2025 11:18 PM
Hi Scott,
Did you find a way forward with this?
I am looking at to achieve a similar thing. I can of course use the DR Provided by relationship from server to server for example but it does not always work on a 1 to 1 basis if something fails. I am wondering whether to use an app service mirroring the primary for the purpose of a DR environment?
Regards
Dan
