Migrate workloads to Cloudist VDC using Carbonite Migrate
Introduction
Migration using Carbonite Migrate (formerly known as DoubleTake) can move any Windows or Linux workload from any environment to Cloudist VDC, making the underlying hardware, hypervisor or cloud platform irrelevant.
Prerequisites
Contact sales@cloudist.se and request a license for Carbonite Migrate (charges will apply)
Installation media downloaded to source and target machines (available here Carbonite)
Networking connectivity is needed between source and target environments. A general recommendation is to setup a IPSec VPN tunnel between the sites similar to the image below, to secure the data transported between source and target.
Procedure
Installation
Install Carbonite Migrate on both target and source using installation media provided above.
Normally, a default setup is working fine in most environments, but firewalls might need to be opened to allow traffic over the specific TCP ports that Carbonite require (6320, 6325, and 6326) between source and target.
License keys
1. This key is your delivered key and should be installed on source machine
2. This key is generic and should be installed on target machine
Once you have entered the license keys, it should look similar to this (from the Target Server console)
Job setup
The settings below should be considered and adapted to your specific needs.
Normally, its recommended to do Job Setup from Carbonite console on Target server.
For full detail see https://download.doubletake.com/_download/Documentation/8.5/8.5.9.0/Migrate/Windows/MigrateWindowsUsersGuide.htm
Failover options
Wait for user to initiate failover: The cutover process can wait for you to initiate it, allowing you to control when cutover occurs. When a cutover occurs, the job will wait in the Protecting state for you to manually initiate the cutover process. Disable this option if you want cutover to occur immediately after the mirror is complete.
Shutdown source server: Specify if you want to shut down the source server, if it is still running, before the source is cutover to the target. This option prevents identity conflicts on the network in those cases where the source and target are still both running and communicating.
Failover identity
Apply source network configuration to the target - If you select this option, you can configure the source IP addresses to cutover to the target. If your target is on the same subnet as the source (typical of a LAN environment), you should select this option. Do not select this option if you are using a NAT environment that has a different subnet on the other side of the router.
Retain target network configuration - If you select this option, the target will retain all of its original IP addresses. If your target is on a different subnet (typical of a WAN or NAT environment), you should select this option.
Compression
To help reduce the amount of bandwidth needed to transmit OpenText Migrate data, compression allows you to compress data prior to transmitting it across the network. In a WAN environment this provides optimal use of your network resources. If compression is enabled, the data is compressed before it is transmitted from the source. When the target receives the compressed data, it decompresses it and then writes it to disk. You can set the level from Minimum to Maximum to suit your needs.
Keep in mind that the process of compressing data impacts CPU usage on the source.
Bandwidth
Choose an option that fits your networking environment
Do not limit bandwidth—OpenText Migrate will transmit data using 100% bandwidth availability.
Use a fixed limit—OpenText Migrate will transmit data using a limited, fixed bandwidth.
Use scheduled limits—OpenText Migrate will transmit data using a dynamic bandwidth based on the schedule you configure. Bandwidth will not be limited during unscheduled times.
Before cutover
Things to consider on the source machine before failing over
Consider disabling Windows Update while replicating as this might cause remirror operations in Carbonite Migrate.
Cutover
When the migration mirror has completed, the target may or may not reboot automatically depending on your selection for user intervention. If you disabled user intervention, the target will reboot automatically to complete the migration process. If you enabled user intervention, when the migration mirror is complete, the status will change to Protecting
On the Jobs page, highlight the job that you want to cutover and click Failover or Cutover in the toolbar.
Cutover to live data—Select this option to initiate a full, live cutover using the current data on the target. The source may be automatically shut down if it is still running, depending on your job configuration. The target will stand in for the source by rebooting and applying the source identity, including its system state, on the target. After the reboot, the target becomes the source, and the target no longer exists.
Select how you want to handle the data in the target queue.
Apply data in target queues before failover or cutover—All of the data in the target queue will be applied before cutover begins. The advantage to this option is that all of the data that the target has received will be applied before cutover begins. The disadvantage to this option is depending on the amount of data in queue, the amount of time to apply all of the data could be lengthy.
Discard data in the target queues and failover or cutover immediately—All of the data in the target queue will be discarded and cutover will begin immediately. The advantage to this option is that cutover will occur immediately. The disadvantage is that any data in the target queue will be lost.
When you are ready to begin cutover, click Cutover.
After cutover
To make the target machine ready to be used, there are some things to consider
Uninstall hypervisor specific tools from source platform, like VMware Tools, QEMU Tools etc
Contact Cloudist Support (support@cloudist.se) and ask them to add their Microsoft SPLA license key for Windows to the target machine.
Install VMware or QEMU Tools, suitable for target platform.
Add backup if that is required
Monitor machine performance and adjust resources accordingly.
Product documentation and guides
See following documentation for detailed capabilities and limitations
See following documentation for detailed networking requirements
Watch video on installation process
Watch video on migration process