By Joe Wolke

Today, businesses are facing greater change than ever before. Fortunately, they also have choices they’ve never had before… and the choices they make can and should be based on business objectives and cost optimization.

When the bridge in Minneapolis/St. Paul tragically collapsed, the country focused on its dangerously aging infrastructure; it seemed the time had come to really address this issue. But years later, many bridges with the same problems still stand, unimproved.  No other major collapses have occurred... But is it just dumb luck? Of course. The problem is just too big and expensive to easily solve.

Businesses do the same with IT. The cost to upgrade the existing model to meet current and future needs is so great that companies are doing what they can to eke another year out of hardware through low quality maintenance, or in some cases, a wish and a prayer.

By Scott Van Dyke

The terminology recovery point objective (RPO) and recovery time objective (RTO) are commonly used to plan how to best protect data and applications around disaster recovery scenarios. For proper disaster planning, a business determines the maximum acceptable level of data loss following an unplanned event that could result in data loss (RPO). A responsible business will also determine the maximum amount of time they can tolerate without their critical applications (RTO). The primary focus RPO and RTO is to plan how to best protect your critical applications and data in the event of a disaster.

One often overlooked area that impacts a business is what happens to the critical applications and data for a business when performing a server migration. A server migration typically arises for one of the following reasons: