Exporting and importing vDisks

Citrix Provisioning exports and imports bothversionedandunversionedvDisks from an existing store to another store in a different farm.

With vDisk versions, you can isolate updates to a vDisk or allow for quick revisions without affecting and copying a 30–40 GB file every time you want to make an update to your vDisk.

When working with vDisk versions, exporting the vDisk is the easiest way to move those versions to another farm. When you export a vDisk, an XML manifest file for the given vDisk is created. The XML manifest file fetches version details from SQL and/or the vhdx/avhdx files on vDisk. This can then be used to import the vDisk into the Citrix Provisioning console. An unversioned vDisk can be imported without the manifest XML file, but a versioned vDisk requires a manifest XML file before it can be imported.

Tip:

Merge differencing disks first to a base disk using third party tools if you are importing VHDs that are not exported using Citrix Provisioning. After merging them, import the new VHD base disk.

Exporting vDisks

To export a vDisk

1. Right-click on the vDisk in the Citrix Provisioning console, then select theExportmenu option. TheExportdialog appears.
2. Select the version to export from the menu, then clickOK. The manifest file is created in the Store.

Tip:

If you delete a vDisk that you plan to export, Citrix recommends that you export the vDisk first. After exporting it, copy the resulting XML file to the new location before deleting it from the original location.

Importing vDisks

A vDisk or vDisk chain of differencing VHD files can be imported into a store if:

• The imported VHD does not exist in the store and both the highest version number of the VHD and associated manifest files match.
• The VHD chain includes a base image, and that base image version number matches the base image version in the manifest file.

Note:

When importing a single vDisk, no manifest file is required, however, if you import vDisks with versions you must include a manifest file.

• The VHD does exist in the store but the imported version number in the associated manifest file is greater than the existing VHD version number.

Important:

If you have an existing vDisk with the same name in other stores, and one or more of those stores either has not set the provisioning server, or the server is unreachable, the import fails. A message appears to indicateNo server available to handle [other store name]. This issue occurs because the import process checks that the imported vDisk is not stored in the same location as the vDisk with the same name in the other store.

To add or import an existing vDisk to a site

1. Copy the vDisk and any associated properties files to shared storage, if they do not exist there.
2. In the console, right-click on theStore or a vDisk Pool, then select theAdd or Import Existing vDiskmenu option. TheAdd or Import Existing vDisksdialog appears.
3. Select the store to search for vDisks from theStore to searchmenu.
4. Select the server to use to search for vDisks from the服务器to use for searchingmenu, then clickSearch. All vDisks in the store display in theAdd checked vDisks to the vDisk Pool.
5. Check the vDisks you want added to the vDisk pool.
6. Optionally, checkEnable load balancing for these vDisksto enable load balancing on provisioning servers that provide this vDisk to target devices.
7. ClickAddto add the vDisk(s) to the vDisk pool.

Adding vDisk versions

To add a vDisk version to a site

1. Copy the vDisk, and any associated property files, to shared storage, if they do not exist there.
2. In the console, right-click on theStoreor avDisk Pool, then select theAdd vDisk Versionsmenu option. TheAdd vDisk Versionsdialog appears.
3. Select the store to search for vDisks from theStore to searchmenu.
4. Select the server to use to search for vDisks from the服务器to use for searchingmenu, then clickSearch. All vDisks in the store display in theAdd checked vDisks new versions.
5. Check those vDisk versions added to the vDisk pool.
6. ClickAddto add the vDisk(s) to the vDisk pool.