VCAP-DTD | Objective 5.1 | Create a Physical Design for View Infrastructure Storage

Size the Events database

I’ve already covered off sizing the events database in Objective 3.2, however to recap:

Looking through release notes and other documentation, I haven’t managed to find any officially supported calculators. You can however, assume that 2.5MB per desktop per month is required for the overall sizeof the events database. In real life, 1-1.5MB is a more realistic figure, however this depends on how many refresh, logoff and recompose actions take place.

Size the View Composer database

I’ve already covered off sizing the events database in Objective 3.2, however to recap:

Again, I can’t find any official documentation or calculators that help with this sizing, however you can safely assumed that your composer database will never get close to 5GB in size. Sizing for 5GB is a safe bet.

Determine storage requirements for the Transfer Server repository

The View Transfer server has specific storage requirements which I have touched upon already in Objective 3.1:

A View Transfer server must have access to the data stores that store the desktop virtual disks to be transferred. The data stores must be accessible from the ESXI host on which the View Transfer server VM is running on.

View Transfer server can transfer a maximum of 60 disks concurrently. During a transfer operation, a local desktop’s virtual disk is mounted on the transfer server. The transfer server VM must have 4 SCSI controllers, with each having 15 slots. This config supports 60 disks to be attached to the server at any one time. This number is likely to never to be the limiting factor and network constraints  will be reached before then.

Remember that VM must be configured with an LSI Logic parallel SCSI controller. This is not the default when running through the VM creation wizard for Windows Server 2008 R2.

Other than the storage controllers, the transfer server should have 20GB storage assigned for the repository (VMware recommendation). This should reside on a network share and not on local storage. The share on which the repository resides, must have enough space to store the staid image files. Image files are the View composer base images. These disk images are sparsely provisioned. This means that only blocks with data are stored. For example, a 40GB base image may only have 7GB worth of data, therefore only providing decent space savings.

Although not a storage requirement, remember that the transfer server should use VM hardware version 7 or 8.

Determine storage requirements for infrastructure virtual machines (e.g., vCenter servers, View servers, etc.)

At this stage, we should already have set out what we need to support our View infrastructure. This will include number of:

  • vCenter Servers
  • VUM Servers
  • SQL Servers
  • AD Servers
  • Connection Servers
  • Transfer Servers
  • Security Servers
  • File Servers
  • vCNS Servers
  • vCOPS for View

Each of these will have their own storage requirements, I’d like to think that is this information was needed, they would make it available to you in the exam.