Product documentation
Citrix Virtual Apps and Desktops
Service Current Release 2407 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR
View PDF

Manage a XenServer catalog

November 19, 2024
Contributed by: 
C C

Manage machine catalogs describes the wizards that manage a machine catalog. The following information covers details specific to XenServer virtualization environments.

Note:

Before managing a XenServer catalog, you need to finish creating a XenServer catalog. See Create a XenServer catalog.

Storage migration of persistent and non-persistent VMs

You can migrate the following VM disks from one storage to another using the Move-ProvVMDisk PowerShell command.

  • For persistent Full Clone VMs: OS Disk, Identity Disk, and non-MCS provisioned disks.
  • For non-persistent VMs: OS Disk, Identity Disk, and Write-back Cache (WBC) disk.

Prerequisite

The new storage must satisfy the following condition:

  • The host on which the VM is running must have access to both the old and new datastores.

Limitations

Consider the following limitations while migrating persistent and non-persistent VMs:

  • For persistent Full Clone VMs: If there are snapshots with the moving VM, after migration, an additional consolidated disk might consume more disk space. For example, before migrating (snapshot1 100G + snapshot2 20G + 10G OS files). After migration (consolidated disk 130G + snapshot1 100G + snapshot2 20G).
  • For non-persistent VMs: Migration of snapshots is not supported.

Migrate the disk storage

To migrate the disk storage:

  1. Add a destination storage to an existing hosting unit. You can run the PowerShell command Add-Hyphostingunitstorage to add the destination storage:

    If you do not want to add new VMs to the old storage, then change the old storage to Superseded. You can do this using Studio or PowerShell commands. See Edit storage. You can also run Set-Hyphostingunitstorage and Superseded as true to disable new VM creation in the old storage.

    Note:

    For non-persistent VMs:

    • If WBC is used, then configure the WBC destination storage in the hosting unit.
    • If OS destination storage is configured, then WBC (if used) must be compatible with OS destination storage.
    • If OS destination storage is not configured, then WBC (if used) must be compatible with the current OS storage.
  2. Turn off the VMs and turn on the Maintenance Mode.

  3. Get the information about the provisioning scheme, hosting unit, OS disk storage, and WBC disk storage. See ProvResourceInStorage for OS storage information. For example:

    $result=Get-ProvSchemeResourceInStorage -ProvisioningSchemeName xxxxx
$result
$result.ProvResourceInStorage | Format-List -Property *
<!--NeedCopy-->

    See TemporaryStorageInfo for WBC storage information. For example:

    $result=Get-ProvSchemeResourceInStorage -ProvisioningSchemeName xxxxx
$result
$result.TemporaryStorageInfo | Format-List -Property *
<!--NeedCopy-->

  4. Migrate the OS disk, Identity disk, and WBC disk (applicable to non-persistent VMs) to the destination storage using the Move-ProvVMDisk PowerShell command.

    Note:

    • Always provide the OS and Identity disks in the DiskType and DestinationStorageId parameters.
    • The DestinationStorageId for OS disk and Identity disk must be the same.

    Example:

    Persistent VMs:

    (Get-ProvVM -ProvisioningSchemeName xxxxx) | Move-ProvVMDisk -ProvisioningSchemeName "myFullCloneProvScheme" -VMName "machine01" -DiskType OS,Identity -DestinationStorageId datastore1,datastore1
<!--NeedCopy-->

    Important:

    For Persistent VM, all disks are moved. You cannot select which disks to move.

    Non-persistent VMs:

    (Get-ProvVM -ProvisioningSchemeName xxxxx) | Move-ProvVMDisk -ProvisioningSchemeName "myCleanOnBootProvScheme" -VMName "machine01" -DiskType OS,Identity,WBC -DestinationStorageId None,None,datastore1
<!--NeedCopy-->

    Important:

    • If you don’t want to migrate a specific disk, set the value as None for the DestinationStorageId parameter.
    • If the VM has WBC disk, then add the WBC disk in DiskType parameter and add the required information in DestinationStorageId parameter.

Troubleshoot

If one of the disks fails to migrate, then none of the disks are migrated to the destination storage. You can get the failure report using the following command:

(Get-ProvTask -TaskID xxxxxxxxx).DiskMoveFailedVirtualMachines
<!--NeedCopy-->

Identify resources created by MCS

Following are the tags that MCS adds to the resources. The tags in the table are represented as “key”:”value”.

Resource name Tag
Published base disk and its copy on each network or local storage “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
ID disk “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
OS disk “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
Prep VM “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
VM in catalog “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
WBC disk “CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”

More information

Manage a XenServer catalog
November 19, 2024
Contributed by: 
C C
November 19, 2024
Contributed by: 
C C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.