6.0

10 If the space specified for storage is excessive for your purposes, you can adjust the capacity values.
By default, the entire free space on the storage device is available.
11 Click Next.
12 In the Ready to Complete page, review the datastore configuration information and click Finish.
A datastore on the SCSI-based storage device is created. If you use the vCenter Server system to manage
your hosts, the newly created datastore is added to all hosts.
Create NFS Datastore in the vSphere Client
You can use the Add Storage wizard to mount an NFS volume and use it as if it were a VMFS datastore.
Prerequisites
Launch the vSphere Client and log in to a vCenter Server system.
Because NFS requires network connectivity to access data stored on remote servers, before configuring NFS,
you must first configure VMkernel networking.
Procedure
1 Log in to the vSphere Client and select the host from the Inventory panel.
2 Click the Configuration tab and click Storage in the Hardware panel.
3 Click Datastores and click Add Storage.
4 Select Network File System as the storage type and click Next.
5 Enter the server name, the mount point folder name, and the datastore name.
For the server name, you can enter an IP address, a DNS name, or an NFS UUID.
NOTE When you mount the same NFS volume on different hosts, make sure that the server and folder
names are identical across the hosts. If the names do not match exactly, the hosts see the same NFS
volume as two different datastores. This might result in a failure of such features as vMotion. An
example of such discrepancy could be if you enter filer as the server name on one host and
filer.domain.com on the other.
6 (Optional) Select Mount NFS read only if the volume is exported as read only by the NFS server.
7 Click Next.
8 In the Network File System Summary page, review the configuration options and click Finish.
Managing Duplicate VMFS Datastores
When a storage device contains a VMFS datastore copy, you can mount the datastore with the existing
signature or assign a new signature.
Each VMFS datastore created in a storage disk has a unique signature, also called UUID, that is stored in the
file system superblock. When the storage disk is replicated or its snapshot is taken on the storage side, the
resulting disk copy is identical, byte-for-byte, with the original disk. As a result, if the original storage disk
contains a VMFS datastore with UUID X, the disk copy appears to contain an identical VMFS datastore, or a
VMFS datastore copy, with exactly the same UUID X.
In addition to LUN snapshotting and replication, the following storage device operations might cause ESXi
to mark the existing datastore on the device as a copy of the original datastore:
n
LUN ID changes
n
SCSI device type changes, for example, from SCSI-2 to SCSI-3
vSphere Administration with the vSphere Client
324 VMware, Inc.