最後更新: 2022-10-26

NFS 慢的原因:

everything the esxi box issues is a sync write.

patching the NFS code to ignore O_SYNC commands from ESXi

async

Applications can use the O_SYNC open flag to force application writes to individual files to go to the server immediately without the use of the sync mount option.

Memory pressure forces reclamation of system memory resources.
An application flushes file data explicitly with sync(2), msync(2), or fsync(3).
An application closes a file with close(2).
The file is locked/unlocked via fcntl(2).

NFS 與 Veeam vPower NFS

veeam instant recovery

vPower NFS datastore is left mounted to the host in order to save time on mounting it again during the next vPower task.

Speed test

Esxi5.5 --> Centos6

iScsi: Avg: 176 Mbit

NFS: 17 Mbit

ESXi 5.5 add iscsi resource

"Storage Adapters" ->" Add" -> "Dynamic Discovery"

Details -> View: -> Type: disk

** Confirm to rescan the Host Bus Adapter.

Storage -> Add -> VMFS-5

ESXi 7 NFS CLI

# List the NAS volumes currently known to the ESX host.

esxcli storage nfs list

# Add a new NAS volume to the ESX Host

# --host | -H
# --share | -s         The share name on the remote system to use for this NAS mount point. (required)
# --volume-name | -v   This must be a unique volume name and cannot conflict with existing NAS, VMFS or other volume names.
# --readonly | -r

storage nfs add

# get param

esxcli storage nfs param get -v NFS_Datastore_Name

Volume Name                  MaxQueueDepth  MaxReadTransferSize  MaxWriteTransferSize
---------------------------  -------------  -------------------  --------------------
VeeamBackup_WIN-???????????     4294967295                65536                 65536

# umount

esxcli storage nfs remove -v NFS_Datastore_Name