Originating Author: Peter Burris
While decisions regarding 3-node DR architectures should be conceived and executed on the basis of application needs (e.g., core revenue-based processes with high write-to-read ratios), the reality of today’s application portfolios is deep interconnectedness of function. The process of choosing which application function and data to support with a 3-node DR architecture usually reveals application resources that not only cannot be supported, but need to be retired. This typically includes software, network, and traditional storage technologies (e.g., legacy tape systems). To streamline the implementation process, as well as reap any savings made possible by exiting ancient maintenance contracts, requires a strong hand that is as focused and disciplined on getting rid of stuff as others are at procuring new products. The scope for this role must cut across storage, application, and network, or 3-node DR architecture projects will fail to deliver expected results.
Action Item: Before beginning to bring new 3-node DR technologies into the shop, empower someone with the mandate and resources required to get rid of the roadblock technologies that offer limited, other benefits.
Footnotes:
