![Dell EMC Vblock 240 Administration Manual Download Page 92](http://html1.mh-extra.com/html/dell-emc/vblock-240/vblock-240_administration-manual_2468384092.webp)
Managing VMware vSphere ESXi 6.0
Configuring the persistent scratch location (vSphere 6.0)
When all VMware vSphere ESXi hosts have been added to vCenter, you can configure the persistent
scratch location on all hosts with the tasks in this procedure.
About this task
Follow this procedure on each VMware vSphere ESXi host. VMware considers a Boot-from-SAN LUN as
a "remote disk" and may write scratch data to a RAM disk. This procedure (in conjunction with use of the
Core Dump Collector Service) is required to ensure scratch data is stored on persistent storage.
Before you begin
To perform the tasks in this procedure, you must have vSphere Client installed on a Windows machine.
You must have network access and administrative privileges to the VMware vCenter server. Data stores
must be assigned to the VMware vSphere ESXi host.
Procedure
1
Connect to vCenter Server or the VMware vSphere ESXi host using the vSphere Client.
2
Click the VMware vSphere ESXi host in the inventory, select the
Configuration
tab, highlight
Storage
in the hardware frame.
3
Right-click
Boot-from-SAN datastore
(that is,
VB20023082esx01-localstorage
), click
Browse
.
This datastore will comprise of the unused capacity of the 10 GB or 20 GB boot-from-
SAN LUN.
4
Create a uniquely-named directory for this VMware vSphere ESXi host (for
example,
.locker_ESXHostname
).
5
Close the Datastore browser.
6
Click
Advanced Settings
under the
Software
frame.
7
Select the
ScratchConfig
section.
8
Update the
ScratchConfig.ConfiguredScratchLocation
parameter field:
a
Enter the full path to directory created in the prior step, for example,
/vmfs/volumes/
VB20023082esx01-localstorage/.locker_ESXHostname
b
Click
OK
.
9
Put the VMware vSphere ESXi host into maintenance mode and reboot for the configuration
change to take effect.
Managing VMware vSphere ESXi 6.0
|
92