There are two main things that need to be covered when defining a recovery plan:

• Protect documents and data,
• Create a check-list of “what-ifs” and write out what your businesses’ response would be,

Documents and data are critical to the success of the business. It is often said that people are the most valuable asset to a business, but its data comes in a very close second. A single premises business has a potential for further risk as all the non-human assets are stored in a single location. Think of the risk of a fire. Computers (or Servers) must be regularly backed-up with the copies being retained off-site.
It is important to know what your insurance policy covers, but it is also important that key documents are kept off-site. Many insurance policies only cover the essentials e.g. the stock in a store fire, but it is essential to have all IT equipment included. For the small business it can be the red-tape around a policy that can ensure a smaller business does not re-open. Off-site back-ups of computer files and important documents at least ensures that aspect of the business can re-start.

Implementing Business Intelligence solutions it has historically always decided that a data warehouse would simply be re-populated on a new system as part of the disaster recovery plan. In the early days of data warehousing solutions it was possible to simply re-populate the database on a new environment. This is no longer an option for a Business Intelligence solution as the complexity of systems continues to grow. It is essential to consider mission critical the BI system is along with every other corporate application.

In determining how mission critical any system is there are a number of factors that need to be identified. These include:

• Goals generic to the industry sector
• Factors unique to the business being measured
• Applications and their contribution to global business goals
• Corporate legacy architecture

When assessing various parts of the architecture they forget to ask how important is this to the success of the corporation as a whole. E.g. how critical is the success of the passenger check-in system to the success of an airline? The answers will determine a league table of the system criticality.

How mission critical is your BI Solution?

The truth is it will never be the most critical system in the organisation, but it can no-longer simply be repopulated from old data. In our airline example systems relating to safety and ensuring planes continue to depart on-time will always be the most critical of systems. The analytics provided by the BI solution will have become very important in today’s business world.

Closed-loop analytics is becoming increasingly important to many corporations. In one telecom company this capability was so closely tied to the CRM system that Customer Service agents would simply be unable to function correctly without the BI input into the process.

“I want to close my account, and transfer my telephone number to provider X”, takes the agent to a decision based process, that will firstly determine whether the customer is one that the company wishes to retain. Assuming they have retention value the process will provide a set of alternative offers that can be presented to the customer, with the express intent of retaining them. Each step in the process combines the knowledge of the BI system with the capabilities of the CRM. Clearly a mission critical system – central to Disaster Recovery. Not having the two components working smoothly together will damage corporate responsiveness. Agreed the systems are not as mission critical as those necessary to keep the cellular network active, but crucial nonetheless.

According to Wayne Eckerson of TDWI “the litmus test is whether a data warehouse becomes so mission critical that when it goes down people begin to have problems”. This in my view is more the test of when the BI system need to have automatic failover applied to it (as DR is concerned with more than individual machine failure). Many of the database vendors, such as IBM, Oracle and Teradata include failover.

Failover would not have been possible for a server located in the world trade centre on September 11^th 2001, but recovering from the disaster means alternative systems come back on-line within the prescribed time.

Many data warehouses contain derived and aggregated data, which forms the basis upon which specific business decisions can occur. This data needs to be stored and associated with the decision made as an historical check-point. Whenever advanced analytics functions are engaged it is often necessary to update the data warehouse. It is unlikely this data will ever appear in any operational system, placing the data warehouse firmly in the critical path for disaster recovery.

There may be some operations managers that feel adding the data warehouse to the list of critical systems means that other systems are removed. It however important to remember that the role of the data warehouse is to retain historical subject oriented data and is not a backup of associated operational source systems.

The continuity of business ultimately depends on the recovery of the data warehouse as a part of a recovery from a disaster in order to sustain the business and grow from the point of the disaster and moving forward, which often necessitates innovative advances in the marketplace to demonstrate the effectiveness of the corporation.

Peter B. Giblett