The 2 most important considerations in server migration

Win2k3Workloads are your company’s lifeblood. Physical servers, virtual machines (VMs), or a combination of both are running Microsoft Exchange, SharePoint, and various other applications. Inevitably the time will come to migrate these workloads to different hardware or VMs.

For organizations running Microsoft Windows 2003, that time is coming soon. These companies will need to migrate those servers to a new operating system before Microsoft ends support in July of this year. Migrating workloads from one server to another can be difficult, whether from one version of an operating system on a physical server to a newer version on a physical server, from a physical server to a virtual server, or from one hypervisor platform to another.  Application and version compatibility issues, network connectivity, and authentication and security problems can present challenges during a migration. Many organizations conducting a migration experience one of these situations; a recent survey conducted by IDC found 48 percent of companies run both physical and virtualized servers, and 54 percent of companies run more than one hypervisor in their environment.

This is especially true when moving a production workload to a new OS environment when it is intimately linked to the current environment. The two most critical steps in every migration are effectively backing up a full log of the data, and using the right tools to conduct the actual migration. Full image backups ensure all data – content and application settings, for example – can safely be migrated, and universal migration tools can simplify the actual process so it’s as easy as it is effective.

If done incorrectly, organizations can lose data, extend downtime, miss revenue opportunities, and adversely affect customer service perceptions – not to mention the long, hectic extra hours it takes to fix the problem. Continue Reading…

Tags: , , , , , ,