Migrating OVF and VM Templates between Content Libraries or vCenter Servers

Products

• VMware vCenter Server

Issue/Introduction

Administrators may need to migrate Content Library templates to a new datastore or an entirely new vCenter Server when underlying hardware or source vCenters are being decommissioned.

The procedure for moving a template depends heavily on whether it is an OVF/OVA Template or a VM Template (VMTX).

• OVF Templates are standalone files that can be synchronized between vCenters using Publisher/Subscriber libraries.

• VM Templates (VMTX) are backed by objects in the vCenter Server inventory. Deleting a VM template from a Content Library removes it from the vCenter inventory, even if the files reside on a different datastore.

Resolution

Choose the migration method below based on the type of template being moved.

Method 1: Migrating OVF Templates (Cross vCenter)

Use this method to move OVF templates from one vCenter Server to another.

1. Source vCenter Server: Convert the local Content Library to a Publisher content library. (Refer to Create and Edit a Content Library.)

2. Destination vCenter Server:

   1. Create a Subscribed content library that subscribes to the Publisher library on the source vCenter.

   2. Navigate to the new Subscribed library and select Actions -> Synchronize to pull the library items from the publisher.

   3. Create a brand new Local content library on the destination vCenter.

   4. From the Subscribed library, select All templates -> Right-click -> Clone item, and point the clones to the newly created Local library.

3. Once all OVF templates are successfully cloned to the Local library, the admin can safely delete the Subscribed library.

Method 2: Migrating VM Templates / VMTX (Between Content Libraries)

Because VM Templates (VMTX) are tied to the vCenter inventory, migrating them requires converting them briefly to virtual machines.

1. In the vSphere Client, navigate to the VMs and Templates view.

2. Right-click the VM Template and select Convert to Virtual Machine -> Finish.

3. Right-click the newly converted virtual machine and select Clone as Template to Library.

4. Ensure that the template type is set to VM Template.

5. Select the New Content Library from the wizard. (Note: The user can place the new VM Template on any datastore, irrespective of where the new Content Library is hosted).

Additional Information

Syncing VMTX: If you attempt to sync VM Templates (VMTX) using the Publisher/Subscriber method in Method 1, both vCenter Servers must participate in Enhanced Linked Mode (ELM). Otherwise, they will not sync.

Bulk Migrations: For bulk migration of VM Templates to a new Content Library, consider using PowerCLI to clone the VM Templates as OVA/OVF files into the new library.

Manage VM Templates in a Content Library
Clone OVA/OVF templates to a new Content Library
Japanese KB: VM テンプレートをあるコンテンツライブラリから別のコンテンツライブラリに移動する方法