4.3 Synchronizing Workloads with Server Sync

The Server Sync feature enables you to reduce the scope of data that is transferred from your source to your target to just data that is different between a source and a target, effectively synchronizing their volume contents.

For example, when setting up a job for a workload portability operation, you can choose to update an existing physical or virtual machine to match the state your source workload without transferring volume data in its entirety. PlateSpin Migrate compares the target physical or virtual workload with the selected source and transfers only data that is different between the two, overwriting files on the target with those on the source workload.

Server Sync is useful in situations where the size of volume data or network conditions are prohibitive for a direct source-to-target virtualization over the network.

4.3.1 Server Sync to a Virtual Target

  1. Discover your source workload.

    See Discovering Source Workloads and Migration Targets.

  2. Create a target virtual machine by using one of the following methods:

    • Do an initial migration of your workload to a virtual machine. See Migrating a Workload to a VM Host (P2V, V2V).

      - OR -

    • Using your virtualization platform’s native interface, manually install a virtual machine with the same operating system profile as that of your source.

      NOTE:When you are creating a virtual target for Server Sync, you should also manually install the appropriate virtualization enhancement tools, such as VMware Tools or XenServer Tools.

      - OR -

    • (Windows only) Capture your workload to a PlateSpin Image, and deploy it to a virtual machine on your virtualization platform. See Capturing a Workload to a PlateSpin Image and Deploying a PlateSpin Image.

  3. (Conditional; Hyper-V only) Because the Server Sync option is disabled for a Hyper-V VM, it is necessary to use the following steps, as documented in KB 7010748:

    1. After booting the target VM with bootofx2p.iso, wait for the Migrate Server URL prompt, Then press Alt+F7 to launch the debug console.

    2. From the debug console, run the following command to determine which devices are /, /boot and swap:

      fdisk -l

    3. Using the information obtained from the debug console, mount the appropriate devices as under:

          mount /dev/%root device% /
    mount /dev/%boot device% /boot

    4. Press Alt+F1 to switch to the server command line.

    5. At the command line, provide the required information at each individual prompt:

      • PlateSpin Server: Use the following format:

        http:// server_host /platespinmigrate

        Replace server_host with the actual PlateSpin Server host’s name or IP address.

      • Credentials (User Name/Password): Enter the name of an admin-level user on the PlateSpin Server host, including the domain or machine name. For example: domain\username, or localhost\Administrator. Provide a valid password for the specified user.

      • Network Card: Select the network card that is active, then either enter a temporary static IP address for this card or press the Enter key to use a DHCP server.

      • Temporary hostname: Provide a temporary VM name for PlateSpin Migrate Client to use to list the newly registered VM. The workload’s target hostname you select in the migration job overwrites this name.

      • SSL encryption: If your PlateSpin Migrate is installed on a host with SSL encryption enabled, enter Yes. If not, enter No.

      • PlateSpin Migrate Network: Unless you have defined your own PlateSpin Migrate Network in PlateSpin Migrate Client, press the Enter key. If you are working with a non-default PlateSpin Migrate Network, type its name, then press the Enter key.

        A controller on your target virtual machine communicates with PlateSpin Server and registers the virtual machine as a physical target for a migration job.

  4. In the Servers view, drag your source workload and drop it on the required target (Server Sync target or discovered physical machine under control).

    The system validates the selected source and target and, if it detects matching operating systems on them, provides you with two Transfer Scope options, Full Migration and Server Sync:

  5. Select the Server Sync option, then click Advanced (you can only set up a Server Sync job in Advanced mode).

    A Server Sync job configuration window opens in Advanced mode:

  6. In the job configuration window, specify the parameters of the job as dictated by the purpose of the operation, address any warnings and errors, and make sure that you map the required volumes on the source to those on the target (see Volume Configuration in Server Sync).

    When you have finished, click Start.

    PlateSpin Migrate starts the job and lists it in the Jobs view.

4.3.2 Server Sync to a Physical Target

  1. Discover your source workload.

    See Discovering Source Workloads and Migration Targets.

  2. Discover your physical target by using the appropriate boot ISO boot image.

    See Discovering Target Physical Machines.

  3. In the Servers view, drag your source workload and drop it on the required target (Server Sync target or discovered physical machine under control).

    The system validates the selected source and target and, if it detects matching operating systems on them, it provides you with two Transfer Scope options, Full Migration and Server Sync, similar to the Server Sync to a Virtual Target scenario (see Step 4).

  4. Select the Server Sync option, then click Advanced (you can only set up a Server Sync job in Advanced mode).

    A Server Sync job configuration window opens in Advanced mode:

  5. In the job configuration window, specify the parameters of the job as dictated by the purpose of the operation, address any warnings and errors, and make sure that you map the required volumes on the source to those on the target.

  6. When you have finished, click Start.

    PlateSpin Migrate starts the job and lists it in the Jobs view.