Creating
and
using
VMFS
on
the
storage
unit
for
an
Intel
host
running
VMware
ESX
Server
This
section
provides
information
for
creating
and
using
VMFS
on
the
storage
unit
for
an
Intel
host
running
VMware
ESX
Server.
After
you
partition
the
disk
as
described
in
“Partitioning
storage
unit
disks
for
an
Intel
host
running
VMware
ESX
Server”
on
page
130,
the
next
step
requires
that
you
create
a
VMFS
file
system
by
using
the
following
commands:
vmkfstools
–C
vmfs2
<device>
<device>
is
on
the
format
vmhba
<C>:<T>:<D>:<P>
,
where
<C>
is
the
virtual
host
adapter,
<T>
is
the
SCSI
ID
of
the
storage
unit,
<D>
is
the
Lun
ID,
and
<P>
refers
to
the
partition
number
to
use
on
that
device
(previously
created
with
fdisk).
In
most
cases
it
will
be
1.
[root@denethor
vmfs]#
vmkfstools
-C
vmfs2
vmhba0:4:71:1
This
is
already
a
file
system
on
vmhba0:4:71:1.
Overwrite
it
(y/n)?
y
Creating
file
system
on
vmhba0:4:71:1
with
blockSize
1048576
After
this
operation
is
completed,
the
new
file
system
is
mounted
under
/vmfs.
vmkfstools
–N
<label
name>
Note:
This
step
is
optional
but
we
strongly
recommended
that
you
do
it
because
it
can
ease
your
task
of
storage
management.
It
can
become
a
mandatory
step
if
you
do
not
configure
persistent
binding
on
VMware
ESX
Server.
Copy
Services
considerations
This
section
provides
considerations
for
using
copy
services.
Copy
Services
are
only
available
for
the
VMware
ESX
Console
OS
IBM
supports
FlashCopy
and
Remote
Mirror
and
Copy
between
different
VMware
ESX
Servers
with
the
following
limitations:
v
Copy
Services
are
only
available
for
the
VMware
ESX
Console
OS.
v
The
source
and
target
volumes
must
exist
on
separate
physical
machines.
v
Remote
Mirror
and
Copy
read
from
secondary
option
is
not
supported.
v
Rescan
of
LUNs
might
be
required.
IBM
does
not
support
“system
LUN/disk”
for
the
virtual
machine.
Therefore,
you
must
use
VMFS
1
or
2.
The
locking
mechanism
of
VMFS
might
get
confused
when
performing
copy
services
on
the
target
volume.
To
prevent
this,
it
is
mandatory
that
no
virtual
machine
using
a
copy
target
volume
is
running
during
the
copy
process.
The
source
and
target
volumes
must
be
on
separate
physical
machines
VMFS
file
system
uses
a
label
mechanism
and
if
it
encounters
2
volumes
with
the
same
label,
only
one
remains
accessible.
132
DS6000
Host
Systems
Attachment
Guide
Summary of Contents for System storage DS6000 Series
Page 1: ...IBM TotalStorage DS6000 Host Systems Attachment Guide GC26 7680 03...
Page 2: ......
Page 3: ...IBM TotalStorage DS6000 Host Systems Attachment Guide GC26 7680 03...
Page 16: ...xiv DS6000 Host Systems Attachment Guide...
Page 28: ...xxvi DS6000 Host Systems Attachment Guide...
Page 30: ...xxviii DS6000 Host Systems Attachment Guide...
Page 50: ...20 DS6000 Host Systems Attachment Guide...
Page 84: ...54 DS6000 Host Systems Attachment Guide...
Page 88: ...58 DS6000 Host Systems Attachment Guide...
Page 164: ...134 DS6000 Host Systems Attachment Guide...
Page 170: ...140 DS6000 Host Systems Attachment Guide...
Page 174: ...144 DS6000 Host Systems Attachment Guide...
Page 192: ...162 DS6000 Host Systems Attachment Guide...
Page 212: ...182 DS6000 Host Systems Attachment Guide...
Page 226: ...196 DS6000 Host Systems Attachment Guide...
Page 240: ...210 DS6000 Host Systems Attachment Guide...
Page 248: ...218 DS6000 Host Systems Attachment Guide...
Page 250: ...220 DS6000 Host Systems Attachment Guide...
Page 256: ...Taiwan class A compliance statement VS07171L 226 DS6000 Host Systems Attachment Guide...
Page 297: ......
Page 298: ...Printed in USA GC26 7680 03...