Desktop Virtualization › Managing the vDisks and the vDisk Clones › How vDisk Clones are Handled

How vDisk Clones are Handled

You can copy or clone the vDisks to provision virtual desktops. vDisk copies or clones and their parent vDisk appear as separate management records in the MDB.  The comstore values of the provisioning server farm, store, site, vDisk name differentiate a parent vDisk from that of a cloned vDisk.

CA ITCM uses the following rules to identify vDisk clones and create a separate management record for them:

• A new management record is created in CA ITCM and the agent name is in the FarmName-StoreName-vDisk format, when a vDisk is booted in private mode for template management.
• A new management record is created for the clone, when a vDisk clone is booted in private mode for template management from a different farm.
• A new management record is created for the vDisk copy, when the clone is booted from the same farm and a different store, and vDisk and its parent name are different.
• A new management record is created for the vDisk copy on the following rule:
  • The clone vDisk is booted from the same farm and a different store
  • vDisk and its parent name are same
  • The site from which the vDisk is booted for template management and its parent are different

    Note: If the site is same as the parent vdisk, Administrator is prompted to verify whether to create a management record in the MDB or reuse the existing one.

• A new management record is created on the following rule:
  • The farm and store are same
  • vDisk name changes
  • The parent vDisk is part of the store
  • vDisk is booted as a copy

    Note: If the Parent vdisk is not part of the store, Administrator is prompted to verify whether to create a management record in the MDB or reuse the existing one.

• An existing managed computer record is reused, when the vDisk, farm and store names are same.

Back to Top