HP StoreOnce D2D4324 HP StoreOnce VSA Deployment and Configuration Guide (TC45 - Page 17

Next&gt, Select OVF from Depot on SEM, VM name for StoreOnce VSA

Get HP StoreOnce D2D4324 PDF manuals and user guides View all HP StoreOnce D2D4324 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

5. Click Next>. Details of the ESXi server and its available datastores are displayed. Note that at this stage you are selecting the datastore for the StoreOnce VSA system files (not the data storage). This datastore requires a minimum of 50 GB. (The virtual disk created will be thin provisioned, with a capacity of 500 GB.) • Select the datastore using the radio button in the first column of the table of available datastores. • In the Select OVF from Depot on SEM drop-down list, select the required StoreOnce VSA OVF file. • Enter a name in VM name for StoreOnce VSA. This is the name that will identify the HP StoreOnce VSA, for example when it is displayed in the vCenter GUI. NOTE: For both system files (selected here) and user data storage (selected in the next step), the StoreOnce VSA is supported on VMFS3, VMFS5 and NFS datastores. StoreOnce VSA is not supported on Raw Device Mapping (RDM). 6. Click Next>. Select a datastore for the User Data Disk using the radio button in the first column of the table of available datastores. The datastore can be VMFS or NFS: • The virtual disk created from a VMFS datastore will be thick provisioned, lazy-zeroed with a capacity of 1 TB. All available datastores are displayed, but you can only select a datastore that can accommodate the 1 TB capacity requirements of the virtual disk and a maximum file size of 1 TB. • The virtual disk created from an NFS datastore will be thin provisioned with no minimum free space requirement. The maximum file size is not known to VSA because it is controlled by the NAS storage and not by VMware. However, you should ensure that the maximum file size of 1 TB is supported for NFS. Deployment process 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
5.
Click
Next>
. Details of the ESXi server and its available datastores are displayed. Note that
at this stage you are selecting the datastore for the StoreOnce VSA system files (not the data
storage). This datastore requires a minimum of 50 GB. (The virtual disk created will be thin
provisioned, with a capacity of 500 GB.)
•
Select the datastore using the radio button in the first column of the table of available
datastores.
•
In the
Select OVF from Depot on SEM
drop-down list, select the required StoreOnce VSA
OVF file.
•
Enter a name in
VM name for StoreOnce VSA
. This is the name that will identify the HP
StoreOnce VSA, for example when it is displayed in the vCenter GUI.
NOTE:
For both system files (selected here) and user data storage (selected in the next step),
the StoreOnce VSA is supported on VMFS3, VMFS5 and NFS datastores. StoreOnce VSA is
not supported on Raw Device Mapping (RDM).
6.
Click
Next>
. Select a datastore for the User Data Disk using the radio button in the first column
of the table of available datastores. The datastore can be VMFS or NFS:
•
The virtual disk created from a VMFS datastore will be thick provisioned, lazy-zeroed
with a capacity of 1 TB. All available datastores are displayed, but you can only select
a datastore that can accommodate the 1 TB capacity requirements of the virtual disk and
a maximum file size of 1 TB.
•
The virtual disk created from an NFS datastore will be thin provisioned with no minimum
free space requirement. The maximum file size is not known to VSA because it is controlled
by the NAS storage and not by VMware. However, you should ensure that the maximum
file size of 1 TB is supported for NFS.
Deployment process
17