четверг, 28 июля 2016 г.

Типы дисков в Linked-Clone Desktop окружении


View Composer creates an OS disk for each linked clone. This disk stores the system data that the clone needs to remain linked to the base image and to function as a unique desktop.

View Composer creates a second disk with the OS disk. The second disk stores QuickPrep configuration data and other OS-related data that must be preserved during refresh and recompose operations. This disk is small, typically about 20MB. This disk is created whether you use QuickPrep or Sysprep to customize the desktop.
If you configure separate View Composer persistent disks to store user profiles, three disks are associated with each linked clone: the OS disk, the second desktop disk, and the View Composer persistent disk.
The second desktop disk is stored on the same datastore as the OS disk. You cannot configure this disk.

In a dedicated-assignment pool, you can configure separate View Composer persistent disks to store Windows user-profile data. This disk is optional.
Separate persistent disks let you preserve user data and settings. View Composer refresh, recompose, and rebalance operations do not affect persistent disks. You can detach a persistent disk from a linked clone and attach it to another linked clone.
If you do not configure separate persistent disks, the Windows profile is stored in the OS disk. User data and settings are removed during refresh, recompose, and rebalance operations.
You can store persistent disks on the same datastore as the OS disk or on a different datastore.

When you create a linked-clone pool, you can configure a separate, nonpersistent disk to store the guest OS's paging and temp files that are generated during user sessions. You must specify the disk size in megabytes.
This disk is optional.
When the linked clone is powered off, View Manager replaces the disposable-data disk with a copy of the original disk that View Composer created with the linked-clone pool. Linked clones can increase in size as users interact with their desktops. Using disposable-data disks can save storage space by slowing the growth of linked clones.
The disposable-data disk is stored on the same datastore as the OS disk.



Was looking for solution to increase the persistent disk space for a user today who was running out of space. I am using view 4.5 . Very easy to set the configuration to reflect the new size is future deployment of a pool . But need to do some manual work for already provisioned VM . It will a bit of pain if you already have few vm deployed already. Not sure if there is any work around but will check in future.
To start with the pool needs to be changed if all future pool machines need to selected HDD  , do the following .
1. Login to the VMware View Administrator.
2. Select the pools from the ‘Inventory.
3. Select Edit from the top menu tabs
4. Under View Composer Disk change the value of Persistent disk size to the required value
5. Click OK
From now on any new deployed vm will get the edited Persistent HDD size.However already provisioned VM from that pool will still have the old persistent HDD.Do the following fow those VM.
1. Login to the vSphere Client
2. Select the virtual machine that needs to be changed and right click selecting Edit Settings…
4. Select the Hard disk that is the current persistent disk. Make sure you are changing the right HDD . You can double check the HDD name from Vmware View Administrator console.
5. In the Disk Provisioning section change the Provisioned Size to the required size
6. Click OK.
Now restart the virtual machine and login to this with a username that got Administrative right.Then do the following.
1. Click Start and the right click on Computer selecting Manage
6. Select Disk Management
7. Select the disk to be change and right click selecting Extend Volume…
8. Click Next
9. Click Next
10. Click Finish
11. Close the window and logoff the machine
Now check the Persistent disk space from my computer to make sure you are getting the right HDD size.

Комментариев нет:

Отправить комментарий