Disaster Recovery Planning

Disaster Recovery Planning International Standard Set by Janco

webmaster — Wed, 25 Aug 2010 16:04:45 -0600

Disaster Recovery Business Continuity Template Now Accepted as the International Standard

Update to the Disaster Recovery Business Continuity Template has just been released by Janco Associates..

Park City, UT - The Disaster Recovery Business Continuity Planning template has been sold to enterprise in over 65 countries around the globe. With the release the latest verison of the template it is in complete compliance with Sarbanes-Oxley, HIPAA, ITIL (Ver 3), ISO 17799, and PCI DSS.

M V Janulaitis the CEO of Janco said, "Our DRP /BCP Template has been accepted by enterprise around the globe as the standard for disaster recovery plan and business continuity plan creation." In response to that need Janco has updated its "Disaster Recovery / Business Continuity Template" by increasing the content of the template as well as updating the entire document to be compliant with Sarbanes-Oxley, HIPAA, ITIL (Ver. 3), ISO 17799, and PCI DSS.

The Disaster Recovery Business Continuity Plan has been purchased for use in over 65 countries around the globe including:

Angola
Australia
Austria
Bahamas
Barbados
Belgium
Belize
Bermuda
Brazil
Bulgaria
Canada
Cayman Islands
Columbia
Croatia
Czech Republic
Denmark
Egypt

Finland
France
Germany
Greece
Honduras
Hungary
Iceland
India
Indonesia
Israel
Italy
Jamaica
Japan
Jordan
Kenya
Lebanon
Lithuania

Macao
Malta
Mexico
Mozambique
Namibia
Netherlands
New Zealand
Nigeria
Norway
Panama
Philippines
Poland
Portugal
Puerto Rico
Qatar
Republic of Ireland
Romania

Russia
Saudi Arabia
Singapore
South Africa
South Korea
Spain
Sri Lanka
Swaziland
Switzerland
Taiwan
Thailand
Trinidad & Tobago
Uganda
United Kingdom
United States
Venezuela
Zambia

The Disaster Recovery Business Continuity Plan has been purchased for use in government, public, and private enterprises in almost all industries including:

Federal Government
State Governments
Local Governments
Law Firms
Think Tanks
Chemical
Telecommunication
Real Estate
Manufacturing

Universities
School Districts
Consulting Firms
Banks
Financial Service
Investment Banks
Credit Unions
Outsourcers
Property Mgt

Heavy Industry
Light Industry
Distribution
Retail
Hospitality
Energy
Insurance
Medical
ISPs

Application Development
Construction
Graphics
Entertainment
Paper Products
Defense
Aerospace
Media

Disaster Plan & Business Continuity Infrastructure

webmaster — Wed, 18 Aug 2010 09:35:37 -0600

The key technology elements of a Disaster Recovery Plan and Business Continuity Plan (DRP/BCP) infrastructure are the primary data center, a remote site that duplicates the resources in that primary location and the method used to get files (master and transaction) between the two sites - such as high-bandwidth network connections. The best DRP/BCP strategies follow a "redundant every-thing" philosophy throughout the data center. Multiple mainframes and servers should run in the production and backup data facilities. Then, if a component in the production system encounters problems, it immediately fails over to the local backup as a first line of defense.

Power supplies and communication links are one of the most critical components in a DRP/BCP strategy.

Microsoft products do not work with each other

webmaster — Fri, 13 Aug 2010 12:31:57 -0600

Angry customers, perhaps unable to contact customer support via e-mail, have inundated Microsoft support forums with an array of complaints, such as the inability to load or to send messages, as well as problems with script errors.

As if these problems that have turned Hotmail into Notmail weren't bad enough, Microsoft's suggested solutions have ironically urged users to turn off certain Microsoft products or features. Among the recommendations: Don't use Messenger, Internet Explorer, or particular Windows 7 features if you want Hotmail to work properly.

Killing the Web-based version of Messenger is listed as a way to address the problem of a script causing one's browser to run slowly while attempting to access Hotmail. "[We] are working on releasing a fix as soon as possible, but until then, a good workaround is to try signing out of Messenger on the Web (click your name in the upper-right of the page, and then click "Sign out of Messenger" in the menu)," reads a portion of the "Frequently experienced issues in the newest version of Hotmail." The Windows Live Team is working to fix the problem, Microsoft says.

Another frequent problem: Mobile broadband users report they can't read their mail. Microsoft attributes this little inconvenience to, yet again, script errors and suggests users stop using Internet Explorer or Firefox and instead try using Windows Live Mail or the mobile version of Hotmail. An alternative solution Microsoft offered in one of the support threads: Try Google Chrome. Microsoft notes that it the Windows Lives Team has developed a fix for this problem that has yet to be released

Finally, for users who aren't able to send messages, Microsoft offers this workaround: If you are using High Contrast display mode in Windows 7, turn it. The Windows Live Team is -- you guessed it -- working on a fix, Microsoft notes.

The focus of a DRP/BCP

webmaster — Sat, 07 Aug 2010 12:52:24 -0600

All BC/DR plans need to encompass how employees will communicate, where they will go and how they will keep doing their jobs. The details can vary greatly, depending on the size and scope of a company and the way it does business. For some businesses, issues such as supply chain logistics are most crucial and are the focus on the plan. For others, information technology may play a more pivotal role, and the BC/DR plan may have more of a focus on systems recovery. For example, the plan at one global manufacturing company would restore critical mainframes with vital data at a backup site within four to six days of a disruptive event, obtain a mobile telephone switch with 3,000 telephones within two days, recover the company's 1,000-plus LANs in order of business need, and set up a temporary call center for 100 agents at a nearby training facility.

But the critical point is that neither element can be ignored, and physical, IT and human resources plans cannot be developed in isolation from each other. (In this regard, BC/DR has much in common with security convergence.) At its heart, BC/DR is about constant communication.

DRP and Security Plans key to compliance

webmaster — Sat, 24 Jul 2010 13:41:04 -0600

Preparing for a disaster requires detailed planning, preparation and testing. Knowing what IT assets need to be recovered, where to recover them and how to recover them are the essence of IT Disaster Recovery. The most difficult challenge is mapping the prioritized business requirements to the IT assets so that recovery can be staged. The recovery strategy then evolves based on the available options which support the required recovery objectives. The resulting Disaster Recovery plans contain all of the information detailing where to go, who is to do what and the information required to rebuild servers, restore applications and data as well as restart and synchronization procedures.

Simple Disaster Planning Activities

webmaster — Tue, 13 Jul 2010 01:29:34 -0600

Creating a disaster recovery plan is a complex task; however there are a number of basic steps that you can follow to start thre process

Prepare your systems, processes, and people for an organized response to disaster when it strikes.
Identify critical IT systems and develop a long-range strategy.
Select and train your disaster recovery team.
Conduct a Business Impact Analysis.
Determine risks to your business from natural or human-made causes.
Get management support.
Create appropriate plan documents.
Test your plan.

Wireless may become open source like

webmaster — Tue, 22 Jun 2010 22:27:43 -0600

Infrastructure planning may become easier for CIOs as AT&T and Verizon Wireless, the two largest U.S. mobile operators, have joined an organization that ensures roaming among mobile operators' Wi-Fi networks.

The group, called the Wireless Broadband Alliance (WBA), also announced on Monday that South Korean mobile operator KT, Cisco Systems, U.S. cable operator Comcast, and wireless software vendor Devicescape Software have recently joined.

Recovery time is focus of 57% of Business Continuity Managers

webmaster — Fri, 18 Jun 2010 12:09:13 -0600

In a recent survey it was found that 57 percent of IT organizations see reducing recovery time in the event of IT failure and cutting the cost of backup as the two biggest pain-points for backup and disaster recovery. The next most significant difficulties were the ability to roll back to any point in time when recovering workloads and recovery testing.

Virtualization is already in place with the majority of those surveyed, with 86 percent of those questioned having a virtual infrastructure in place within their organizations.

Other findings are:

Tape backup is the most popular technology involved for recovery of virtual machines, with 60 percent of organizations relying on tape to protect their virtualization implementations. 53 percent of organizations are using disk-to-disk backup products, while proprietary virtualization products are used by 23 percent;
17 percent of organizations are only using tape backup for the backup / recovery of their virtual machines;
The number of respondents that were able to judge their recovery point objectives (RPO) when it came to virtualized environments was much lower than those able to define their recovery time objectives (RTO) - only 45 percent of those surveyed were able to state their satisfaction level around their RPOs.

Continuous Data Protection can be used as a backup strategy for DRP amd BCP

webmaster — Thu, 27 May 2010 00:36:24 -0600

Continuous Data Protection (CDP) is an increasingly popular disk-based backup strategy. It is replication with an Undo button. Every time a block of data changes on the system being backed up, it is transferred to the CDP system. However, unlike replication, CDP stores changes in a log, so you can undo those changes at a very granular level. In fact, you can recover the system to literally any point in time at which data was stored within the CDP system.

A near-CDP system works in similar fashion except that it has discrete points in time to which it can recover. To put it another way, near-CDP combines snapshots with replication. Typically, a snapshot is taken on the system being backed up, whereupon that snapshot is replicated to another system that holds the backup.

Why take the snapshot on the source before replication? Because only at the source can you typically quiesce the application writing to the storage so that the snapshot will be a meaningful one.

Senate plans to control IT Spending

webmaster — Mon, 24 May 2010 16:30:47 -0600

The Senate has passed a bill that would put tighter controls around the money the government invests in its major information technology projects. Metrics for this process are yet to be defined

The Information Technology Investment Oversight Enhancement and Waste Prevention Act (S. 920) would set up tougher monitoring of the roughly $80 billion that agencies spend each year on IT.

The Government Accountability Office reported in October 2009 that it had identified 11 mismanaged IT investments made by agencies that will likely cost $3 billion more than planned.

Mobile workforce chanllenges disater planning process

webmaster — Tue, 11 May 2010 13:47:26 -0600

It is estimated that by the end of 2011, mobile workers will make up 73 percent of the total US workforce. These workers increasingly demand access to current, comprehensive, and often sensitive data, while relying on smaller IT operations teams to provide it. This creates a significant challenge for disaster recovery and business continuity planning: how to make the most data available to the greatest number of mobile employees, while maintaining availability and security levels.

Weather is the primary cause of disaster declarations

webmaster — Sun, 25 Apr 2010 12:30:29 -0600

Disasters and emergency situations can strike at any time. The term, disaster, typically brings to mind serious weather events like tornadoes and fl oods, man-made disasters such as oil spills, or accidents resulting from human error such as a utility crew severing a power line or water main. Though these events are still common - in 2006 and 2007 across the US.

FEMA records disasters and has classified them for 2006 (52 disaster declrations) and 2007 (53 Disaster declarartions).

Disaster declarations at an average rate of one per week - over the past ten years the frequency, magnitude and scope of disasters has broadened to include national wildfi res, pandemic threats, acts of terrorism such as Fort Hood in 2009 and crises such as the Virginia Tech Shootings, the mall shootings in Omaha, Nebraska, in December 2007.

Disaster Recovery Business Continuity for Remote Offices

webmaster — Sat, 24 Apr 2010 01:06:23 -0600

Data residing outside the data center at remote and branch offices (ROBOs) accounts for a significant portion of an enterprise's information store, yet it often either is protected with inefficient backup processes or is not protected at all -- leaving companies at risk on many fronts.

In a recent research report, high priority projects for ROBOs included improving information security measures; ensuring compliance with government, industry or corporate governance mandates; and improving Disaster Recovery Business Continuity processes.

Outsouring Can Help in Disaster Recovery Planning

webmaster — Fri, 16 Apr 2010 21:11:59 -0600

Between hackers, natural disasters, or even a pipe breaking in the office above yours, every business needs a contingency plan. It could mean the difference between riding out a problem and going out of business. For this reason, most businesses are concerned about the safety of their backups. Data loss is a significant concern for any business - and in healthcare and other industries can have huge financial consequences. Solutions typically require that you spend more money on a third party backup solution. Outsourcing is one solution that should not be overlooked. Solutions typically require that you spend more money on a third party backup solution. Outsourcing is one solution that should not be overlooked.

Guidelines for Disaster Recovery and Business Continuity Planning

webmaster — Wed, 07 Apr 2010 18:17:03 -0600

Disaster recovery and business continuity are important business issues that require awareness and planning. Guidelines that can be used in this process are:

Look at the big picture - your business processes, systems, networks, data, and people all need to be considered when planning and implementing these processes.
Understand your levels of tolerance for lost work, missing data, and unproductive time.
Document and test your plans, and update them when business needs change.
Configure your environment to minimize the likelihood of a failure escalating into a disaster.
When evaluating technology solutions, take into account meeting your recovery objectives, kinds of disasters you're likely to face, and levels of cost, complexity, and disruption involved.
Know the advantages and limitations of each technology, and adjust your expectations accordingly.
Remember that backing up your data is the most reliable form of protection, without which your business is vulnerable.

Budget cuts impact disaster plans

webmaster — Thu, 04 Mar 2010 23:13:19 -0600

IT staff cuts spurred by the economy are likely to continue throughout the remainder of the year. According to a survey of 300 IT center managers last year, half of all data centers were planning to cut 2010 budgets by an average of 15%. Respondents at 14% of those companies said the cuts would include layoffs of IT staffers.

The PayPal electronic payment system is one of many Internet-based services that have been hit with outages. And based on news reports, the number of such incidents appears to have been increasing in recent months, analysts said. They cited shutdowns of the Google Apps software hosted by Google Inc., outages at data centers run by Rackspace Hosting Inc. and a distributed denial-of-service attack on Twitter.

Observers pointed to several possible reasons for the apparent uptick in online outages, including IT budget and personnel cutbacks, increasing corporate dependence on hosted applications -- and bad luck. Companies are not doing the maintenance we should be doing, and when you do not do maintenance, they increase the probability of catastrophic failure.

Which Files Need to be backed up

webmaster — Sat, 20 Feb 2010 17:08:13 -0600

Hard drives often contain hundreds of thousands of files. Many of them should be backed up every day, others only occasionally, and still others - including temp files, the hibernation file, and your browser cache--not at all.

Documents: You should back up your word processing files, spreadsheets, and similar documents every day. Most basic backup program perform incremental backups, in which the program copies only the files that have changed since the most recent previous backup. (Several backup programs also perform versioning; they keep several iterations of the same file on hand and enable you to choose which version to restore.)
Recent Documents: If your backup program can handle incremental backups, you don't have to worry about recent documents as separate entities. But if you often work on these files on other people's computers, you may want to carry a copy of them on a flash drive or store a copy of them online.
Application Data: Applications create and maintain data files such as e-mail messages, browser favorites, calendar entries, and contacts that require daily backing up. Many programs store them in a hidden folder inside your user folder (in XP, C:\Documents and Settings\your name\Application Data; in Vista, C:\Users\your name\AppData). Also, in XP, Microsoft stores Outlook and Outlook Express data in C:\Documents and Settings\your name\Local Settings\Application Data). Fortunately, any well-designed backup program intended for everyday, nonexpert users (as opposed to IT departments) knows where to look for Outlook data.

Operating System: You can always reinstall Windows and your apps, if you have the original discs or can download the programs. But if Windows becomes unusable or your hard drive crashes, switching to a system backup (also called a disaster recovery backup) that you create a couple of times a year can get your machine up and running smoothly without much effort.

Media: These large files require a separate backup strategy because of the amount of storage space they require..
Heirlooms: Files that you want to keep forever need backing up and extra protection.

How to calculate the cost of downtime

webmaster — Wed, 10 Feb 2010 16:32:53 -0600

One overlooked truth is that downtime costs accelerate in a non-linear fashion every hour. If a system fails for five minutes, the costs are fairly low because manual methods (paper and pencil) of making records or communicating by telephone instead of e-mails can suffice to conduct business. Over an extended period, however, the volume of work overwhelms the manual processes. Yet some businesses - such as Amazon or e-Bay - cannot run at all on manual processes. Business and financial operations increasingly deteriorate, and the rate of dollar losses grows - sometimes to the point of fatally damaging the business.

In addition, when assessing the financial impact of downtime, you need to consider factors such as potential lost revenue, reductions in worker productivity, and damaged market reputation. In some cases, downtime can even reduce shareholder confidence, which can create unnecessary and unplanned costs. Financial analysts and accountants at your company can help you come up with the factors at your company that are affected by downtime and contribute to its costs.

Cost of email downtime is high

webmaster — Sun, 31 Jan 2010 16:37:21 -0600

In today's economy, the importance of e-mail takes on new meaning. Recovery time and recovery point objectives (RTOs and RPOs) are no longer general rules. The Exchange administrator's ability to meet or exceed the proverbial lines in the sand, in terms of time to recover and the age of the data recovered, can mean the difference between gainful employment and prepping for a job interview. In fact, average yearly cost of Exchange downtime for a 500-person corporation, according to data derived from the Contingency Planning Association and Strategic Research, is over $1.5 million.

Disaster Recovery Planning Template Business Continuity Plan

Sarbanes - Oxley - ISO 27000 (27001 & 27002) - HIPAA - PCI- Compliant

Disaster Recovery Planning (DRP) template can be used by any size enterprise. The template and supporting material have been updated to be Sarbanes-Oxley compliant. The Disaster Recovery Planning Documentation comes as a Word document and includes:

Disaster Recovery Plan Template
Business and IT Impact Analysis Questionnaire
Work Plan
Disaster Recovery & Business Continuity Audit Program

Included in the template is Business Impact Questionnaire as well as a full Job Description for the Disaster Recovery Manager. The premium edition contains 11 full job descriptions.

Communication during a recovery process often is not well planned

webmaster — Sat, 23 Jan 2010 12:08:22 -0600

Disaster recovery and emergency team members status communication and news have distinct audiences with different needs when a crisis occurs.

Employees/General Populace: Need access to 'basic information' such as where to go, when to return to work, and how to locate general information about the crisis situation
Disaster Recovery Team Members: Need to account for all employees/constituents safety and assess the state of business operations; need the ability to communicate in real time, disseminate information, track recovery efforts, assign tasks and provision supplies, power, etc.; need the ability to have real time status of the situation
Executives/Leaders: Need to know that their employees and constituents are safe; need to know the status of their business and access a high level, real-time status of the recovery efforts; need to be able to communicate with customers, investors, and people external to their business about the crisis.

Effective crisis communication requires technology to provide a unified solution for communicating information to all involved constituents and should provide a single source of accurate and up-todate information that can be accessed.

Many Businesses Fail After a Disaster

webmaster — Tue, 19 Jan 2010 17:34:10 -0600

Businesses' reliance on IT systems and digital data has never been greater. The 2007 Best's Underwriting Guide found that only 6% of companies that suffer catastrophic data loss survive while 43% never reopen and 51% close within 2 years of the disaster. Best's Underwriting Guide 2007 also found that 93% of the companies that did not have their data backed up in the event of a disaster went out of business. An analysis of SMBs' prioritization of disaster recovery, backup and high availability for 2008 shows that businesses understand the risks to their business and the value of protection. However, many organizations still think that backup is a sufficient disaster recovery plan. However, mid-sized enterprises are at the most risk to disaster and are more likely to rely strictly on backup as a disaster recovery plan.

The needs and resources of mid-market firms are unique. Midsized companies must work with limited finances infrastructure and human resources. Robust disaster recovery used to be affordable and manageable only by large enterprises. Mid-sized enterprises relied more on backup than on a formal disaster recovery plan. As businesses' reliance on IT has grown, backup has increasingly shown its weaknesses. However, the introduction and maturation of several key technologies, such as virtualization, have brought affordable and easily implementable Disaster Recovery and Business Continuity to small and mid-sized companies. SMBs do not always equate virtualization with Disaster Recovery and Business Continuity because awareness of the many virtualization applications is just starting to grow.

Consolidation and Disaster Planning

webmaster — Thu, 07 Jan 2010 10:31:42 -0600

Most organizations today are faced with conflicting goals and challenges. They have geographically distributed workforces, with headquarters, datacenters, branch offices, and mobile workers scattered widely. Everyone needs to access email, file shares, and mission critical applications, and the speed of access directly ties to employee productivity. So computing resources have been widely deployed in many locations to give the local workers the best possible service delivery. However, this approach is now seen as wasteful and expensive with extra hardware and software to buy and maintain for many locations, and often few local IT staff to support the systems. As budgets get tighter, organizations are looking for solutions to handle this burden. IT consolidation is the number one approach today, taking infrastructure out of remote offices and into the main data center as a way to cut costs and boost IT staff productivity. The trick is how to consolidate without hurting the performance for the end users.

While consolidation can certainly bring a number of benefits to organizations, it will take more than just a Friday afternoon to
ensure that your consolidation, disaster recovery, and business continuity projects are truly successful. As far too many IT managers will tell you, a poorly planned project will have your executives screaming, users threatening mutiny, and IT in the hot seat to quickly undo all the effort that went into the project in the first place.

Lay out a change and risk management strategy
Develop a plan for resiliency
Test (and improve) branch office performance & local consolidation
Architect a forward-looking infrastructure & support plan
Plan a phased roll-out

Lack of disaster planning led to present crisis

webmaster — Sat, 05 Dec 2009 12:21:57 -0600

Everyone came to the same conclusion: A lack of disaster planning was a key component to the extent of the damage and loss of life.

Seventeen charity and civil society organizations met at the Jeddah Chamber of Commerce and Industry (JCCI) to organize their efforts after a few days of spontaneous but much appreciated mobilized work to collect and distribute donations in the affected areas. This followed a warning issued by the Governorate cautioning individuals and groups against donating haphazardly and instead directed them to give their donations through registered charity organizations, which are supposed to coordinate their distribution work with the Jeddah Governorate to ensure that the donations reach those who need them.

Discussions quickly revealed a lack of coordination among the charities and with the relevant government offices, namely the Civil Defense and the governorate. While several charities focused on the hardest hit areas, which needed every parcel of assistance it could get, other areas that were also hit hard were almost neglected. It turns out that Al-Sawaed, which has become a ghost town with only ruins, and all the Kilo areas and Mahameed were in bad shape. Poor neighborhoods in downtown Jeddah such as Ghulail and Karantina were also stricken with residents living in knee-high stinking sewage with barely the essentials to live by. Other areas hit hard include Um Alsalam, Bahra, Jamaa, Al-Musaid.

DVDs Last Only Two to Five Years

webmaster — Mon, 16 Nov 2009 02:41:39 -0600

The National Archives warns - "CD/DVD experiential life expectancy is 2 to 5 years even though published life expectancies are often cited as 10 years, 25 years, or longer. However, a variety of factors discussed in the sources cited in FAQ 15, below, may result in a much shorter life span for CDs/DVDs. Life expectancies are statistically based; any specific medium may experience a critical failure before its life expectancy is reached. Additionally, the quality of your storage environment may increase or decrease the life expectancy of the media. We recommend testing your media at least every two years to assure your records are still readable."

Busines continuity planning is impacted by this. However there may be a solution. Start-up claims its DVDs last 1,000 years - The DiamonDisc uses standard DVD players and burn software and Cranberry's DiamonDisc product holds a standard 4.7GB of data, which roughly amounts to 2,000 photos, or 1,200 songs, or three hours of video, but the media is unharmed by heat as high as 176 degrees Fahrenheit, ultraviolet rays or normal material deterioration, according to the company. DiamonDiscs contain no dye layers, adhesive layers or reflective materials that could deteriorate.

Testing and training models for a disaster recovery and business continuity plan

webmaster — Tue, 10 Nov 2009 11:16:36 -0600

After you created your disaster recovery and business continuity plan you are not done. In reality your disaster recovery and business continuity plan are useless until you test them and train your staff in how to activate and use them. The key is to incorporate testing and training as part of the overall disaster recovery and business continuity management process.

Testing and Training Models

Plan Review

In a plan review, the disaster recovery and business continuity plan owner and team discuss the disaster recovery and business continuity plan. They look for missing elements and inconsistencies within the plan or with the organization. This type of exercise is comparable to plan auditing, and is useful to train new members of a team, including the business function owner.

Walk-Thru

In a walk-thru exercise, participants gather in a room to execute documented plan activities in a stress-free environment. Walk-thru exercises can effectively demonstrate whether team members know their duties in an emergency and if they need training. Documentation errors, missing information and inconsistencies across disaster recovery and business continuity plan can be identified in a walk-thru exercise.

Simulation

To determine if disaster recovery and business continuity management procedures and resources work in a realistic situation, a simulation exercise helps. This exercise uses established disaster recovery and business continuity resources, such as the recovery site, backup equipment, services from recovery vendors and transportation. It can require sending teams to alternate sites to restart technology as well as business functions. Errors, omissions, missing or insufficient resources, incomplete coverage, and limited vendor capabilities may surface in this exercise. Simulations may also uncover staff issues regarding the nature and the size of their tasks. The use of a scenario is highly recommended for simulations.

Objectives

Why exercise in the first place? The primary objective is to ensure that the plan works when it is needed. But it is not enough to exercise parts of a plan. Ideally all elements of disaster recovery and business continuity plans should be exercised at least once a year if not quarterly. Each exercise may have different objectives, beside the primary one.

Main exercise objectives include identifying weaknesses and shortcomings, verifying recovery objectives and procedures, validating global efficiency of plans, verifying the adequacy of emergency operations centers (EOCs) and alternate sites, and achieving specific recovery time objectives (RTOs) and recovery point objectives (RPO).

How much should you test?

Tests can be simple or complex. A table-top exercise can establish a plan performance baseline. A specialized test, such as one which focuses on crisis management procedures at an EOC, provides valuable information about specific activities. At a higher level, an integrated exercise can address multiple disaster recovery and business continuity plans or plan components. Finally, an entire plan, with all components, can be exercised. It is far better to err on the side of exercising too much, rather than not enough.

Managing human resources

Tests present human resource issues. Tests are important for validating team member expertise and identifying training opportunities. Conversely, people could refuse to work overnight, weekends or be away from home even a few days. Be sure to discuss and resolve these issues with human resources management.

During disaster recovery and business continuity plan tests, it is good practice to treat team members well, especially when they are away from home or working difficult hours. Be sure to budget for appropriate hotel accommodations and food, while managing costs.

Effective test strategies

The test options will help improve disaster recovery and business continuity plans and train staff. But no matter how often you exercise plans, when reality strikes, your response capability could be much different than in the exercises.

Key strategies for testing include starting simple; raising the bar in terms of difficulty; involving vendors and stakeholders in exercises; making objectives increasingly difficult to achieve; and launching surprise exercises. When launching an exercise program, start with plan reviews and walk-thrus. This will help staff get comfortable with the exercise process. As they improve, increase the level of exercise complexity. Remember that if an exercise fails, it is not a failure; rather, it is a success. It is far better to identify systems and procedures that may fail, and rectify them, before a real incident occurs. Finally, a true test is to launch a surprise incident. This will truly test how well prepared the organization is to address a real incident.

What is a successful test?

The primary reason to exercise is to identify limitations of disaster recovery and business continuity plans. Recognizing that most organizations change frequently, even mature business continuity plans may be inappropriate in a given situation or at a given time. Tests that appear to be successful and uncover no problem should be suspect. Maybe the objectives were too easy or the situation was unrealistic. Exercises present opportunities to fix problems before a disaster happens.

A successful test uncovers and documents problems. Once the problems have been fixed, consider running a follow-up test to ensure the repairs work. Measuring the success of disaster recovery and business continuity tests means having relevant objectives that will help uncover problems. Testing is your chance to push your disaster recovery and business continuity plans increasingly closer to the reality of a disaster.

US Smart Grid Could Cause Business Interruptions - Disaster Planning Consideration

webmaster — Mon, 02 Nov 2009 04:02:29 -0600

A cybersecurity coordination task force released a report that assesses various security and privacy requirements for the U.S. Smart Grid, as well as strategies needed to address them. It looks at security and disaster planning issues.

The 256-page document was compiled by the task force, composed of individuals from the government, industry, academia, and regulatory bodies, and led by the National Institutes of Standards and Technology (NIST). Now open for comment, NIST will release a final version of the document in March 2010 describing a overall Smart Grid security architecture and security requirements.

The draft report highlights the need for planners to address threats that could potentially allow attackers to penetrate the smart grid, gain access to control software, and alter load conditions to cause widespread disruptions. Cybersecurity strategies for protecting the smart grid need to address not only deliberate attacks but also inadvertent compromises resulting from user errors, equipment failures and buggy software, the report said.

Released as part of the report was a Privacy Impact Analysis that examines some of the privacy implications of establishing a smart grid for power distribution.

A smart grid uses digital technology to transmit, distribute, and deliver power to consumer in a more reliable and efficient manner than traditional electricity systems. A key component of the smart grid is the real-time, two-way communication it establishes between consumers and power distributors for tracking energy use and enabling smarter consumption and pricing. Current plans call for nearly 17 million two-way connected smart meters to be installed in U.S. homes over the next few years.

Disaster recovery continues to be an area of high risk and high cost

webmaster — Sat, 17 Oct 2009 11:40:55 -0600

A recent survey by Janco Associates showed that organizations of all sizes considered that the loss of IT systems was the threat most likely to have an impact on costs and revenue and that it is the most commonly experienced disruption.

The regulated nature of the IT environment, combined with the statutory obligations of clients' data protection, means that having a disaster recovery system in place is essential. Until now, enterprises of all sizes have faced enormous costs and inflexible regimes to implement effective IT disaster recovery provisions. Many have therefore been forced to settle for a mere plan of action or ineffective options, which may in reality, do little to reduce their risks. So what are the options for protecting critical IT systems for your firm?

Have a backup

Most organizations take backups, but it is the barest minimum requirement for protecting your firm from a disaster. Backups are for getting you out of a hole when you accidentally delete/lose/corrupt data on your working machines. If you lose those machines completely then the backup will only help once you have replaced and rebuilt your systems. In addition, replacing and rebuilding is not as simple as it sounds and can take a long time before you have working systems again.

CIOs should also know that taking a backup is not the same as having a good working backup. Backup processes have a reputation for letting enterprises down when they need them most. If the recovery plan in based on backups only, CIOs should check regularly that backups are actually working and understand that they have only covered the first step and plan to be without working systems for typically around 3 to 7 days). Also, remember that if you want to guard against a disaster that physically destroys your machines, then your backups need to be off-site - well out of harm's way.

Swine Flu - DRP - BCP - CIO Issue

webmaster — Sat, 19 Sep 2009 11:51:08 -0600

What swine flu has done is reminded us all of the necessity to plan for threat scenarios that affect people more than they do data centers and other physical corporate facilities. Alternate work area facilities, mobile recovery units, and other workforce recovery strategies are not effective when people are home sick or there are travel bans in place. In these scenarios, your workforce recovery strategy must rely on remote access solutions or virtual workforce solutions.

Large numbers of employees out sick will affect the business (revenue) and cost your company a lot of money in productivity loss (you still pay employees their salary when they are out). In a recent Janco Associates survey, they asked over 300 DRP/BCP decision makers if their company had strategies for workforce recovery in their BCPs, 71% said yes. This means that 29% of you out there have a lot of work to do. Of the 71% that have strategies in place, 82% use remote access procedures as part of their strategy.

The US Center for Disease Control (CDC) has confirmed thousands of cases of swine flu in the United States and as other countries including Canada, New Zealand, the United Kingdom, Israel, Spain, and all of Europe has confirmed cases. This means health officials have confirmed that the disease can spread person-to-person and has the potential to cause "community-level" outbreaks.

IT disaster recovery is not necessarily business continuity. In addition there is a good chance that the plan is out of date and that it has not been exercised in a long time.

A plan walk through is no substitute for a more thorough exercise but it is a good place to start.

Validate the currency of the plan and the procedures.
Validate team member, roles, and responsibilities.
Understand what technology and services you currently have in place.

UK Pandemic system for disaster fails

webmaster — Thu, 20 Aug 2009 09:55:37 -0600

The UK Government has rolled out the National Pandemic Flu Service in England today. Scotland, Northern Ireland and Wales have decided to opt out of the service as demands in numbers are significantly less than that of England.

According to the BBC, the UK may have over 100,000 cases of H1N1 infection along with roughly 30 deaths as a result. The US is reported to have 40,000 cases with over 250 deaths. But because the flu pandemic has spread so far and wide, it is difficult to determine whether someones death is a direct result from swine flu, or whether the figures and statistics are accurate. There are simply too many cases and not enough resources being spent on data collection; some would say at least governments have their priorities right.

The National Pandemic Flu Service will be primarily a web based service, alongside a call center which will not be operated by health staff or qualified professionals to allow an "ease of burden on the NHS". It will act as a checklist service that algorithmically determines whether your symptoms are severe enough to require Tamiflu, the main anti-viral drug used to combat the illness.

Backup Window Must be Planned For

BackupWindow@e-janco.com — Sat, 01 Aug 2009 13:49:55 -0600

Rather than add more bandwidth, or invest in expensive, dedicated storage networks, WAN optimization can improve IP network performance sufficient to turn recovery into continuity. To help meet the objectives outlined above, a WAN optimization solution must be able to do three separate tasks for true business continuity: restrict bandwidth to backup applications during the allowed window and allocate it to critical applications in the event of a disaster, overcome latency and bandwidth limitations on the wire, and provide acceleration to roaming or displaced users redirected to alternative data sources.

Regardless of whether the data is being replicated from a massive cabinet, over IP-based storage or off a users hard drive for compliance purposes, during the backup window maximum bandwidth should be available to ensure completion. This requires granular bandwidth management that can isolate applications on the network and provide a predictable, policy-based service level. Further, the solution should be able to distinguish between a user initiated file copy and one started by the backup daemon, and apply different bandwidth allocations to each.

Also, the solution must remove latency and protocol inefficiencies that constrain current WAN backups. Caching and compression technology combined with inline protocol optimization of commonly used file transfer protocols form a technology suite that improves the performance characteristics of a WAN, adding bandwidth and reducing the time needed to complete backups and restores. Moreover, it should be able to do this for individual devices and accommodate displaced and roaming users without the need for bulky appliances.

What is the optimal method of back up for an enterprise's disaster recovery plan?

webmaster — Sat, 01 Aug 2009 13:49:36 -0600

The Backup and Backup Retention policy is an 11 page sample policy that is a complete policy which can be implemented immediately.

The document is provided in both Word 2003 and Word 2007 format and is easily modified.

*Solution*	*Benefit*	*Cost*
Local Backup	Shorter backup times Reduced bandwidth	More hardware and staff Security risks
Central Backup	Less hardware and staff	Increased bandwidth costs Increased backup times
Central Backup	Shorter backup times Reduced bandwidth Less hardware and staff	One-time technology investment

Roles in Developing a Disaster Recovery Plan

webmaster — Sat, 18 Jul 2009 10:06:48 -0600

The disaster recovery policy must be reviewed at least annually to assure its relevance. Just as in the development of such a policy, a planning team that consists of upper management, and personnel from information security, information technology, human resources, or other operations should be assembled to review the disaster policy. Roles and responsibilities of the planning team should be as follows:

Perform an initial risk assessment to determine current information systems vulnerabilities.
Perform an initial business impact analysis to document and understand the interdependencies among business processes and determine how the business would be affected by an information systems outage.
Take an inventory of information systems assets such as computer hardware, software, applications, and data.
Identify single points of failure within the information systems infrastructure.
Identify critical applications, systems, and data.
Prioritize key business functions.

The Disaster Recovery Plan Template has tools that can be used immediately and defined in detail all of these responsiblities and provides a work plan that can be use as is.

Questions to Ask About Your Disaster Plan

webmaster — Tue, 14 Jul 2009 06:43:09 -0600

Does your datacenter have the right procedures and equipment in place to recover your business from a disaster? Can your business survive extended downtime without your computing resources? Is your company prepared for a planned D/R event? What about an unplanned event? Who's in charge? Which technicians are driving the project?

A real disaster recovery effort is much different from a test.

People work around the clock in cramped quarters, getting very little sleep.
There often are too many people involved in the data cener leading to questions of who is in charge.
There are not sufficient LAN drops for the all the necessary technicians to be on the network simultaneously.
The equipment being using needs to be refreshed, so there is an equipment refresh along with a data recovery, which posed additional problems during the recovery.

Credit Card Processor Disaster

webmaster — Sat, 04 Jul 2009 08:24:02 -0600

Talk about a serious outage. Payment gateway service provider Authorize.net was down several hours. The service is used by tens of thousands of e-commerce vendors to accept credit card and electronic checks payments on their websites.

A fire in Seattles Fisher Plaza appears to be the reason what has taken down Authorize.net.

With its website down, Authorize has set up a new Twitter account to provide updates and address the many customer complaints and questions.

On July 2nd at approximately 11:10 pm, an incident in a garage-level electrical room disrupted power to Fisher Plaza East and knocked out the facility's backup generation system. The electrical room is where Fisher Plaza East receives its power from Seattle City Light. One of the services affected was Authorize.net, the largest credit card and e-check payment processor in the world, with tens of thousands of partners and processing millions of transactions on a daily basis. Authorize.net set up a Twitter account to keep its customers informed and transaction processing has been restored with a backup data center. ARB transactions will be rerun over the weekend thought there are still issues with CIM, VPOS and api.authorize.net.

Maximum Tolerable Period of Disruption (MTPOD) is an issue

webmaster — Sat, 06 Jun 2009 16:03:05 -0600

The concept of Maximum Tolerable Period of Disruption (MTPOD) is an issue with the introduction of British Standard 25999-2. When applied appropriately, MTPOD will improve management's understanding of your disaster recovery business continuity program and clarifies your enterprise's recovery priorities.

BS 25999-2, Section 4 says that the goal of a business impact analysis is to "determine the impact of any disruption of the activities that support the organization's key products and services." A key aspect of determining the impact of a disruption is identifying what BS 25999 calls the "Maximum Tolerable Period of Disruption," or MTPOD. BS 25999 defines MTPOD as the "duration after which an organization's viability will be irrevocably threatened if product and service delivery cannot be resumed." MTPOD is the maximum amount of time that the organization's key products or services can be unavailable or undeliverable before its stakeholders realize unacceptable consequences.

The full application of this concept can mean rethinking how a business impact analysis is approached. While many DRP / BCP professionals start a business impact analysis by gathering data from individual departments, MTPOD forces them to first look at products and services. Disaster Recovery and Business continuity professionals should understand downtime tolerance, taking into account:

Customer expectations
Regulatory requirements
Reputational issues
Financial and operational impairment
Strategic consequences.

Based on management input, disaster recovery / business continuity professionals can propose preliminary Maximum Tolerable Periods of Disruption for key products or services within the scope of the business continuity program.

Once MTPOD is established for key products and services, the traditional business impact analysis or service. From there, the business impact analysis can either validate or disagree with preliminary MTPOD conclusions. In addition, the business impact analysis does identify the department, function and process details that are needed to achieve the MTPOD.

Perhaps most importantly, the disaster recovery / business continuity professional must understand the amount of time required to perform the process or activity in order to deliver the product or service to its key stakeholders (internal or external). This is referred to as cycle time. For example, in a manufacturing company, cycle time would be how long it takes to obtain the necessary stock, manufacture the product, and deliver it to the customer.

With an understanding of MTPOD and cycle time, the business continuity professional can identify what is commonly accepted as the core output of the business impact analysis - the recovery time objective, or RTO. RTO is the point in time following a disruption when operations must resume (at a minimum level) in order to meet downtime tolerances.

Defining a Functional Disaster Recovery Business Continuity Plan

webmaster — Mon, 01 Jun 2009 12:17:10 -0600

What makes a truly functional disaster recovery business continuity solution is the ability to restore full systems and enterprise operations quickly, in a matter of hours or even minutes, using available computing resources, which may be local, but may also be remote.

True disaster recovery and business continuity plans must allow for recovery from site-wide disasters, such as a hurricane. The primary site may be completely down, due to a lack of power and network connectivity. The secondary site located in a non-affected area would be used to restore services until the primary site comes back online.

Many enterprises opt for remote Disaster Recovery Business Continuity site(s) for such scenarios. Many system administrators opt for virtual servers, which use asynchronous replication to replicate both the data and virtual machines to the secondary site, which has several standby servers. That way if they need to activate the secondary site, they just direct the activity to the virtual machines and all the systems are back up and running with the latest data.

Template Tools for CIOs

webmaster — Wed, 20 May 2009 10:20:51 -0600

Disaster planning is an essential component of preserving your institutions collections. With a written disaster plan, libraries, archives, museums, historical societies, and other collection-holding institutions can reduce the risk of disaster and minimize losses. dPlan is perfect for small and medium-sized institutions that do not have in-house preservation staff. dPlan is also valuable for large library systems or museum campuses that need to develop separate but related plans for multiple buildings, locations, or branches.

The Janco Disaster Recovery / Business Continuity Plan Template can help you create a plan for disaster prevention and response. This template will help you:

Prepare for the most likely emergencies,
Respond quickly to minimize damage if disaster strikes, and
Recover effectively from disaster while continuing to provide services to your community.

Google flops on its conversion to IPv6 from IPv4

webmaster — Sun, 17 May 2009 10:57:48 -0600

Google flops on its conversion to IPv6 from IPv4. Widespread outages involving several Google services--including search, Google Docs, and Gmail--were caused by an upgrade gone awry inside of Google, according McAfee. The outage began at 8:13 a.m. PDT, according to McAfee's data, and was fixed by 9:14 a.m. PDT. A senior manager at McAfee said that Google attempted to make changes to key Internet routing numbers--known as autonomous system numbers--as part of its ongoing transition from an older networking standard (IPv4) to a newer one called IPv6. An unknown "bug" inside Google's network prevented Internet service providers from finding Google's new ASNs on the Internet--effectively blocking its services.

Not all Internet users were affected, but some that use larger providers--such as AT&T or Verizon--appeared to be disproportionately hurt because large ISPs "peer" with Google, or interconnect their networks with Google's networks in order to improve speed and reduce bandwidth costs. Not all customers at those providers were affected, and smaller ISPs that did not interconnect their networks were able to route around the problem.

Mid-Sized Firms are at Risk When Disasters Occur

webmaster — Fri, 17 Apr 2009 16:32:30 -0600

Many firms are inadequately protected and mistakenly think that a disaster is rare and won't happen to them anytime soon.

SMBs prioritization of disaster recovery, backup and high availability for 2008 shows that businesses understand the risks to their business and the value of protection. However, many organizations still errantly think that backup is a sufficient disaster recovery plan. But, mid-sized enterprises are at the most risk to disaster and are more likely to rely strictly on backup as a disaster recovery plan.

The needs and resources of mid-market firms are unique. Midsized companies must work with limited finances infrastructure and human resources. Robust disaster recovery used to be affordable and manageable only by large enterprises. Mid-sized enterprises relied more on backup than on a formal disaster recovery plan. As businesses' reliance on IT has grown, backup has increasingly shown its weaknesses. However, the introduction and maturation of several key technologies, such as virtualization, have brought affordable and easily implementable disaster recovery to small and mid-sized companies. SMBs do not always equate virtualization with disaster recovery because awareness of the many virtualization applications is just starting to grow.

Project plan for developing and maintaining a Disaster Plan

webmaster — Tue, 14 Apr 2009 13:48:24 -0600

There are a number of approaches that have been used by Jancos clients to create a Disaster Recovery / Business Continuity Plan. One, which several have used, is to start with the Janco Disaster Recovery Business Continuity Template and implement a seven-step process (a subset of the project plan which is included in the template) using the tools included with the template. The process is as follows:

Develop the contingency planning policy statement. A formal department or agency policy provides the authority and guidance necessary to develop an effective contingency plan.
Conduct the business impact analysis (BIA). The BIA helps to identify and prioritize critical IT systems and components.
Identify preventive controls. Measures taken to reduce the effects of system disruptions can increase system availability and reduce contingency life cycle costs.
Develop recovery strategies. Thorough recovery strategies ensure that the system may be recovered quickly and effectively following a disruption.
Develop an IT contingency plan. The contingency plan should contain detailed guidance and procedures for restoring a damaged system.
Plan testing, training and exercises. Testing the plan identifies planning gaps, whereas training prepares recovery personnel for plan activation; both activities improve plan effectiveness and overall agency preparedness.
Plan maintenance. The plan should be a living document that is updated regularly to remain current with system enhancements.