Notices Carbonite Cloud Migration User's Guide, Thursday, March 22, 2018 If you need technical assistance, you can contact CustomerCare.

Transcription

1

2 Notices Carbonite Cloud Migration User's Guide, Thursday, March 22, 2018 If you need technical assistance, you can contact CustomerCare. All basic configurations outlined in the online documentation will be supported through CustomerCare. Assistance and support for advanced configurations may be referred to a Pre-Sales Systems Engineer or to Professional Services. Man pages are installed and available on Carbonite Move Linux servers. These documents are bound by the same Carbonite license agreement as the software installation. This documentation is subject to the following: (1) Change without notice; (2) Furnished pursuant to a license agreement; (3) Proprietary to the respective owner; (4) Not to be copied or reproduced unless authorized pursuant to the license agreement; (5) Provided without any expressed or implied warranties, (6) Does not entitle Licensee, End User or any other party to the source code or source code documentation of anything within the documentation or otherwise provided that is proprietary to Carbonite, Inc.; and (7) All Open Source and Third-Party Components ( OSTPC ) are provided AS IS pursuant to that OSTPC s license agreement and disclaimers of warranties and liability. Carbonite, Inc. and/or its affiliates and subsidiaries in the United States and/or other countries own/hold rights to certain trademarks, registered trademarks, and logos. Hyper-V and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark of Linus Torvalds. vsphere is a registered trademark of VMware. All other trademarks are the property of their respective companies. For a complete list of trademarks registered to other companies, please visit that company s website Carbonite, Inc. All rights reserved.

3 Contents Chapter 1 Carbonite Cloud Migration overview 5 Configurations and ports 6 Chapter 2 Requirements 10 Source requirements 11 Target requirements 15 Target requirements for Amazon Web Services 16 Target requirements for custom environments 17 Target requirements for Microsoft Azure Classic 19 Target requirements for Microsoft Azure Resource Manager 20 Registering and assigning owner role in Microsoft Azure Resource Manager 21 Target requirements for OpenStack 28 Target requirements for VMware vcloud Director 29 Target requirements for VMware vsphere 31 Proxy requirements 32 Carbonite Cloud Migration interface requirements 33 Chapter 3 Getting started 34 Chapter 4 Carbonite Cloud Migration interface 35 Configuration 37 Chapter 5 Environments 38 Creating an Active Directory environment 41 Creating an Amazon Web Services environment 43 Minimum permissions for Amazon Web Services 44 Creating a custom environment 46 Creating a Microsoft Azure Classic environment 47 Creating a Microsoft Azure Resource Manager environment 49 Creating an OpenStack environment 51 Creating a VMware vcloud Director environment 52 Creating a VMware vsphere environment 54 Proxy server 55 Chapter 6 Servers 56 Discovering servers in non-custom environments 58 Discovering servers in custom environments 59 Viewing server details 61 Chapter 7 Migrations 62 Migrating to Amazon Web Services 64 Migrating to a custom environment 69 Migrating to Microsoft Azure Classic 73 Migrating to Microsoft Azure Resource Manager 78 Migrating to OpenStack 83 Migrating to VMware vcloud Director 87 Migrating to VMware vsphere 92 Viewing migration details 97 Viewing migration history 98 Contents 3

4 Chapter 8 notification 99 Chapter 9 Account management 100 Contents 4

5 Chapter 1 Carbonite Cloud Migration overview Carbonite Cloud Migration is an online service that enables migrations of Windows and Linux servers to a public or private cloud. Using only a few clicks in Carbonite Cloud Migration, you can easily automate server migrations for a secure, near-zero downtime experience. There are four main components to Carbonite Cloud Migration. Source The server you want to migrate is called your source server. The source server can be a physical or virtual server on the ground or in a cloud. Target The new server you are migrating to is called the target server. The target server is a virtual server and it can be hosted on the ground or in a cloud. Carbonite Cloud Migration This is the online service that enables the migration of the source to the target. Proxy If your source or target does not have a public IP address, you will have to use a proxy server. See Configurations and ports on page 6 for details and diagrams of how to configure Carbonite Cloud Migration. Chapter 1 Carbonite Cloud Migration overview 5

6 Configurations and ports The flexibility of private and public accessibility allows for many different Carbonite Cloud Migration configurations, including whether a proxy server is needed. If your source or target does not have a public IP address, you will have to use a proxy server. Even though migration data is encrypted, you may need to consider private and public accessibility between your source and target for the migration of the data. There are different port requirements depending on the configuration you are using. Source configurations Your source environment will have the source server and optionally cloud services or a hypervisor, depending on your configuration. Chapter 1 Carbonite Cloud Migration overview 6

7 Target configurations Your target environment will have the target server and cloud services or a hypervisor, depending on your configuration. Chapter 1 Carbonite Cloud Migration overview 7

8 Source to target configurations Even though migration data is encrypted, you may need to consider private and public accessibility between your source and target for the migration of the data. Sample configuration Any combination of the configurations above is possible. For example, if you are migrating from cloud to cloud and your source and target both have private IP addresses, your configuration would look similar to this. Chapter 1 Carbonite Cloud Migration overview 8

9 Ports The colored arrows correspond to the configuration diagrams above. Component to Component Windows Communication Linux Communication Arrow Color Web Browser to Carbonite Cloud Migration Carbonite Cloud Migration to Cloud or Hypervisor Service HTTPS port 443 Proxy Server to Cloud or Hypervisor Service Proxy to Carbonite Cloud Migration Service Bus (outbound only) port 9354 SignalR port Proxy to Source Proxy to Target Carbonite Cloud Migration to Source Carbonite Cloud Migration to Target Source to Target SMB port 445 WinRM ports 5985 and 5986 Carbonite Move port 6325 Carbonite Move ports 6320 and 6325 SSH port 22 Carbonite Move port 6326 Carbonite Move ports 1500, 6325, and 6326 Chapter 1 Carbonite Cloud Migration overview 9

10 Chapter 2 Requirements Review the separate requirements sections for details on the requirements for your source servers and source infrastructure, your target servers and infrastructure, your proxy server if you are using one, and for the Carbonite Cloud Migration service and interface. Source requirements on page 11 The servers you are migrating have specific requirements including operating system and configuration of the source servers. There are also requirements for the infrastructure where the source servers are located, networking, and other specifications. Target requirements on page 15 In addition to general target requirements, you must meet requirements specific to the target cloud infrastructure you are using. Proxy requirements on page 32 If your source or target does not have a public IP address, you will have to use a proxy server for Carbonite Cloud Migration communication. Carbonite Cloud Migration interface requirements on page 33 The Carbonite Cloud Migration is the online service and interface that you use to execute and manage the migration. You must meet the specific requirements to use the service. Chapter 2 Requirements 10

11 Source requirements The source servers you are migrating, and the infrastructure where the source servers are located, must meet the following requirements. Infrastructure The source servers must be running in one of the following supported infrastructures. Active Directory Local networks running Active Directory are supported. Carbonite Cloud Migration will query the Active Directory service in order to identify servers that you can migrate. In a domain environment, Carbonite Cloud Migration (or a proxy server) must be able to resolve the domain name and connect to the domain controller using port 389. Amazon Web Services (AWS) You must have an access key and secret key in order to use Amazon Web Services. Custom This environment type is a manually created environment when your servers are not in any of the other infrastructures. Servers can be discovered using a range of IP addresses or an IP address and subnet mask. The servers must be able to respond to a ping request. You can also manually add servers to the environment by a single IP address or name. If you specify a computer name, Carbonite Cloud Migration (or a proxy server) must be able to resolve the computer name for the IP address. VMware vcloud Director You must have a version of vcloud Director that is currently supported by VMware. You must know the vcloud IP address or hostname as well as the organization within vcloud that you have access to and want to use. You must have credentials that can access vcloud. VMware vsphere You must have a version of vsphere that is currently supported by VMware. You must know the vsphere IP address or hostname and have credentials to access it. Operating system The source servers must be one of the following Windows or Linux operating systems, with supported file system and kernel type. Make sure your operating system is also supported on the target cloud you are migrating to. Operating System Version File System Kernel Type for 32-bit Architectures Kernel Type for 64-bit Architectures 2008 R2 Service Pack 1 or later Windows * 2012 NTFS Not applicable 2012 R2 Red Hat Enterprise Linux Oracle Enterprise Linux ** CentOS 5.9 through 5.11 Ext3 Ext4 XFS Default SMP Xen PAE Default SMP Xen Chapter 2 Requirements 11

12 Operating System Version File System Kernel Type for 32-bit Architectures Kernel Type for 64-bit Architectures Red Hat Enterprise Linux Oracle Enterprise Linux CentOS 6.6 through 6.8 Ext3 Ext4 XFS (64-bit only) Default Red Hat Enterprise Linux Oracle Enterprise Linux CentOS 7.0 through 7.2 Ext3 Ext4 XFS No 32-bit architectures are supported Default Default SUSE Linux Enterprise 11.2 through 11.4 Ext3 XFS Xen XenPAE Default Xen VMI SUSE Linux Enterprise 12.0 through 12.1 Ext3 Ext4 XFS No 32-bit architectures are supported Default Ext2 Ubuntu Ext3 Ext4 Generic XFS * A Windows source server cannot be a Hyper-V server. Migration of a Hyper-V server is not supported. ** Support is for the mainline kernel only, not the Unbreakable kernel. For all Linux operating systems except Ubuntu, the kernel version must match the expected kernel for the specified release version. For example, if /etc/redhat-release declares the system to be a Redhat 6.6 system, the kernel that is installed must match that. Stacking filesystems, like ecryptfs, are not supported. Chapter 2 Requirements 12

13 Linux packages and services Each Linux server must have the following packages and services installed before you can install and use Carbonite Cloud Migration. See your operating system documentation for details on these packages and utilities. sshd (or the package that installs sshd) lsb parted /usr/bin/which /usr/sbin/dmidecode /usr/bin/scp SELinux policy SELinux must be disabled on your Linux servers. UEFI, trusted boot, secure boot UEFI, trusted boot (tboot), secure boot, or other volume blocking mechanisms are not supported on your Linux servers. LVM Linux servers can have LVM, however, the LVM mapping will not exist on the target after migration. Amazon Web Services is the exception with LVM. If your source is a Linux server with LVM, you cannot migrate to AWS. System memory At least 1 GB of memory is required on the source servers. Server name Unicode file system support is included, but the source name must still be in ASCII format. If you have the need to use a server's fully-qualified domain name, your server cannot start with a numeric character because that will be interpreted as an IP address. Additionally, all source servers in your environment must have a unique server name. Source to target communication A VPN is required if your source and target cannot communicate together in both directions. Source to Carbonite Cloud Migration communication If your source does not have a public IP address, you will have to use a proxy server for source to Carbonite Cloud Migration communication. If you are using a proxy server, it must be run on Windows 2012 or 2012 R2. You can also run it on Windows 2008 R2, but you must install PowerShell version 4.0 or later to use this operating system. Do not install the proxy server on your source server. See Proxy server on page 55 for more details. Windows Remote Management On Windows servers, you must enable WinRM, by typing winrm quickconfig at a local command prompt on each server and then typing y to grant administrative rights remotely to local users. Windows firewall configuration On each Windows source, you must have the following ports open. File and Printer Sharing (SMB-In) Port 445 must be open for all profiles. PowerShell and Windows Remote Management (HTTP-In) Port 5985 (for HTTP) and 5986 (for HTTPS) must be open for public and domain profiles. Confirm in Windows Remote Management (HTTP-In) that the Scope for Remote IP address is set to Any IP address. Carbonite Move Ports 6320, 6325, and 6326 must be open for UDP and TCP for both inbound and outbound traffic. Linux firewall configuration On each Linux source, you must have ports 22, 1500, 1505, 1506, 6325, and 6326 open for both UDP and TCP for both inbound and outbound traffic. You must also have port 1501 open for localhost communication. Carbonite licensing Carbonite Cloud Migration is powered by Carbonite Move, which requires a license on each source server. Source licenses will automatically be activated when a Chapter 2 Requirements 13

14 migration job is started and will automatically expire after 60 days. If you delete and re-create a migration from that same source, the license will be reused, however you still only have the 60 day window from when it was first activated to complete the migration. See Configuration on page 37 for details on adding licenses to your environment. Time The clock on your source and target servers must be within a few minutes of each other, relative to UTC. Large time skews (more than five minutes) will cause errors during cutover. Chapter 2 Requirements 14

15 Target requirements The target servers you are migrating to have general requirements as well as requirements specific to the infrastructure where the target servers are located Infrastructure requirements You must meet requirements specific to the target cloud infrastructure you are using. See the following links for requirements specific to that environment type. Target requirements for Amazon Web Services on page 16 Target requirements for custom environments on page 17 Target requirements for Microsoft Azure Classic on page 19 Target requirements for Microsoft Azure Resource Manager on page 20 Target requirements for OpenStack on page 28 Target requirements for VMware vcloud Director on page 29 Target to source communication A VPN is required if your source and target cannot communicate together in both directions. Target to Carbonite Cloud Migration communication If your target does not have a public IP address, you will have to use a proxy server for target to Carbonite Cloud Migration communication. If you are using a proxy server, it must be run on Windows 2012 or 2012 R2. You can also run it on Windows 2008 R2, but you must install PowerShell version 4.0 or later to use this operating system. Do not install the proxy server on your source server. See Proxy server on page 55 for more details. Carbonite licensing You do not have to purchase or activate a Carbonite Move license on each target server. Carbonite Cloud Migration will handle the licensing on the target server. Time The clock on your source and target servers must be within a few minutes of each other, relative to UTC. Large time skews (more than five minutes) will cause errors during cutover. Chapter 2 Requirements 15

16 Target requirements for Amazon Web Services In addition to the general Target requirements on page 15, an Amazon Web Services environment must meet the following requirements. Keys You must have an access key and secret key in order to use Amazon Web Services. Templates During the migration setup, you must select an operating system template for each source operating system you are migrating. This template will be used to create the target server in the cloud. Your templates must meet the following requirements. Amazon Machine Images The list of available templates is determined by the AMIs (Amazon Machine Images) that you have available. Carbonite Cloud Migration can only use AMIs that meet the following characteristics. Image type machine Root device type ebs Virtualization type hvm Block device mapping volume type standard or gp2 If you do not have an AMI that meets this criteria, your search list will be empty. Linux restrictions The templates for Linux operating systems must meet the following requirements Volumes The / and /boot system volumes must match on the source and template. If you have / and /boot on different volumes on the source, you have / and /boot on different volumes on the template. If they are on the same volume on the source, they must be on the same volume on the template. UEFI, trusted boot, secure boot UEFI, trusted boot (tboot), secure boot, or other volume blocking mechanisms are not supported on your Linux templates. Kernel Paravirtualized kernels are not supported on your Linux templates. Chapter 2 Requirements 16

17 Target requirements for custom environments A custom environment as a target infrastructure is only supported when the target server already exists. Carbonite Cloud Migration will not create any virtual machines or disks, configure any target access points, open firewall ports, or other automated tasks that are usually performed when Carbonite Cloud Migration creates the target for you. Therefore, the target must meet the following requirements, in addition to the general Target requirements on page 15. Matching volumes Windows For each volume you are migrating from the source, the target must have a matching volume. For example, if you are migrating volumes C: and D: on the source, the target cannot have volumes D: and E:. In this case, the target must also have volumes C: and D:. Additional target volumes are preserved and available after cutover with all data still accessible. Linux There are no limits to the number of volumes you can protect on the source, although you are bound by operating system limits. The / and /boot system volumes must match on the source and target. If you have / and /boot on different volumes on the source, you have / and /boot on different volumes on the target. If they are on the same volume on the source, they must be on the same volume on the target. For each non-system volume you are protecting on the source, the target must have a matching volume. For example, if you are protecting /data and /home on the source, the target must also have /data and /home. Additional target volumes are preserved and available after cutover with all data still accessible. Operating system Windows The source and target must have the same operating system. For example, you cannot have Windows 2008 on the source and Windows 2012 on the target. The two servers do not have to have the same level of service pack or hotfix. Windows 2008 and 2012 and their R2 releases are considered different operating systems. Therefore, you cannot have Windows 2008 or 2012 on the source and the corresponding R2 version on the target. The Windows edition (Standard, Enterprise, and so on) does not have to be the same. Linux The source and target must have the same distribution and major version. For example, you cannot have a Red Hat version 5.8 source failing over to a Red Hat version 6.4 target. The two servers do not have to have the same minor version. For example, you can failover Red Hat version 6.4 to Red Hat version 6.5. Disk space The target must have enough space to store the data from the source. If you do not have enough disk space, the migration will fail. This amount of disk space will depend on the applications and data files you are migrating. The more data you are migrating, the more disk space you will need. The target must also have enough space to store, process, and apply the source's system state data. The size of the system state will depend on the operating system and architecture. Windows A copy of the source system state data will be staged on the target boot volume in a folder called Staging-SSM. You can predict (approximately) how much space you will need in this staging folder by calculating the size of the following folders on your boot volume. Chapter 2 Requirements 17

18 Documents and Settings Program Files Program Files (x86) Program Data Windows Users If the target's boot volume does not have enough space to accommodate the source data and the staging folder, the job will become stuck in a retrying state and will be unable to complete synchronization. You should also have approximately 2-3 GB or more additional space on the target boot volume (beyond your calculation above) to ensure there is enough space for failover processing. The following are rough estimates for the free space needed for the staging folder for different operating systems. Windows 2008 R2 at least 10 GB Windows 2012 at least 14 GB Windows 2012 R2 at least 15 GB These minimums are for a clean operating system installation. Operating system customizations, installed applications, and user data will increase the disk space requirement. Linux A copy of the source data and system state will be staged on the target in a /dtstaging location for each mount point. For example, / will be staged in /dtstaging and /boot will be staged in /boot/dtstaging. You can predict how much space you will need in the staging folders by the amount of used space on the source. Other target compatibility requirements There are other requirements for a compatible existing target that are detailed in the Carbonite Move documentation. See the Documentation Library and select the Carbonite Move User's Guide that matches your Carbonite Move version and your operating system. Inside the Carbonite Move User's Guide, look under Full server migration, and then in Full server migration requirements for a Target compatibility section. This section details how an existing target server must be compatible with the source you are migrating. Remote access The existing target must allow remote access. For Windows servers, the target must allow WinRM connections. For Linux servers, the target must allow SSH connections. Connectivity The existing target must be accessible using the IP address you will provide for the migration. It also must be able to access the source using any of source s known IP addresses. The source machine must be able to access the target using the same IP you will provide for the migration. Firewall For an existing Windows target, ports 6320, 6325, and 6326 must be open for UDP and TCP for both inbound and outbound traffic. For an existing Linux target, you must have ports 22, 1500, 1505, 1506, 6325, and 6326 open for both UDP and TCP for both inbound and outbound traffic, and you must also have port 1501 open for localhost communication. Carbonite Move installation Because Carbonite Cloud Migration is not automating creation of the target server in a custom environment, you must have Carbonite Move already installed on the existing target before you begin the migration. See the Source requirements on page 11 for details on the packages and services that must be available before installing Carbonite Move. Chapter 2 Requirements 18

19 Target requirements for Microsoft Azure Classic In addition to the general Target requirements on page 15, a Microsoft Azure Classic environment must meet the following requirements. Subscription You must download and import an Azure subscription file. Templates During the migration setup, you must select an operating system template for each source operating system you are migrating. This template will be used to create the target server in the cloud. In the case of templates for Linux operating systems, the templates must meet the following requirements. Volumes The / and /boot system volumes must match on the source and template. If you have / and /boot on different volumes on the source, you have / and /boot on different volumes on the template. If they are on the same volume on the source, they must be on the same volume on the template. UEFI, trusted boot, secure boot UEFI, trusted boot (tboot), secure boot, or other volume blocking mechanisms are not supported on your Linux templates. Kernel Paravirtualized kernels are not supported on your Linux templates. Each time you use a Windows template, the size of the system disk created on the target may be different than the size of the system disk on the template based on a calculation. The calculation is the system disk space in use on the source plus minimum amounts of additional free space required by Carbonite Cloud Migration based on your operating system (10 GB for 2008 R2, 14 GB for 2012, and 15 GB for 2012 R2). If the calculation is smaller than the template system disk size, the template disk size will be used on the target. If the calculation is larger than the template system disk size, the calculation size will be used on the target. If the calculation is equal to or larger than the allowed maximum Azure size, the migration will not be allowed. Chapter 2 Requirements 19

20 Target requirements for Microsoft Azure Resource Manager In addition to the general Target requirements on page 15, a Microsoft Azure Resource Manager environment must meet the following requirements. Configuration You must register Carbonite Cloud Migration as a consumer of Active Directory and assign it an owner role. During the registration, you will need to obtain a Client ID, Client Secret, and Tenant ID that will be required when creating an Azure Resource Manager environment in Carbonite Cloud Migration. See Registering and assigning owner role in Microsoft Azure Resource Manager on page 21 for details. Networking A virtual network and subnet must be associated to the region you are migrating to. Subscription You must have your Azure Active Directory subscription ID. Templates During the migration setup, you must select an operating system template for each source operating system you are migrating. This template will be used to create the target server in the cloud. In the case of templates for Linux operating systems, the templates must meet the following requirements. Volumes The / and /boot system volumes must match on the source and template. If you have / and /boot on different volumes on the source, you have / and /boot on different volumes on the template. If they are on the same volume on the source, they must be on the same volume on the template. UEFI, trusted boot, secure boot UEFI, trusted boot (tboot), secure boot, or other volume blocking mechanisms are not supported on your Linux templates. Kernel Paravirtualized kernels are not supported on your Linux templates. Chapter 2 Requirements 20

21 Registering and assigning owner role in Microsoft Azure Resource Manager When using Microsoft Azure Resource Manager, you must register Carbonite Cloud Migration as a consumer of Active Directory and assign it an owner role. During the registration, you will need to obtain a Client ID, Client Secret, and Tenant ID that will be required when creating an Azure Resource Manager environment in Carbonite Cloud Migration. Complete the following steps in the new Azure portal. 1. To register Carbonite Cloud Migration as a consumer of Active Directory, select Azure Active Directory, App registrations, Add, specify the application information (as identified below this image), and click Create. Name Enter a unique name for the application. Application Type Select Web app/ API. Sign-on URL Enter any valid URL. For example, you might enter 2. Select the application you just created. Chapter 2 Requirements 21

22 3. In the Settings pane, click Properties. Chapter 2 Requirements 22

23 4. On the Properties pane, copy the Application ID and use it for the Client ID in Carbonite Cloud Migration. Chapter 2 Requirements 23

24 5. Again on the Settings pane, click Keys. 6. Specify the key information. Description Enter a description for the key. Expires Enter a duration for the key. Value Click Save to display the key value. Copy this value now. You will only be able to copy this key the first time you save it. After that, it will not be visible. Copy this key and use it for the Client Secret in Carbonite Cloud Migration. Chapter 2 Requirements 24

25 7. Back on the App registrations pane, select Endpoints and then copy the GUID (global unique ID) from the middle of the URL under OAUTH 2.0 AUTHORIZATION ENDPOINT. Use this GUID for the Tenant ID in Carbonite Cloud Migration. 8. Assign the owner role to your application by adding the application you just created as a user and assigning it the owner role. On the main menu, select Subscriptions, select your subscription, Access control, and click Add. Chapter 2 Requirements 25

26 9. Select the Owner role. Chapter 2 Requirements 26

27 10. Enter the name of the application in the search field, select your application, the click OK. Chapter 2 Requirements 27

28 Target requirements for OpenStack In addition to the general Target requirements on page 15, an OpenStack environment must meet the following requirements. Version OpenStack Liberty is the only supported version. Network You must have one external and at least one internal network. Templates During the migration setup, you must select an operating system template for each source operating system you are migrating. This template will be used to create the target server in the cloud. Your templates must meet the following requirements. Agent The templates must contain the cloudbase-init agent. Naming convention Some operating system templates must be named using a specific naming convention in order for Carbonite Cloud Migration to locate and use them. The following keywords must be specified as part of the template name for the following operating systems. These keywords are not case-sensitive. Operating systems not listed do not have any special naming conventions required. Windows 2008 R2 2008R2 Windows or 2K12 Windows 2012 R2 2012R2 or 2K12R2 CentOS Centos Linux restrictions The templates for Linux operating systems must meet the following requirements Volumes The / and /boot system volumes must match on the source and template. If you have / and /boot on different volumes on the source, you have / and /boot on different volumes on the template. If they are on the same volume on the source, they must be on the same volume on the template. UEFI, trusted boot, secure boot UEFI, trusted boot (tboot), secure boot, or other volume blocking mechanisms are not supported on your Linux templates. Kernel Paravirtualized kernels are not supported on your Linux templates. Services The following services must be running. Keystone Identity service used by OpenStack for authentication (authn) and high-level authorization (authz). It currently supports token-based authn and user-service authorization. Nova Compute service used for hosting and managing cloud computing systems. It is a component-based architecture enabling quicker additions of new features. Glance Image service that provides discovery, registration and delivery services for disk and server images. Cinder Volume service that provides access to, and manages, block storage. Neutron Software-defined networking (SDN) project focused on delivering networkingas-a-service (NaaS) in virtual compute environments. Neutron has replaced the original networking application program interface (API), called Quantum, in OpenStack. Chapter 2 Requirements 28

29 Target requirements for VMware vcloud Director In addition to the general Target requirements on page 15, a VMware vcloud Director environment must meet the following requirements. vcloud Director Version 5.5 and 5.6 are the only supported versions. Networking Your vcloud networking must meet the following requirements. Static IP pool and DHCP are supported. Manual static addresses are not supported. You must have org vdc networks available Routed networks are supported only on the target with the following caveats. Carbonite Cloud Migration can detect NAT configurations and automatically use public facing IP addresses and ports. It cannot create the NAT configuration for you. If you are unable to create a NAT configuration because the private IP of the target server is not known (since it is not yet created), provisioning will fail. However, you can then create NAT rules for the newly created virtual machine and resume the migration. Carbonite Cloud Migration will recognize the new NAT rules and use the public facing IP address and ports for the migration. IP address ranges are not a supported configuration. You can map ports from any port to any port. In addition, if you are protecting a Windows server, you can map specific ports using the following port numbers. Port X to port 6320 Port Y to port 6325 If you are protecting a Windows server and using specific port mappings, you must use a Carbonite Cloud Migration proxy inside the routed network. vapp templates A vapp template must be provided in your catalog for each source operating system you are migrating. The templates must meet the following requirements Disks The template must have only one system disk. No data disks can be attached. Each time you use a Windows template, the size of the system disk created on the target may be different than the size of the system disk on the template based on a calculation. The calculation is the system disk space in use on the source plus minimum amounts of additional free space required by Carbonite Cloud Migration based on your operating system (10 GB for 2008 R2, 14 GB for 2012, and 15 GB for 2012 R2). If the calculation is smaller than the template system disk size, the template disk size will be used on the target. If the calculation is larger than the template system disk size, the calculation size will be used on the target. If the calculation is equal to or larger than the allowed maximum vcloud size, the migration will not be allowed. System bus number The system disk bus number must be 2. System disk unit number The system disk unit number must be 0. Virtual machines per vapp You can only have only one virtual machine per vapp. Chapter 2 Requirements 29

30 Guest The guest operating system of the template must support customization. VMware Tools The template must have the appropriate version of VMware Tools for your version of vcloud. Windows restrictions For Windows templates, the system disk bus type must be LSI Logic SAS. Linux restrictions The templates for Linux operating systems must meet the following requirements Volumes The / and /boot system volumes must match on the source and template. If you have / and /boot on different volumes on the source, you have / and /boot on different volumes on the template. If they are on the same volume on the source, they must be on the same volume on the template. UEFI, trusted boot, secure boot UEFI, trusted boot (tboot), secure boot, or other volume blocking mechanisms are not supported on your Linux templates. Kernel Paravirtualized kernels are not supported on your Linux templates. Security You must have organization administrator privileges. Chapter 2 Requirements 30

31 Target requirements for VMware vsphere In addition to the general Target requirements on page 15, a VMware vsphere environment must meet the following requirements. ESX The ESX server that will host your target must be version or later. vcenter If you are using vcenter, it must be version or later. vmotion Host vmotion is only supported if you are using vcenter. Storage vmotion is not supported. Template During the migration setup, you must select an operating system template for each source operating system you are migrating. This template will be used to create the target server in the cloud. The templates must meet the following requirements. Credentials You must provide credentials to access the template to anyone using the template. The credentials will be entered during the migration creation process and will be used to create a clone of the template. The clone will become the target. VMware Tools You must have VMware Tools installed on your template. The version of VMware Tools should correspond to the version of ESX you will be using. Networking DHCP networking is required on the template. Windows Windows templates must also meet the following requirements. Disks The template must have only one system disk. No data disks can be attached. Windows Remote Management WinRM must be enabled. To enable it, type winrm quickconfig at a local command prompt on the template and then type y to grant administrative rights remotely to local users. Firewall configuration The template must have the following ports open. Windows Remote Management (HTTP-In) Port 5985 (for HTTP) and 5986 (for HTTPS) must be open for public and domain profiles. Confirm in Windows Remote Management (HTTP-In) that the Scope for Remote IP address is set to Any IP address. Carbonite Move Ports 6320, 6325, and 6326 must be open for UDP and TCP for both inbound and outbound traffic. Linux Linux templates must also meet the following requirements. Operating system The default minimal installation of the operating system must be used. Disks The system disk may be one volume with / present and /boot as a directory, or it can be two volumes with / and /boot on different volumes. In either case, no data disks can be attached. Linux packages The template must have the following packages installed. See your operating system documentation for details on these packages. ssh /usr/sbin/dmidecode lsb SELinux policy SELinux must be disabled on the template. Chapter 2 Requirements 31

32 Proxy requirements If your source or target does not have a public IP address, you will have to use a proxy server for Carbonite Cloud Migration communication. The proxy server must meet the following requirements. Operating system The proxy server must be run on Windows 2012 or 2012 R2. You can also run it on Windows 2008 R2, but you must install PowerShell version 4.0 or later to use this operating system. System memory The minimum system memory on the proxy server is 1 GB. Disk space for program files The proxy server requires 150 MB of disk space for the program files. Server where proxy is installed Do not install the proxy server on your source server. Chapter 2 Requirements 32

33 Carbonite Cloud Migration interface requirements The Carbonite Cloud Migration is the online service and interface that you use to execute and manage the migration. You must meet the following requirements to use the service. Web browser Any recent web browser can be used to access Carbonite Cloud Migration, however the browser must have JavaScript enabled for the site to work correctly. If you are using Internet Explorer version 10 or later, make sure you are not running Compatibility Mode. Carbonite Cloud Migration to server communication If your source or target does not have a public IP address, you will have to use a proxy server for Carbonite Cloud Migration to server communication. If you are using a proxy server, it must be run on Windows 2012 or 2012 R2. You can also run it on Windows 2008 R2, but you must install PowerShell version 4.0 or later to use this operating system. Do not install the proxy server on your source server. See Proxy server on page 55 for more details. Chapter 2 Requirements 33

34 Chapter 3 Getting started Before you get started, make sure you have reviewed the Requirements on page 10 and have access to the Carbonite Cloud Migration interface on page 35. Then complete the following tasks, in order. 1. Create environments Environments contain the information needed to connect to an infrastructure. You will need at least two environments. One environment will be for the source so you can discover all of the servers you want to migrate. The second environment will be for the target so you can connect to your target cloud infrastructure. If you are migrating from or to multiple infrastructures, you will need an environment for each infrastructure type. See Environments on page 38 for more details. 2. Discover servers Once you have your source environment created, you can discover the source servers you want to migrate. See Servers on page 56 for more details. 3. Migrate servers After your environments are created and your source servers discovered, you can migrate them. See Migrations on page 62 for more details. Chapter 3 Getting started 34

35 Chapter 4 Carbonite Cloud Migration interface You can access the Carbonite Cloud Migration interface at migrate.doubletake.com. First time access Use these steps if it is your first time accessing the service. a. Click the Create an account link. b. Provide the requested information, noting that the password must be at least six characters long and must contain characters from at least three of the following categories: uppercase letters, lowercase letters, numerals, or non-alphanumeric characters. c. You must agree to the license agreement, terms of use, and privacy policy in order to use the service. d. Click Register. e. You will receive a verification from noreply@doubletake.com. Click the Verify link in the message to complete your sign up. Log In Use the address and password you specified when first signing up for the service. Dashboard Each time you access Carbonite Cloud Migration, you will see a dashboard page, which is the highest level overview. Migrations, Overview On the Overview tab of the Migrations section, you will see the number of migrations in each of the various states. Hover over colored areas of the large circle to see the number of migrations that are in that state. Click on a state name above the circle to go the Migrations page. Only those migrations that are in the state clicked will be displayed on the Migrations page. Clear the state name from the search box to see all migrations. Migrations, Activity On the Activity tab of the Migrations section, you will see the migration activity log. Servers On the Servers sections, you will see the number of servers in each of the various states. This is for servers in all of your environments. Hover over colored areas of the large circle to see the number of servers that are in that state. Click on a state name above the circle to go the Servers page. Only those servers that are in the state clicked will be displayed on the Servers page. Clear the state name from the search box to see all servers. Chapter 4 Carbonite Cloud Migration interface 35

36 Alerts No matter which page you are on in the interface, you can access a list of alerts from the bell icon near the upper right corner of the page. The number of alerts will be displayed in a circle over the bell. If you have only information alerts, the circle will be green. If you have one or more warning alerts, the circle will be yellow. If you have one or more error alerts, the circle will be red. The yellow warning color overrides green information, and red error overrides yellow warning. By clicking the circle or bell, you can view the alerts and the time they were generated. You can dismiss individual alerts or all of the alerts in the current list. User profile Under your sign in name, in the upper right corner, is a menu of options. My Account Select this option to access your user profile. this is the account information you provided when you signed up as well as a few settings specific t your account. Delete The trash icon allows you to delete your Carbonite Cloud Migration account. You will receive an requiring you to confirm the deletion. Details This is your profile and contact information. You can also modify your account credentials here. Preferences You have several display options as well as configuration. Show What's New on startup Specify if you want to show or hide the page that lists new features each time you access the Carbonite Cloud Migration. You can view this page at any time by clicking View. Prefix By default, the subject line of alerts sent to your account will be prefaced with Carbonite Cloud Migration Alert. This prefix allows you to recognize and filter s specific to Carbonite Cloud Migration. You can change or remove the prefix as desired. Alerts Select the type and level of alerts that you want to receive as messages. If you do not select any type or level, you will not receive alerts as messages. You will still get alerts in the Carbonite Cloud Migration whether alerts are enabled or disabled. Activity Log This is the log of activity that has occurred during your current user session. The log will be cleared when you sign out. Downloads Select this option to access download files. PowerShell SDK Carbonite Cloud Migration includes Windows PowerShell cmdlets that you can use to control Carbonite Cloud Migration. This menu option takes you to the Carbonite SDK site where you can download a zip file that contains example PowerShell scripts that you can adapt to your environment. Proxy Server If you need to install and register a proxy server, click Download. See Proxy server on page 55 for more details. Documentation Select this option to access the Carbonite Cloud Migration User's Guide from the web. Log Out Select this option to manually sign out of Carbonite Cloud Migration. If there is a period of inactivity, you will automatically be signed out. Any migrations that you have started will continue to run, even when you are signed out. Chapter 4 Carbonite Cloud Migration interface 36

37 Configuration The Configuration page allows you to configuration your default migration options, manage your Carbonite Move licenses, and manage your proxy servers. Migrations You can set the default options that will be used. You can override these default settings when creating a migration. Default options These settings are the default migration options. Automatically cutover after synchronization completes When selected, cutover will begin automatically as soon as synchronization is complete. If this option is not selected, the migration process will pause when it gets to the cutover step and wait until you click Cutover to continue the migration process. Shut down source when cutover starts When selected, the source will be shut down automatically when cutover begins. In most cases, you should shut down the source because conflicts can occur if you have two servers with the same name on the same network. Shutting down the source server allows the target to come up without conflicts. If this option is not selected, the source will remain online when cutover begins. Compress data during migration When selected, data will be compressed as it is sent across the wire from the source to the target. Compression can reduce the amount of bandwidth consumed as well as the time that it takes to synchronize all of the data to the target. If this option is not selected, the data is not compressed. Licenses Licenses will be listed with the version of the license, the used and available remaining quantities, and the date and time the license was updated. Click Add License to add another license to your environment. Click Delete to remove an existing license. Proxies Proxy servers will be listed. Click Delete to remove an existing proxy server. If you need to install and register a proxy server, click Download Installation File. See Proxy server on page 55 for more details. Chapter 4 Carbonite Cloud Migration interface 37

38 Chapter 5 Environments Environments contain the information needed to connect to an infrastructure. You will need at least two environments. One environment will be for the source so you can discover all of the servers you want to migrate. The second environment will be for the target so you can connect to your target cloud infrastructure. If you are migrating from or to multiple infrastructures, you will need an environment for each infrastructure type. The following environment types are supported. See Target requirements on page 15 for links to details on using each of these environments. Active Directory Environment Type Supported for Source Infrastructures X Supported for Target Infrastructures Amazon Web Services (AWS) X X Custom X X 1 Microsoft Azure Classic Microsoft Azure Resource Manager OpenStack X X X VMware vcloud Director X X VMware vsphere X X 1. A custom environment as a target infrastructure is only supported when the target server already exists. See Target requirements for custom environments on page 17 for complete details on the requirements for using an existing server in a custom target environment. On the Environments page, you will find high-level information and controls for your environments. You can sort the environment list by clicking on any column heading. You can select multiple environments on this page by selecting the checkbox to the left of a table row. A checkmark indicates the environment is selected. Chapter 5 Environments 38