

Notice that my vSphere-WahlNetwork environment is using a proxy called JUMP1. You can pass credentials to CMC to discover VMs in the source environment(s) or even set up a proxy server inside of a private vSphere deployment to circumvent NATs and reveal private IPs. This will allow me to perform migrations on my Windows VMs that live in either vSphere or AWS and move them over to Azure. I’ve added four environments to my CMC portal below: a source environment for both VMware vSphere and Amazon AWS, and two target environments within Microsoft Azure. And, since I have environments in most of the major clouds, it seemed like a good idea to connect them into the CMC dashboard and see how they appeared. I asked the team for a handful of licenses so I could tinker around with the Cloud Migration Center interface. I’m a fan of releasing a small number of working features to start, and then adding more features within quick iterations, rather than trying to build every bell and whistle into the initial release. The benefit, however, is that the product is operational today and should include a greater choice in source and target environments in the future.

Target environments are limited to Microsoft Azure.Source environments are limited to VMware vSphere and Amazon AWS.There are a few restrictions that are coupled with the release: With CMC, that’s no longer necessary – you use the web interface to perform all these tasks and gain visibility into the health, status, and controls of the product. For those new to Double-Take, you typically install a Double-Take Console somewhere within an environment to add source and target servers, control replication, and monitor failover. This is a SaaS based front-end that abstracts away all of the Double-Take back-end infrastructure while also providing a slew of cloud source and target destinations for migrations, disaster recovery, and application protection. 🙂Ī few weeks back, Vision Solutions announced their next iteration with the release of Cloud Migration Center. Oh, and a Physical-to-Virtual (P2V) migration of a GreatPlains (Great Pains) box on Windows Server 2000 that was permanently stuck in the “ soon to be decommissioned but it never quite happens” status. It enabled me to quickly get virtual servers off the prohibitively high cost of monthly maintenance and then address platform migrations at a later date. I’ve personally used Double-Take Availability to migrate several hundred physical machines out of a co-location and into a private data center when I worked in the customer side with great success. The product comes in many different flavors depending on your use case, such as Double-Take Move for one-time migrations using source-based licensing keys and Double-Take Availability to set up more permanent replication between servers to protect an application. Double-Take is an excellent stack of migration, replication, and availability software owned by Vision Solutions.
