Planned downtime: How your disaster recovery solution can reduce costs and shrink outage Windows (page 2 of 2)

These planned, automated operations can carry out the migration with virtually no impact to service levels and allow users to continue to access their data and application without incurring the downtime normally associated with the migration of applications.

Scenario Two: Upgrading Microsoft Exchange. You're running Exchange in a non-clustered, non-automated environment, and you need to upgrade the system with a new service pack. You are forced to shut down the server and turn off all your users, cutting off access to arguably their most critical application. You then have to load in the new service pack, load in the new application, point the application to the data, and redirect your clients to the new server.

If on the other hand, you're running Exchange in a clustered environment, performing upgrades has minimal impact on users. With automated clustering and volume management tools, copying the data to available disk and migrating the Exchange application service to another server within the cluster is a push-button operation saving hours of downtime.

Scenario Three: Server Consolidation. You have a number of standalone systems in your environment that are not generating the ROI they could. The decision is made to bring in a new class of server and storage hardware that can be configured with multiple domains.

Using the clustering technology that you acquired as part of your availability solution, you simply add each standalone system to the new cluster and execute a migration command to move the application over.

Your consolidation ratio is 12:1 (in this hypothetical case), and you wind up with a much smaller footprint for those applications, translating to higher reliability and availability. You can perform the same amount of work with fewer servers and reduce your hardware and maintenance costs.

Scenario Four: Performance-Based Migration. You have applications running in an environment where performance is degrading. The time required to process a transaction, to respond to a Web-page click, has reached the point where your monitoring software is sending alerts.

Your disaster recovery solution includes a cluster server and cluster file system that enable you to migrate the applications, permanently or temporarily, to systems that are better able to handle the service. The process is automated. There is no need to do a restart on the new node. You eliminate downtime while maintaining application performance.


Looking at the Bottom Line: Speed, Efficiency and Cost Reduction
The clustering, replication and volume management tools that make up an effective high availability/disaster recovery solution for many companies can contribute handsomely to ROI when they do double duty as facilitators of planned downtime projects.

One obvious benefit is that they are already in place at most companies. No additional expenditure is necessary.

Another powerful benefit is that these tools automate procedures, reduce administrative costs, increase efficiency and eliminate the possibility of error. Many highly automated routine procedures can be initiated remotely by administrators or run as timed events at night.

The most significant benefit, however, is the ability of these tools to reduce downtime to a matter of seconds. Using stateful migration technologies, users can be migrated to another set of systems without the need for them to reconnect, thereby significantly reducing the downtime associated with planned maintenance. The connection is persistent, and the state of the application is maintained, even for users who were conducting transactions.

Unforeseen events and site outages will happen. However, clustering, replication and volume management technologies can be leveraged to ensure the availability of data and applications, minimize the impact of failures on the business and ultimately align IT with business operations while significantly increasing the enterprise's ROI.