< ? php //If there is analytic campaign data, attempt to get the campaign_guid from that cookie if ( 1 === preg_match( '/pk10mkto-([0-9]+)/', $_COOKIE[ '__utmz' ], $match ) ) { $campaign_guid = $match[ 1 ]; } ?>

Five Workload-to-Cloud Migration Methods: Part 6

January 6, 2014

Full server failover from the original operating system environment into the cloud using software agents

This is the final of six-post series about migration to the cloud the subject.

Last week, we used software agents to install the application environment on top of the OS running on the target system. This time, we are capturing everything installed and configured on the source system and moving it in its entirety to the CSP. Depending on the scale of the migration, you can replicate to a shell VM, agent to agent or to an aggregated target such as a VM appliance.

There are many similarities between to two methods. Both allow you to migrate heterogeneous environments, such as Xen to VMware or Amazon to Peak 10. They are non-disruptive to the production environment, replicating over time without bringing systems down for prolonged periods. The server image replication moves at a controllable pace…slowly during heavy Internet use and full speed during off-hours when no one will be bothered by slow connections. You can stop and test at any point in the process, as many times as you want until the target site is completely in synch with the source. Minor latency caused by network and distance is irrelevant. The risks are similar such as insufficient bandwidth at both ends.

A key difference is that the target server is a complete duplicate of the source server. No rebuilding or reconfiguring or dependencies should be expected. No worries about missing installation media or configuration work-arounds. The complete server package is there. Double Take software is a reliable software agent for this.

Another difference is that it may cost more. In addition to the software and skilled technicians, the cloud services provider (CSP) may have to provide temporary resources in order to do the migration, such as an operating system shell and an adequately sized data volume during the failover process.

This method is particularly good for large numbers of servers, and it scales well.


This concludes our blog series, Five Workload-to-Cloud Migration Methods. We hope this has helped you to evaluate and choose a workload migration method best suited to your needs.

Peak 10 would welcome the opportunity to help guide you through this process, as well as to become your preferred CSP.

Fine tune your content search

About Peak 10

"Our values are the foundation for everything we do at Peak 10, and are ultimately what enable us to earn our customers' business and their trust."
David H. Jones,
Board Member, Peak 10 + ViaWest