You are here: Data migration > Cutting over data migration jobs

Cutting over data migration jobs

When the migration mirror has completed, the migration job may or may not terminate automatically depending on your selection for Wait for user intervention before cutover. If you disabled user intervention, the migration job will automatically terminate to complete the migration process. If you enabled user intervention, when the migration mirror is complete, the status will change to Protecting. Use this time to complete any necessary tasks. When you are ready to complete the migration, use the following instructions to cutover.

On the Manage Jobs page, highlight the job that you want to cutover and click Failover or Cutover in the toolbar.
Select the type of cutover to perform.

Cutover live data—Select this option to initiate a full, live cutover using the current data on the target. The source is automatically shut down if it is still running.
Perform test cutover—This option is not applicable to data migration and full server migration jobs.
Cutover to a snapshot—This option is not available for migration jobs.

Select how you want to handle the data in the target queue. You may want to check the amount of data in queue on the target by reviewing the Statistics or Performance Monitor.

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.

IPv6 addresses on the source will be set to DHCP on the target after cutover. Update them to static addresses manually, if needed.

If your NICs were configured for network load balancing (NLB), you will have to reconfigure that after cutover.

If your source was disconnected from the network during the cutover process, the original job that was mirroring the data will still be active on that machine. Do not bring that machine back on the network. If you do, the original job will attempt to begin mirroring data again which could result in data loss. While the machine is still disconnected from the network, stop the Double-Take service, delete the file connect.sts located in the Double-Take installation directory, and then restart the Double-Take service. This will delete the original job. After the original job is deleted, you can bring the machine on the network if desired.

If you selected share cutover during your data migration job creation, Double-Take will mirror and replicate data from your source shares to the target. During cutover, these shares will be added to the target. Keep in mind that additional steps may be needed after cutover to redirect users and/or applications to the shares on the new server. For example, you may need to rename the new server to the same name as the original server or you may need to update login scripts for the new server name.