Transferring Image Files

Image files for which the export process is completed are stored in object storage. In order to use them in your environment, acquire the image files from object storage and transfer them to the migration destination environment.

About this task

Image files are stored in object storage under the following conditions.

  • Image files (objects) are stored with the "Image Name" + ".vmdk." Image Name is a name specified when the image was created from the virtual server system storage.
  • An ".ovf" file and an ".mf" file are also stored in the same container where the image files (objects) are stored.
  • Image files (objects) are divided and uploaded separately.

  • Divided files are stored in a different container with the name "Container Name" + "_segments."

    Note: If one or more divided files are deleted by accident, you will be unable to use the corresponding image files.

Use the following procedure to acquire exported image files.

Procedure

  1. Receive authorization to access the object storage where image files are stored.
  2. Specify the following parameters to acquire image files from object storage.
    • Project ID
    • Container name where exported image files are stored
    • Names of exported image files
  3. Acquire the ".ovf" file and the ".mf" file at the same time.

Results

Confirm that all image files, the ".ovf" file, and the ".mf" file were acquired successfully. At this time, the ".ovf" file is configured to start the virtual server with the minimal settings. Therefore, make the necessary modifications before transferring the files to your environment.

  • Configuring the number of CPUs (Changing the VirtualQuantity value)

    <Item>
  <rasd:AllocationUnits>hertz * 10^6</rasd:AllocationUnits>
  <rasd:Description>Number of Virtual CPUs</rasd:Description>
  <rasd:ElementName>1 virtual CPU(s)</rasd:ElementName>
  <rasd:InstanceID>1</rasd:InstanceID>
  <rasd:ResourceType>3</rasd:ResourceType>
  <rasd:VirtualQuantity>1</rasd:VirtualQuantity>
</Item>

  • Configuring the memory size (Changing the VirtualQuantity value)

    <Item>
  <rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
  <rasd:Description>Memory Size</rasd:Description>
  <rasd:ElementName>512MB of memory</rasd:ElementName>
  <rasd:InstanceID>2</rasd:InstanceID>
  <rasd:ResourceType>4</rasd:ResourceType>
  <rasd:VirtualQuantity>512</rasd:VirtualQuantity>
</Item>
Tip:
Table 1. List of OS Configured in ".ovf" Files
OS Type Settings
Windows 2008 R2 <OperatingSystemSection ovf:id="1" vmw:osType="windows7Server64Guest">
Windows 2012 R2 <OperatingSystemSection ovf:id="1" vmw:osType="windows8Server64Guest">
Windows 2016 <OperatingSystemSection ovf:id="1" vmw:osType="windows9Server64Guest">
Other than Windows <OperatingSystemSection ovf:id="1" vmw:osType="otherGuest">

What to do next

When the acquisition of image files and the acquisition and editing of ".ovf" and ".mf" files are completed, transfer them to your virtual environment.

Billing continues based on the amount of use of images created as export sources registered in the image archiving service, and image files that have been exported. After confirming that normal operation occurs in your environment, do not forget to delete any files that are no longer needed.