Transparent operation will be relatively straightforward in file-oriented systems where communications latency is unimportant. However, commercial relational database management systems (RDBMSs) will require certain modifications. RDBMSs currently suffer significant performance degradation due to the communications latency experienced when remote operations exceed 100 miles when replicated in synchronous mode. The latency issue arises when the primary site awaits a commit from the secondary site before continuing. Therefore, RDBMS vendors must develop capabilities that support remote operations while maintaining transactional integrity (2005/06). Moreover, these databases must support instant failover between sites with non-active/active clustered systems (2005/06).

Organizationally critical data shares many of the same characteristics as mission-critical data, with the exception that it does not require the same time-based recovery service level. The main difference is that organizationally critical data typically does not demand synchronous operation; asynchronous is sufficient. However, given the likely cost reduction of bandwidth and the probable capabilities of the RDBMS, the distinction will be immaterial by 2008.

[an error occurred while processing this directive]

Although most organizations consider end-user systems and data to be non-critical in nature, the destruction of the World Trade Center and damage to the Pentagon highlighted the fact that, in many cases, data on laptops can be organizationally critical. ITOs have been reluctant to include end-user systems in their data protection strategy, largely because the ITO has little control over how those systems are backed up and because of the incremental personnel cost to include another 10,000 systems in larger organizations. However, by 2004, we expect most ITOs to assume control of protecting the data on end-user systems and for providing a recovery mechanism for those systems.

Because end-user systems are usually outside the data center, DR plans typically do not include these systems. However, companywide loss of this data could nearly halt business operations just as certainly as could the loss of key applications. Therefore, the typical methods used by most organizations to protect desktop and laptop systems (e.g., Iomega Zip devices, replication to a LAN server) are insufficient to protect the organization from the loss of an entire site. This data should be replicated or moved to a remote site (either via disk or tape) using a commercially available management product (e.g., Veritas NetBackup Professional, Connected TLM, CA BrightStor Mobile Backup). Generally, time to recovery is not the critical issue for user data. Although the recovery of this data can be measured in days, its recovery must be ensured to avoid loss of significant intellectual property.

Security must not be overlooked in the context of disaster recovery. DR operations can open one critical back door that most organizations overlook. DR tapes usually include everything necessary to re-establish the system (e.g., operating system, application, data). Not all backup and recovery (B/R) software contains sufficient security mechanisms to prevent these DR tapes from being loaded on unauthorized systems. There may be no security at all, or the security may be limited to the idea that the system must be licensed for the B/R software. However, B/R software vendors routinely make fully functional demonstration versions of their software available on the Web, making this "security" none at all. It is imperative that ITOs verify that their B/R software not contain this breach, and verify it for themselves.

Business impact: A comprehensive portfolio approach to data recovery fosters "transparent recovery" of critical applications from nearly any contingency.

Bottom line: ITOs should develop a "recovery management portfolio" to cover all failure contingencies, from user error to data center loss, to ensure business continuity.

Is your organization taking steps toward safe, secure disaster recovery? Post your thoughts in our Talkback forum below.

Previous page |   1 2

Newsletters
	Tech Update Today eBusiness Update	Tech Update Weekly		All newsletters FAQ Manage my newsletters

[an error occurred while processing this directive]

[an error occurred while processing this directive]