February 8, 2013 at 6:25 am
How to evaluate the current state hardware/databases in light of Disaster Recovery (D/R) and Business Continuity (BC)
what are the factors to consider.
February 8, 2013 at 8:48 am
m.rajesh.uk (2/8/2013)
How to evaluate the current state hardware/databases in light of Disaster Recovery (D/R) and Business Continuity (BC)what are the factors to consider.
This certainly is a topic that exceeds a forum post.
For starters, look at the meaning of "Business Continuity"... it basically means planning has to be in place to ensure that the business continues to exist and operate in case of a disaster.
For starters, applications should be categorized in three different levels, they could be:
1- AA - Critical. Business cannot operate if this application is not available and operational. An example of this one would be the OLTP system taking customer orders on a purely online company.
2- BB - Important. Business can survive for two to three weeks without having this application avalilable and operational. An example could be payroll.
3- CC - Nice to have. Business can survive for a long time if this application is not available and operational. An example could be a particularly obscure datamart.
Once you have all your applications categorized that way you should identify all the hardware and software needed to support all AA and BB applications, also the cost of having each one of the in stand alone mode.
At that point, businss has to make a decision, pick and choose what is needed and fund the project. This is not trivial, it involves stand bye infrastructure, data replication, a sound patching and upgrading strategy for both OS and application, etc. etc. etc.
Hope this helps.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply