You can migrate one or more managed virtual machines in a VMware vRealize ™ Automation environment to a different vRealize Automation environment.

About this task

A managed virtual machine is a virtual machine that is managed in a vRealize Automation environment and can be viewed in the console.

Prerequisites

  • Log in to the vRealize Automation console as a fabric administrator and as a business group manager.

  • If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool. For more information, see #GUID-CBB6810F-4C3E-4492-91E1-012BE371D623.

  • If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool. For more information about using a network profile to control IP address ranges, see Configuring vRealize Automation.

Procedure

  1. Generate a virtual machine CSV data file.
    1. Select Infrastructure > Administration > Bulk Imports.
    2. Click Generate CSV File.
    3. Select Managed from the Machines drop-down menu.
    4. Select one of the available resource types from the Resource drop-down menu.

      Option

      Description

      Endpoint

      Information required to access a virtualization host.

      Compute Resource

      Information required to access a group of virtual machines performing a similar function.

    5. Select the name of the virtual machine resource from the Name drop-down menu.
    6. (Optional) Select Include custom properties.

      You include custom properties when you import a virtual machine into a new deployment with the same properties.

    7. Click OK.
  2. Edit your virtual machine CSV data file.

    Whether you must edit the CSV data file depends on the similarity of the source and target environments. If the configuration values in the source environment do not match the values in the target environment, you must edit the CSV data file so that the values match before you begin migration.

    1. Open the CSV file, and edit the data categories to match existing categories in the target vRealize Automation environment.

      To migrate virtual machines contained in a CSV data file, each virtual machine must be associated with a reservation, storage location, blueprint, machine component, and owner that exists in the target vRealize Automation environment. All the values for each virtual machine must be present in the target vRealize Automation environment for migration to succeed. You can change the values for reservation, storage location, blueprint, and owner, or add a static IP address value to individual virtual machines by editing the CSV file.

      Heading

      Comment

      Example

      # Import--Yes or No

      Change to No to prevent a particular virtual machine from being imported.

      Yes

      Virtual Machine Name

      Do not change.

      MyMachine

      Virtual Machine ID

      Do not change.

      a6e05812-0b06-4d4e-a84a-fed242340426a

      Host Reservation (Name or ID)

      Enter the name or ID of a reservation in the target vRealize Automation environment.

      DevReservation

      Host To Storage (Name or ID)

      Enter the name or ID of a storage location in the target vRealize Automation environment.

      ce-san-1:custom-nfs-2

      Deployment Name

      Enter a new name for the deployment you are creating in the target vRealize Automation environment.

      Each virtual machine must be migrated to its own deployment. You cannot import a single virtual machine to an existing deployment. You cannot import multiple virtual machines to a single environment.

      ImportedDeployment0001

      Converged Blueprint ID

      Enter the ID of the blueprint in the target vRealize Automation environment that you use to import the virtual machine.

      Make sure that you enter only the blueprint ID. Do not enter the blueprint name. You must select a blueprint that contains only a single virtual machine component. The blueprint must be published and added to an entitlement.

      ImportBlueprint

      Component Blueprint ID

      Enter the name of a virtual machine component that is contained in the blueprint you selected. You cannot import a virtual machine into a blueprint that has more than one component.

      ImportedMachine

      Owner Name

      Enter a user in the target vRealize Automation environment.

      user@tenant

      Example of a complete, properly formatted CSV line: Yes, MyMachine, a6e05812-0b06-4d4e-a84a-fed242340426, DevReservation, ce-san-1:custom-nfs-2, Imported Deployment 0001, ImportBlueprint, ImportedMachine, user@tenant

    2. If you are migrating a virtual machine with a static IP address, append a command in the following form to the CSV file.

      ,VirtualMachine.Network#.Address, w.x.y.z, HOP

      Configure the command with the appropriate information for your virtual machine.

      • Change the # to the number of the network interface being configured with this static IP address. For example, VirtualMachineNetwork0.Address.

      • Change w.x.y.z to be the static IP address for the virtual machine. For example, 11.27.42.57.

      • The HOP string, Hidden, Not encrypted, Not runtime, sets the visibility of the property. This default property is removed from the virtual machine after a successful import.

      For a successful migration, the IP address must be available in a properly configured address pool. If the address cannot be found or is already in use, the migration succeeds without the static IP address definition, and an error is logged.

    3. Save the CSV file.
  3. Use the vRealize Automation management interface to migrate your virtual machine to a vRealize Automation environment.
    1. Select Infrastructure > Administration > Bulk Imports.
    2. Click New.
    3. Enter a unique name for this task in the Name text box, for example, managed migration 10.
    4. Enter the CSV filename in the CSV file text box by browsing to the CSV filename.
    5. Select import options.

      Option

      Description

      Start time

      Schedule a future start date. The chosen start time is the local server time and not the local time of the user workstation.

      Now

      Begin the migration process immediately.

      Delay (seconds)

      If you are migrating many virtual machines, select the number of seconds to delay each virtual machine registration. Selecting this option slows the migration process. Leave blank to select no delay.

      Batch size

      If you are migrating many virtual machines, select the total number of virtual machines to register at a given time. Selecting this option slows the migration process. Leave blank to select no limit.

      Ignore managed machines

      Leave unselected.

      Skip user validation

      Selecting this option sets the virtual machine' owner to the value listed in the Owner column of the CSV data file without verifying that the user exists. Selecting this option can decrease the migration time.

      Test import

      Test the migration process without migrating the virtual machines so you can test your CSV file for errors.

    6. Click OK.

      The progress of the operation appears on the Bulk Imports page.