28.2 Configuring Migration of a Workload to VMware vCloud Director

When you add or discover a workload, the workload is listed on the Workloads page and the status is set as Not Configured. Before you migrate the workload, you must configure the workload for migration:

  1. Launch the PlateSpin Migrate Web Interface.

  2. On the Workloads page, select the workload you want to configure.

  3. Click Configure Migration.

  4. Select one of the following based on the scope of data you want to transfer from the source to the target:

    • Full Replication: A full volume of data transfer takes place from the source to the target.

    • Incremental Replication: Only differences are transferred from the source to the target, provided they have similar operating system and volume profiles.

      NOTE:PlateSpin Migrate does not support Incremental Replication for the initial replication of data to existing target workloads in VMware vCloud Director. However, you can schedule Incremental Replications for subsequent replication of data. See Incremental Recurrence in Step 8.

  5. Select a VMware vCloud Organization, which you previously configured as a target, to which you want to migrate the source data. See Section 3.3.3, Targets.

  6. Click Configure Migration.

  7. Configure the following settings. Ensure that the IP address for the source workload, the replication network for target, the cutover network, and the test cutover network are all different.

    Schedule Settings

    Incremental Recurrence

    Specify the following:

    • Start of Recurrence: The date when you want to start the replication. You can specify the date or click the calendar icon to select the date. By default, the time is 12:00 a.m.

    • Recurrence Pattern: The pattern to follow for the recurrence of the replication. For example:

      • To use incremental recurrence everyday, select Daily.

      • To never use incremental recurrence, select None.

      NOTE:

      • Scheduled incremental replications are skipped until the first full replication is complete.

      • When you schedule incremental recurrence, the replication takes place for a maximum period of 60 days from the starting time of replication. For example:

        • If you select Daily, then the replication takes place for 60 days from the time the replication starts.

        • If you select Weekly, then the replication takes place for 8 weeks from the time the replication starts.

        • If you select Monthly, then the replication takes place for 2 months from the time the replication starts.

    Full Replication

    Do one of the following:

    • To specify a schedule for the replication, click Start and specify the date when you want to start the full replication.

    • To start full replication manually without setting a schedule, click None.

    NOTE:You must prepare the workload prior to the scheduled time.The full replication cannot run unless the target VM exists and the workload preparation is complete. Migrate skips the scheduled full replication and retries it at the next scheduled time.

    Blackout Window

    Use these settings to force a replication blackout. The replication blackout suspends scheduled replications during peak utilization hours or prevents conflicts between VSS-aware software and the PlateSpin VSS block-level data transfer component.

    To specify a blackout window, click Edit and do the following:

    • Specify the start and end time for the blackout period.

    • Select one of the blackout recurrence pattern such as daily, weekly, or monthly. If you do not want to force a replication blackout, select None.

    NOTE:The blackout start and end times are based on the system clock on the PlateSpin Server.

    Compression Level

    These settings control whether data is compressed during transmission between the source and target workloads, and the level of data compression applied.See Data Compression. Select one of the following options:

    • Fast: Consumes the least CPU resources on the source, but yields a lower compression ratio.

    • Optimal: Consumes optimal CPU resources on the source and yields an optimal compression ratio. This is the recommended option.

    • Maximum: Consumes the most CPU resources on the source, but yields a higher compression ratio.

    Bandwidth Throttling

    These settings control the bandwidth throttling. PlateSpin Migrate enables you to control the amount of available bandwidth consumed by direct source-to-target communication over the course of a workload migration. You can specify a throughput rate for each migration job. Throttling provides a way to prevent migration traffic from congesting your production network and to reduce the overall load of your PlateSpin Server.

    To throttle replications to a specified rate, specify the required throughput value in Mbps and the time pattern.

    Migration Settings

    Transfer Method

    (For Windows Workloads) Select a data transfer mechanism and security through encryption.See Section 2.2, Supported Data Transfer Methods.

    To enable encryption, select the Encrypt Data Transfer option. See Section 2.3, Security and Privacy.

    Transfer Encryption

    (For Linux Workloads) To enable encryption, select the Encrypt Data Transfer option.See Section 2.3, Security and Privacy.

    Source Credentials

    Specify the credentials required for accessing the workload. See Section 19.3, Discovery Guidelines for Source Workloads.

    CPU

    (For migration to vCloud and VM platforms using VMware 5.1, 5.5, and 6.0 with a minimum VM hardware Level 8) Specify the number of sockets and the number of cores per socket for the target workload. It automatically calculates the total cores. This parameter applies on the initial setup of a workload with an initial replication setting of Full Replication.

    NOTE:The maximum number of cores the workload can use is subject to external factors such as the guest operating system, the VM hardware version, VMware licensing for the ESXi host, and ESXi host compute maximums for vSphere (see ESXi/ESX Configuration Maximums (VMware KB 1003497)).

    Some distributions of a guest OS might not honor the cores and cores per socket configuration. For example, guest OSes using SLES 10 SP4 retain their original cores and sockets settings as installed, whereas other SLES and RHEL distributions honor the configuration.

    Organization Virtual Data Center

    (For migration to vCloud) Select a virtual data center associated with your organization.

    vApp

    Specify a name for the VMware vApp.

    Virtual Machine Name

    Specify a display name for the new virtual machine.

    Disks

    Specify the path to the hard disk on the target virtual machine.

    Volumes

    Select volumes to be included in the target for migration.

    NTFS Cluster Size

    (For File-Based Windows Workloads) Specify the cluster size for the NTFS volume. For information about the default cluster size for an NTFS volume, see Microsoft Support KB Article 140365.

    Non-volume Storage

    (For Linux Workloads) Specify a non-volume storage, such as a swap partition, that is associated with the source workload. This storage is re-created in the migrated workload.

    Disks For Volume Groups

    (For Linux Workloads) Specify the datastore name and the path where the virtual disk must be created on the target machine. You can choose to retain the path specified by default.

    Volume Groups

    (For Linux Workloads) Specify the LVM volume groups to be migrated with the LVM logical volumes listed in the Converted Logical Volumes section of the settings.

    NOTE:Disks that host both regular volumes (such as /boot) and volume groups are configured in the Disks section.

    Converted Logical Volumes

    (For Linux Workloads) Specify one or more LVM logical volumes to be migrated for a Linux workload.

    Replication Network for Target

    By default, the replication NIC is the primary NIC that you specify in Target Workload Settings> Network Connections. Specify a network interface (NIC or IP address) on the target to use for replication traffic.

    1. Select a network to use for replication traffic.

    2. Select one of the following:

      • DHCP: Obtain an IP address automatically assigned by a DHCP server.

      • Static - Manual: Specify a static IP address that is unique within the supported subnet.

      • Static - IP Pool: Select this option to automatically issue IP address from the IP pool.

    3. Specify an MTU value that the PlateSpin Migrate Linux RAM Disk (LRD) replication network can use. Setting a low value helps to avoid jabber over networks. For example: a VPN.

      The default value is an empty string. When networking is configured in the LRD, it allows the network device to set its own default, which is usually 1500. However, if you specify a value, PlateSpin Migrate adjusts the MTU when it configures the network interface.

    Replication Networks for Source

    Select one or more network interfaces (NIC or IP address) on the source workload to use for replication traffic that are valid for communications with the replication environment.

    Services to Stop Before Any Replication

    (For Windows Workloads) We recommend that all the non-VSS compliant services or antivirus are stopped temporarily on the source while the VSS snapshot is being captured on the source. Select the Windows services that you want to be temporarily stopped on the source workload while the VSS snapshot is being captured on the source. These services are restored as soon as the VSS snapshot creation completes.

    Services to Stop for Cutover with Replication

    (For Windows Workloads) Select the Windows services that should be permanently stopped on the source workload for cutover with any replication. The services stopped on the source workload during the replication process are not restored after Cutover. The stopped services are restored after a Test Cutover.

    Daemons to Stop Before Any Replication

    (For Linux Workloads) Select the Linux services that you want to be temporarily stopped on the source workload before replication. These services will be restored back after replication completes.

    Daemons to Stop for Cutover with Replication

    (For Linux Workloads) Select the Linux services that should be permanently stopped on the source workload for Cutover with any Replication. The services stopped on the source workload during the replication process are not restored after Cutover. The stopped services are restored after a Test Cutover.

    Target Workload Settings

    (These settings are applied during the Run Cutover)

    VM Memory

    Specify the amount of memory allocated to the target workload.

    VM Tools

    To install the VM tools, select the Install VM Tools option. This option is selected by default.

    Hostname

    Do one of the following:

    • To retain the same host name, select No Change.

    • To change the host name, select Set To and specify the new name.

      NOTE:An incremental replication is required if you change the host name at cutover.

    System Identifier (SID) - (This setting is applicable only for Windows Server 2008)

    To generate a new system identifier for the target workload, select Generate New System Identifier (SID) in the Target Workload Test Settings section of the Web Interface. For Windows Server 2008, you must specify the local Administrator account credentials. If this account has been locally renamed on the source, provide the new name.

    Domain / Workgroup

    (For Windows Workloads) Depending on whether the source workload belongs to workgroup or domain, one of the following displays:

    • Workgroup: Workgroup_name

      where Workgroup_name is the workgroup name to which the source belongs.

    • Domain: Domain_name

      where Domain_name is the domain name to which the source belongs.

    NOTE:An incremental replication is required if you change the domain or workgroup at cutover.

    Do one of the following depending on where you want the target workload to join:

    • When the source workload belongs to a workgroup: Assume that the source workload belongs to a workgroup named WorkGroup1.

      • For the target workload to join the same workgroup (WorkGroup1), retain the following existing selection:

        Workgroup: Workgroup1

      • For the target workload to join a different workgroup (say WorkGroup2), select Join Workgroup and specify the name as WorkGroup2.

      • For the target workload to join a domain, select Join Domain and specify the domain name you want the target to join.

    • When the source workload belongs to a domain: Assume that the source workload belongs to a domain named Domain1.

      • For the target workload to join a workgroup, click Join Workgroup and specify the name of the workgroup you want the target to join.

      • For the target workload to join the same domain (Domain1) with the domain registration settings preserved, retain the following existing selection:

        Domain: Domain1

      • For the target workload to join the same domain (Domain1) without preserving the domain registration settings, select Join Domain and specify the domain name as Domain1.

      • For the target workload to join a different domain, select Join Domain and specify the domain name you want the target to join.

    Domain Credentials

    (For Windows Workloads) If you select Join Domain, specify the domain administrator credentials.

    Network Connections

    1. For workloads that have more than one NIC, select Include for each NIC to be migrated. Deselect Include to exclude a NIC.

      • At least one NIC is required.

      • The number of NICs to migrate cannot exceed the maximum number of NICs supported by the selected cloud instance.

    2. Ensure that the Primary NIC is properly configured for its role as Primary. The default Primary Connection is the first NIC in the list. To set a different NIC as Primary NIC, click Edit for the corresponding NIC and select Primary Connection for that NIC.

    3. For each included NIC:

      1. Select Start Connected to connect the virtual network interface when starting the target workload.

      2. Select a network.

      3. (Conditional) To set the NIC as Primary NIC, click Edit and select Primary Connection. This resets the Primary Connection for the previously set Primary NIC.

      4. Select one of the following:

        • DHCP: Obtain an IP address automatically assigned by a DHCP server.

        • Static: Specify a static IP address, a subnet mask, and a gateway IP address. The IP address must be unique within the supported subnet.

    DNS Servers

    (For Linux Workloads) Specify the DNS Servers for the target workloads. This is applicable only if you select Static in the Network Connections option:

    • Primary DNS server: Specify the primary DNS server address.

    • Alternative DNS server: Specify an alternate DNS server address.

    • Additional DNS server: To specify additional DNS server addresses:

      1. Click Advanced.

      2. Specify the DNS server address.

      3. Click Add to add the server in the DNS Server Addresses list.

      4. Click OK.

    Services States on Target VM

    (For Windows Workloads) Select Windows services that must be automatically stopped on the target VM.

    Daemons States on Target VM

    (For Linux Workloads) Select Linux daemons that must be automatically stopped on the target VM.

    Target Workload Test Settings

    (These settings are applied during the Test Cutover)

    Copy Target Workload Settings

    Click the Copy Target Workload Settings option to automatically copy the workload settings from Target Workload Settings (These settings are applied during the Run Cutover) section to Target Workload Test Settings (These settings are applied during the Test Cutover) section.

    VM Memory

    Specify the amount of memory allocated to the target workload.

    VM Tools

    To install the VM tools, select the Install VM Tools option. This option is selected by default.

    Hostname

    Do one of the following:

    • To retain the same host name, select No Change.

    • To change the host name, select Set To and specify the new name.

      NOTE:An incremental replication is not required if you change the host name at test cutover.

    System Identifier (SID) - (This Setting is applicable only for Windows Server 2008)

    To generate a new system identifier for the target workload, select Generate New System Identifier (SID) in the Target Workload Test Settings section of the Web Interface. For Windows Server 2008, you must specify the local Administrator account credentials. If this account has been locally renamed on the source, provide the new name.

    Domain / Workgroup

    (For Windows Workloads) Depending on whether the source workload belongs to workgroup or domain, one of the following displays:

    • Workgroup: Workgroup_name

      where Workgroup_name is the workgroup name to which the source belongs.

    • Domain: Domain_name

      where Domain_name is the domain name to which the source belongs.

    NOTE:An incremental replication is not required if you change the domain or workgroup at test cutover.

    Do one of the following depending on where you want the target workload to join:

    • When the source workload belongs to a workgroup: Assume that the source workload belongs to a workgroup named WorkGroup1.

      • For the target workload to join the same workgroup (WorkGroup1), retain the following existing selection:

        Workgroup: Workgroup1

      • For the target workload to join a different workgroup (say WorkGroup2), select Join Workgroup and specify the name as WorkGroup2.

      • For the target workload to join a domain, select Join Domain and specify the domain name you want the target to join.

    • When the source workload belongs to a domain: Assume that the source workload belongs to a domain named Domain1.

      • For the target workload to join a workgroup, click Join Workgroup and specify the name of the workgroup you want the target to join.

      • For the target workload to join the same domain (Domain1) with the domain registration settings preserved, retain the following existing selection:

        Domain: Domain1

      • For the target workload to join the same domain (Domain1) without preserving the domain registration settings, select Join Domain and specify the domain name as Domain1.

      • For the target workload to join a different domain, select Join Domain and specify the domain name you want the target to join.

    Domain Credentials

    (For Windows Workloads) If you select Join Domain, specify the domain administrator credentials.

    Network Connections

    Available NICs match the included NICs in Target Workload Settings > Network Connections. The default Primary Connection is the first NIC in the list.

    1. For each included NIC:

      1. Select Start Connected to connect the virtual network interface when starting the target workload.

      2. Select a network.

      3. (Conditional) To set the NIC as Primary NIC, click Edit and select Primary Connection. This resets the Primary Connection for the previously set Primary NIC.

      4. Select one of the following:

        • DHCP: Obtain an IP address automatically assigned by a DHCP server.

        • Static: Specify a static IP address, a subnet mask, and a gateway IP address. The IP address must be unique within the supported subnet.

    DNS Servers

    Specify the DNS Servers for the target workloads. This is applicable only if you select Static in the Network Connections option:

    • Primary DNS server: Specify the primary DNS server address.

    • Alternative DNS server: Specify an alternate DNS server address.

    • Additional DNS server: To specify additional DNS server addresses:

      1. Click Advanced.

      2. Specify the DNS server address.

      3. Click Add to add the server in the DNS Server Addresses list.

      4. Click OK.

    Services States on Target VM

    (For Windows Workloads) Select Windows services that must be automatically stopped on the target VM.

    Daemons States to Change

    (For Linux Workloads) Select Linux daemons that must be automatically stopped on the target VM.

    Tag

    Tag

    Select a tag to assign to the workload. For more information about tags, see Section 19.9, Using Tags to Track Logical Associations of Workloads.

  8. (Optional) To change the target, click Change Target.

    NOTE:If you change the target, all the settings you specified will be cleared.

  9. Do one of the following:

    • Click Save to save the settings.

    • Click Save and Prepare to save the settings and start preparing the workload migration.

    • Click Cancel to exit.