Data Processing Recovery (46)
To implement an effective disaster recovery program, planners and technical staff must consider the full range of possible disaster events and the extent to which each event can interrupt business operations and damage corporate data. Some disasters are confined to a single user's desktop, while others affect entire geographic regions. The data protection technologies currently available vary greatly in their ability to protect organizations from specific disaster types.
Traditional data protection tech-nologies, such as tape backup and fault-tolerant storage devices, protect business data from failures and human errors that can damage individual devices or buildings. However, corporate data is vulnerable to site- and region-wide disasters even if tape backup and RAID devices are both in place. Network data mirroring complements these traditional backup methods by protecting organizations from events that can destroy fault-tolerant storage devices. If your organization risks losing valuable time or business information due to wide-area disasters, network data mirroring may be a wise technology addition to your disaster recovery program.
With the increasing reliance on today's computer systems and networks for the day to day running of businesses, there is an imminent threat to business continuity. Computer systems can be affected by a variety of sources, power outages, water leaks, systems failures, etc. Most companies have some sort of backup system in place, example UPS for power failure, but fail to take into account other hidden factors.
It is no longer a question if you will experience system or environmental failures, but when. The 10 question quiz that follows can assist in assessing your company's risk of experiencing downtime due to system or environment failures.
State of the Industry - the Impact of Disaster on Businesses
As the information revolution evolves, corporate executives are becoming more concerned with ensuring their operations are available when their customers want them, guaranteed. Many believe that technology performance will be the key success factor for businesses in the future. This implies that organizations may need to consider production environments that have no single points of failure, that react instantaneously to interruptions in service.
In short, the successful businesses must target a technology environment which can be relied on 24 hours a day, seven days a week, 52 weeks a year. But what if that interruption is a catastrophic disaster? How can a company guarantee continuous operations in the event of a disaster and what is the impact on the recovery environment if a disaster should occur?
In the last decade, there have been numerous local and regional disasters that have affected business in the United States. The impact on the business community has been significant. Statistically, it has been reported that 43 percent of the companies experiencing a disaster never re-open, and an additional 29 percent close within two years. Seventy-five percent of businesses who lose computer support are no longer able to conduct business functions after only two weeks.
Before a business can determine the most appropriate recovery environment, executives must conduct a Business Impact Analysis (BIA) to determine the real hard dollar loss it would expect to incur should they be unable to conduct business over a period of time. This will help shape their recovery requirements and help them weigh the cost of recovery against the risk of a disaster and the impact on the survival of the business.
How well do you sleep?
Nearly four thousand years ago King Solomon wrote 'Have no fear of sudden disaster or of the ruin that overtakes the wicked' Proverbs 3:25, NIVi. King Solomon preserved sound judgment and discernment in the management of his kingdom. Can you sleep with the confidence that King Solomon enjoyed? ( I am referring, of course, to your capability to continue your business through a disaster episode.)
This article focuses on what I shall designate 'Tactical Computing', that is non-mainframe in the broadest sense ( condensed for brevity from a plethora of terms, including: Client/Server, Network Computing, Distributed, Open, Multiplatform, Desktop, PC/LAN, Multi-Platform, Minicomputer and Enterprise Computing. This article also applies to the burgeoning SOHO computing arena (Small Office Home Office).
A case study in wacky data recovery
I heard a true story of a manager, let's call him Joe for the sake of anonymity, who employed a wacky, but effective data recovery technique. It seems that the hard drive on Joe's PC crashed. Sound like a familiar story? Fortunately, Joe believed in tape backups. Alas, his most recent backup tape was an antique, two months old. What was Joe's ingenious recovery strategy? Joe decided to broadcast an e-mail to all recipients of his e-mails and files within the last two months, (a lot of folks, you might expect). His message said that each one should forward all of Joe's previous e-mail and attachments back to him, so that Joe could restore as much valuable data as possible. Pretty clever, eh? But how did Joe get there in the first place? Weak business continuity strategy was the culprit.