Description

This article describes how to copy a Client Image from one data center location to another within the same geographic region for both MCP 1.0 and MCP 2.0 data center locations.

Prerequisites:

  1. NOTE: Windows 2003 Servers cannot be imported to MCP 2.0 Data Center locations.
  2. Only the Primary Administrator OR a User with the Create Image role assigned by the Primary Administrator can copy a Client Image between Locations
  3. The source Client Image and the target data center to which you are trying to copy the Image need to be in the same Geographic Region. If you need to copy a Client Image to a data center in a different Geographic Region, see How to Copy a Client Image between Different Geographic Regions
  4. The target data center to which you are trying to copy the Image needs to support a Maximum Total Storage for an Image which is equal to or greater than that at the source Client Image data center.
    For details see: How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
  5. A Customer organization may have up to two Client Images being copied between locations at one time in a single Geographic Region. If you or other administrators are currently in the process of copying a total of two images, you will need to wait until at least one of them completes before it is possible to begin another copy.
  6. Non-Guest OS Customization client images can only be copied to MCP 2.0 Data Center locations. 
  7. The Image must meet the Target Data Center Location's requirements as identified in How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
    1. IDE and SATA local disks DO count towards Minimum Disk Count, Maximum Disk Count, and Maximum Total Storage
    2. ISO and FLP do NOT count towards Minimum Disk Count or Maximum Disk Count
    3. ISO and FLP DO count towards Maximum Total Storage
  8. The image must also meet certain hardware requirements:
    1. The Virtual Server Virtual Hardware Version for the Target Data Center must be equal to or greater than the one associated with the Image you are trying to copy.
      1. Data Center Virtual Hardware Version can be seen on the Data Center Dashboard. See Navigating the Data Center Dashboard
      2. Note: Virtual Hardware Version must be at least Hardware Version 4, (see http://kb.vmware.com/kb/1003746).
  9. For Guest OS Customization Images only, you cannot copy Images with local disks on a mix of SCSI/SATA/IDE controllers. All local disks must be on the same controller type.
    1. CD-ROM devices do not need to be on the same controller as the local disks but note that Guest OS Customization images will always boot onto a local disk.

Content / Solution:

  1. From the Home page, click on the Compute button and select Images and Applications from the drop-down menu:


  2. The Images and Applications page will be displayed. Click on the Client Images in the Image Type section:


  3. The Client Images page will be displayed. Click on the Image you want to copy to a different location, then click on the Actions button and select Copy to another Data Center:


  4. The Copy Image to Data Center dialog will be displayed:


  5. Fill out the form with the appropriate information:

    • Target Data Center - Select the data center you wish to copy the Client Image to. Note this cannot be the same as the Source Image Data Center.

    • Destination Cluster - Select the target Cluster if User-Manageable Clusters have been enabled for the target Data Center. See Introduction to User-Manageable Clusters

      • Note: This field only appears if the Target Data Center has User-Manageable Cluster capabilities.
    • Target Image name - Select the Client Image you want to copy. Click the "refresh" link to update this list with the latest Client Images at the selected data center (for example if a "Clone" has completed).

    • Description - Enter an optional description of the Image to be copied.

    • Save a copy to your FTPS account -  If you want to download a copy of your image, this value is used to name each of the exported component files of the resulting OVF Package. The permitted character set is (within and excluding the quotes): “a-zA-Z0-9_+=#.,:;()-“. Note that the “space” character is not permitted.

      • If you select 'yes', you will be prompted to enter the OVF Package Name.

    • Add/Update Tag to List - You can add a Tag to the Image, or update an existing Tag. See Introduction to Tagging, Tag Keys and Tag Values
       

  6. Once the form has been filled out, click Copy:

    Important Notes:

    • All disk speed characteristics of the source Client Image will be conveyed to the target Client Image.

    • If you chose to download a copy of the OVF Package, the system displays an on-screen reminder that the OVF Package files will not appear in your staging folder until the copying process is complete.

    • The system will warn you if there is already a Client Image OVF package in your staging folder with the same OVF Package Name Prefix.

  7. The system will display a message indicating that the operation has begun:


  8. The system will begin to copy the image. The progress will be shown on the Client Images page:

    Note: While copying a Client Image, the source Client Image will be locked from use either for server deployments or other changes.

  9. Once the operation has completed, the Image will be available for deployment in the designated Data Center:

    Note: If you chose to retain a copy of the OVF Package in your FTPS Account folder you will be able to download the OVF package files from that location. For details see How to Access your Client Image Import and Export OVF Package Staging Folder
    Note: For Client Images with multiple disks, ensure you download every VMDK file belonging to the OVF package.