c oncerto 700 0 all flash array best practices · the document should be used as a companion to the...
TRANSCRIPT
C
Conccerto
B
o 700
Best P
0 All
Pract
l Flas
tices
Documen
sh Ar
nt Number: 53
rray
35‐0165‐00 R
November
1
Rev 01
r 2014
2
LEGAL NOTICE
Copyright © 2010‐2014 Violin Memory, Inc. All rights reserved.
Violin Memory, Violin, vSHARE, vCACHE, Flash Forward, and the Violin logo are trademarks or registered trademarks of Violin Memory, Inc. (“Violin”) in the United States and other countries.
All other brands, product names, company names, trademarks, and service marks are the properties of their respective owners.
Licenses of Violin’s software are subject to the terms and conditions set forth in Violin’s End User License Agreement. Sales of Violin’s hardware are subject to Violin’s Terms and Conditions applicable to sales of hardware.
Violin Memory, Inc. 4555 Great America Parkway Santa Clara, CA 95054 USA
3
Table of Contents 1 About This Guide ................................................................................................................................... 5
1.1 Intended Audience ........................................................................................................................ 5
1.2 How to Use This Guide .................................................................................................................. 5
1.3 Reference Documents ................................................................................................................... 5
2 Introduction .......................................................................................................................................... 6
3 Connectivity .......................................................................................................................................... 7
3.1 Southbound Connectivity Options ................................................................................................ 7
3.1.1 Port Configuration ................................................................................................................. 7
3.1.2 FC Direct Connect (Concerto 7100) ...................................................................................... 8
3.1.3 Fibre Channel Switch Attach (Concerto 7200) ...................................................................... 9
3.2 Scale‐Up Configurations .............................................................................................................. 10
3.3 Southbound Zoning Considerations ............................................................................................ 10
3.4 Southbound Path Status ............................................................................................................. 10
3.5 Southbound Array Configuration Best Practices ........................................................................ 11
3.5.1 Array LUN Configuration ..................................................................................................... 11
3.5.2 Array LUN Export................................................................................................................. 11
3.5 Performance Best Practices ............................................................................................................ 11
4 HA Configuration & Best Practices ...................................................................................................... 12
4.1 HA Configuration Prerequisites .................................................................................................. 12
4.2 HA Configuration Best Practices ................................................................................................. 12
4.3 Configuration Repository ............................................................................................................ 12
4.4 Email Alerts ................................................................................................................................. 14
5 Northbound Connectivity Best Practices ............................................................................................ 14
5.1 Northbound Ports ....................................................................................................................... 14
5.2 Northbound Zoning Recommendations ..................................................................................... 15
5.3 Brocade Switch Best Practices .................................................................................................... 15
5.4 Host Connectivity ........................................................................................................................ 15
5.5 iSCSI Connectivity Best Practices ................................................................................................ 16
6 Snapshots and Clones ......................................................................................................................... 20
Appendix A. Configuring HA on Concerto Controllers ................................................................................ 21
Configure Network for HA ...................................................................................................................... 21
Set up Configuration Repositories .......................................................................................................... 21
4
Enable Target Mode Ports ...................................................................................................................... 25
Run Failover Setup Wizard ...................................................................................................................... 26
Appendix B. Creating MemClones on Individual MemSnaps using the Concerto Management Console .. 36
Appendix C. Creating MemClones on a Snapshot Group using the Concerto Management Console ....... 40
Appendix D. Refresh data on an Existing MemClone ................................................................................. 43
Appendix F. Remapping a MemClone in a Windows 2012 Failover Cluster ............................................... 48
5
1 About This Guide
1.1 Intended Audience
The content in this guide is intended for IT professionals who have experience with and
knowledge of installing and configuring storage systems in Fibre Channel and/or iSCSI storage
network environment.
1.2 How to Use This Guide
This document provides instructions and best practices recommendations for connecting,
configuring, and optimizing the Violin Concerto 7000 Flash Array in a Fibre Channel or iSCSI
storage network.
The document should be used as a companion to the Concerto 7000 All Flash Array Installation
Guide when installing and configuring a Concerto array, providing both specific instructions for
setup and best practice considerations for performance and usability.
1.3 Reference Documents
Violin Memory Documentation
The following guides are available for download from the Violin Memory Support Web site.
Concerto 7000 All Flash Array Installation Guide
Concerto 7000 All Flash Array User’s Guide
Violin 6000 Series Memory Array User’s Guide
Violin Memory Interoperability Best Practices Guide
3rd Party Documentation
Brocade Fabric OS Administrators Guide (Fabric OS 7.3.0)
6
2 Introduction This document is a collection of best practices to follow when deploying Violin Concerto 7000. It
covers best practices for initial connectivity setup, high availability configuration and
mirroring/replication.
The Concerto 7000 All Flash Array consists of high performance Flash Arrays paired with two highly available controllers, and optional Fibre Channel switches. The Concerto 7000 All Flash Array integrates comprehensive data services that solve enterprise challenges in the following ways:
Delivers flexible and powerful business continuity with asynchronous and synchronous replication capabilities.
Reduces the amount of required storage through data efficiency technologies, such as thin provisioning and snapshots.
Protects valuable enterprise data using protection features such as clones, mirroring and encryption.
Scales up to four Flash Arrays with hundreds of terabytes of data.
Transforms performance with enterprise‐class capabilities.
Concerto’s highly available active/active controllers allow administrators to manage applications and users with the flexibility required in enterprise environments. The Concerto 7100 provides up to two storage shelves or 140TB of raw capacity without a fabric switch. The Concerto 7200 provides up to four storage shelves with two fabric switches for 280TB raw capacity.
3 Con
3.1 SoTh
m
C
a
R
in
Th
fo
p
Th
fo
ar
3.1.1 PSe
C
d
Po
Et
iD
nnectivity
uthbound Chere are two
maximum of tw
oncerto 7200
pair of Fibre
efer to the Co
nstallation.
he illustration
or port numb
opulated in P
he illustration
or port numb
re populated
ort Configuree the diagra
oncerto 7000
escription for
ort
th0
DRAC
y
Connectivitytypes of Con
wo Flash Arra
0 is a pair of C
Channel swit
oncerto 7000
n below show
ering informa
PCIe slots 2, 4
n below show
ering informa
in PCIe slots
ration m above for t
0 Controller. T
r their use in
Type
1G Embe
Out‐of‐ba
y Options certo 7000 A
ays, directly c
Concerto Cont
tches.
All Flash Arra
ws the rear of
ation as you m
, 5 and 7.
ws the rear of
ation as you m
5/6 and the i
the locations
The table belo
a SAN configu
edded RJ‐45 Et
and Managem
ll Flash Array
onnected to
trollers conne
ay Installation
a Concerto 7
make the FC c
a Concerto 7
make the FC a
SCSI cards ar
of the netwo
ow displays th
uration.
hernet
ment
y configuratio
a pair of Con
ected to thre
n Guide for a
7000 Fibre Ch
connections.
7000 Fibre Ch
and iSCSI con
re populated
ork and storag
he types of e
Usage
Manage
Used foaccess a
ns. The Conc
certo Contro
e or more Fla
dditional det
hannel Contro
Note that FC
hannel Contro
nections. Not
in slots 1/2.
ge ports on t
ach port and
ement and Hig
r power manaand remote co
erto 7100 ha
llers. The
ash arrays thr
ails on system
oller. Refer to
cards are
oller. Refer to
te that FC car
he rear pane
gives a
h Availability
gement, virtuansole capabilit
7
s a
rough
m
o this
o this
rds
l of a
al media ties
Et
SC
FC
EtEt
3.1.2 FC
3.1.2.1
3.1.2.2
th2, Eth3
CI‐0, SCI‐1
C100 ‐ FC115
th4, Eth5, Eth6th7
C Direct ConIn this config
arrays.
FC Direct Con
In this config
Controllers.
We recomme
the array are
FC Direct Con
In this config
We recomme
each array ar
10G Ethe
10G Ethe
8G Fiber
6, 10G Ethe
nnect (Conceguration, the C
nnect with Sin
guration, a sin
end that each
e used for ma
nnect with Tw
guration, two
end that each
re used for m
ernet (Dual‐por
ernet (Dual‐por
Channel (Quad
ernet (Dual‐por
erto 7100) Concerto Con
ngle Flash Arra
ngle Flash Arr
h MG is conne
ximum throu
wo Flash Array
Flash Arrays
h MG is conne
aximum thro
rt SFP Fiber NIC
rt SFP Fiber NIC
d‐port FC HBAs
rt SFP Fiber NIC
ntrollers are d
ay (Concerto
ay is directly
ected to each
ghput capaci
ys (Concerto 7
are directly c
ected to each
oughput capac
C) Replicat
C) Storage
s) FC portssouthboControll
Cs) iSCSI poconnectand clie
directly conne
7100)
connected to
h controller, a
ty.
7100)
connected to
h controller, a
city.
tion and High A
Cluster Interc
s used for nortound I/O conneler
orts used for notivity between nts
ected to up to
o a pair of Con
and that all ei
a pair of Con
and that all ei
Availability
onnect
thbound and ectivity of the
orthbound I/O the Concerto
o two Violin F
ncerto
ight FC ports
certo Contro
ight FC ports
8
Concerto
Controller
Flash
on
llers.
on
3.1.3 FIn
C
Th
w
Th
Fl
ibre Channen this configu
hannel switch
he diagram b
with two Flash
he diagram b
lash Arrays.
l Switch Attaration, the Co
hes to three o
elow outlines
h Arrays.
elow outlines
ach (Concertoncerto Contr
or more Flash
s the connect
s the connect
to 7200) rollers are co
h Arrays.
tions for a set
tions for a set
nnected thro
t of Fibre Cha
t of iSCSI Con
ough a pair of
annel Concert
certo Contro
f redundant F
to Controllers
llers, with tw
9
ibre
s,
wo
3.2 ScaVio
3.3 So
Zo
so
Co
mo
mo
arr
Ref
con
3.4 SoWheacdowpatbac To Notdow
ale‐Up Confolin supports
uthbound Z
ne each Conc
uthbound Vio
oncerto Contr
ore than one
ore than eigh
ray.
fer to the Con
nfiguration.
uthbound Phen all southbch path for a Fwn, either by th, upon restock to Load Ba
rescan the adte that there wnstream pat
figurations up to four ar
Zoning Cons
certo Control
olin array. For
oller, then ea
port on each
t paths to any
ncerto 7000 A
Path Status bound paths aFibre Channereloading a Moring the pathlancing, an ad
dapter, right‐cmay be a moths are rescan
rrays behind a
siderations
ler initiator p
r instance, if w
ach initiator p
of the two V
y specific LUN
All Flash Array
are up, the Col Device as “LMemory Gateh, the path stdapter rescan
click on Physiomentary pernned.
a set of Conce
port with no m
wiring two Vi
port on the Co
Violin Flash Ar
N from the Co
y Installation
oncerto ManaLoad Balancineway (MG) in tatus may go tn is required.
ical Resourcesformance im
erto Controlle
more than on
olin Flash Arr
oncerto Cont
rrays. This he
oncerto Contr
Guide for add
agement Conng”. When a sa downstreato Standby‐A
s ‐> Physical Apact to upstr
ers.
e target port
rays southbou
roller should
lps to ensure
roller initiato
ditional detai
nsole shows tsouthbound pam Violin arraActive. To get
Adapters andeam clients w
on each
und from a
be zoned to
that there ar
r port to the
ls on zoning
he Path Statupath is broughay or removinthe paths sta
d select Rescawhile the
10
no
re no
us of ht g a atus
an.
11
3.5 Southbound Array Configuration Best Practices
3.5.1 Array LUN Configuration The Violin array connected southbound from the Concerto Controller will present LUNs that will
be virtualized by the Concerto Controller as Virtual devices.
Please use the following guidelines when creating LUNs on the Violin array:
Create 8 LUNs per Violin array. Each Concerto Controller will utilize 4 LUNs on the array
(excluding Configuration Repository). This is recommended for optimal performance.
LUNs created on the array for the Concerto Controller should be non‐ALUA and Thick allocation.
3.5.2 Array LUN Export Violin recommends the following guidelines when exporting LUNs from a southbound Violin
array to the Concerto Controller:
Utilize igroups on the Memory Gateways (MGs) of the Violin array(s) to export LUNs to the
Concerto Controller.
When creating the igroups, use names that represent the Concerto hostname and physical
location, should remote mirroring or replication be implemented at some point.
Export the LUNs through all MGs on each array. Proper zoning (see section Southbound
Zoning Recommendations) will ensure that each Concerto port sees the correct number of
paths per LUN.
3.5 Performance Best Practices In order to allow for optimal performance, ensure that all of the connectivity best practices are
followed.
Violin recommends that at a minimum, four LUNs are created from each southbound array
for each Concerto Controller. For example, in a single array environment, a total of eight data
LUNs (in addition to the Configuration Repository LUNs) would be created—and four would
be used by each Concerto Controller.
As vLUNs are created from the Concerto Controller, a round robin distribution is used to
distribute the vLUNs across the physical LUNs created on the southbound Violin array(s). For
this reason, it is recommended that multiple vLUNs are created and used for each application
so that I/O can be distributed among the multiple logical devices.
12
4 HA Configuration & Best Practices
Concerto 7000 Controllers are always installed in failover pairs to ensure high availability. Failover
pairs guarantee mutual access to application clients in an active‐active configuration, while
ensuring that in the event of a Concerto failure client access will be taken over by the partner node.
4.1 HA Configuration Prerequisites In order to properly set up the Concerto 7000 Controllers in a highly available pair, first ensure
that the following pre‐requisites are met:
The management connection (Eth0) on each Concerto Controller must be configured with a
unique static IP address. The IP addresses of the Eth0 ports on both Concerto Controllers
must be on the same subnet.
Each Concerto 7000 Controller must have access to a 15GB LUN on the Violin array to use for
its configuration repository. Both Concertos in the HA pair must be able to access each LUN.
For an HA configuration in a Fiber Channel SAN, the 10Gb SCI‐0 and SCI‐1 ports of the
Concerto Controllers must be connected to each other with a LC fibre cable. These ports must
also be configured with unique IP addresses in the same subnet.
The number of physical Fibre Channel ports which are set to Target mode must be the same
on both Concerto Controllers. Each port which will be used as a target must be set to target
mode.
4.2 HA Configuration Best Practices When preparing and configuring the Concerto Controllers for an HA configuration, consider the
best practices below:
Create a separate Storage Pool on each Concerto Controller specifically for the 15GB LUNs
used for the configuration repositories. These two Storage Pools, one per controller, should
have no other devices or LUNs in them. This will allow data services features to be applied to
those LUNs (such as Mirroring) and will make a later transition to Stretch Clustering easier.
It is recommended in deployments with multiple arrays, that the configuration repository is
mirrored, so two 15GB LUNs will be required for each Concerto Controller (see “Configuration
Repository” for more information).
Please refer to Appendix A for detailed step‐by‐step instructions on how to set up HA.
4.3 Configuration Repository The Concerto Controllers use a 15GB LUN exported from the southbound Violin array as a
configuration repository. The repository maintains a continuously updated image of the system
configuration on the controllers. Violin recommends mirroring the configuration repository on
each Concerto Controller to another virtual device, if possible on a different physical array.
In o
See
Fig
On
see
cre
order for the
In addition t
15GB LUN w
Example, if t
15GB LUNs.
and the othe
The Violin LU
to both Con
On the Conc
a Storage Po
used as the
e Fig 1 below
ure 1 Logical
ce the Config
en by both Co
ated by right
configuration
to the 15GB L
will need to be
two arrays ar
One of the L
er LUN will be
UN which wil
certo Contro
certo, the virt
ool that is set
mirror must
for logical vie
view of mirro
guration Repo
oncertos and c
clicking on th
n repository t
LUN created o
e created on
re attached to
UNs will be th
e the Mirror o
l be used for
llers. They mu
tual device th
t with the Prim
be in a Storag
ew of mirrore
ored configur
ository is crea
configured in
he Configurat
to be mirrored
on an array fo
a different ar
o the Concert
he Primary Co
of the Configu
the configura
ust have conc
hat holds the c
mary Storage
ge Pool set w
ed Configurat
ation reposito
ted and the v
n a Storage Po
tion Reposito
d, the followi
or the Configu
rray to functio
to Controllers
onfiguration
uration Repo
ation reposito
current non‐E
configuration
e attribute. Th
with the Remo
tion Repositor
ories
virtual device
ool, the mirro
ry in the UI a
ing requireme
uration Repos
on as the mir
s, then each a
Repository fo
sitory on the
ory mirror mu
Exclusive acce
n repository m
he virtual dev
ote Storage at
ries.
e being used f
or of the repo
nd selecting A
ents must be
sitory, a seco
rrored copy. F
array will have
or the control
other contro
ust be presen
ess to the dev
must be adde
vice which wil
ttribute.
for the mirror
ository can be
Add…
13
met:
nd
For
e two
ller,
oller.
nted
vice.
ed to
l be
r is
4.4 Em
Em
pro
are
Em
Con
5 Nor
5.1 NoThe
Con
Wh
item
mail Alerts
ail alerts help
oactively iden
e configured a
ail alerts can
ncerto Contro
Alerts can b
attachments
server is con
It is recomm
higher to pr
Error severit
rthbound
orthbound Pe following FC
ntrollers and
hen wiring Co
ms below to h
If any FC po
Use the sam
if FC ports 1
use the sam
p inform syste
tify potential
and enabled o
be configure
oller and sele
e configured
s can be at le
nfigured to al
mended that a
oactively iden
ty or higher is
Connect
Ports C Ports should
therefore set
ncerto Contr
help ensure s
rts are unuse
me FC ports as
12,111,103, a
me ports as Ta
em administr
l system and
on both Conc
ed in the Violi
cting Email A
to capture an
ast 80MB in s
low attachme
alerts are con
ntify possible
s acceptable.
tivity Best
d be used for
t as dual‐mod
102
106
110
113
ollers into a F
successful imp
d, set those p
s dual‐mode T
and 107 are t
rgets on the o
rators of prob
component f
erto Controll
n Manageme
Alerts. Conside
n X‐Ray (diagn
size and could
ent of this siz
figured to se
e issues. If too
t Practice
application s
de Target port
103
107
111
112
Fibre Channe
plementation
ports on both
Target ports o
the only ports
other Concer
blems with th
failures. It is r
ers to help w
ent Console b
er the followi
nostic) anytim
d grow to mo
ze.
nd events wit
o many alerts
s
server connec
ts:
l SAN, please
n and reliable
h Concerto Co
on both Conc
s set to Targe
rto Controller
eir Concerto
recommended
with optimum
y right‐clickin
ing when ena
me an alert is
ore. Be sure th
th a severity
become a pr
ctivity to the
consider the
high perform
ontrollers to I
certo Controll
et mode on on
r.
Controllers a
d that Email A
service uptim
ng on each
abling email a
s sent. X‐Ray
hat your SMT
of Warning o
roblem, settin
Concerto
e Best Practice
mance:
nitiator mode
lers. For insta
ne Concerto,
14
nd
Alerts
me.
alerts:
TP
or
ng to
e
e.
ance,
then
15
5.2 Northbound Zoning Recommendations Consider the following recommendations when zoning application servers with the Concerto
Controllers FC ports used as dual‐mode Target ports:
The Concerto 7000 requires isolated zoning, where one initiator is zoned to one target in order to minimize I/O interruptions by non‐related FC activities, such as logging in and out, resets, and so on. With isolated zoning, each zone can contain no more than two ports or two WWPNs. This applies to both initiator zones (storage) and target zones (hosts). For example, in the case of northbound (to client) zoning, if there are two client initiators, and two Concerto 7000 targets on the same FC fabric, four specific zones – one for each path – should be used, as it is done for southbound (to storage) zoning. If there are two Concerto 7000 initiators and two storage targets on the same fabric, there should be four zones.
When creating zones for the connections between application servers and the Concerto
target ports, use names that imply the source server, Concerto hostname or site, and
Concerto target port number. This will make identification and troubleshooting easier.
Make sure that the storage devices are not zoned directly connected to the client.
5.3 Brocade Switch Best Practices For Brocade 8G switch ports connecting between initiator ports and target ports, Violin
recommends that you set the fillword to mode 3 (aa‐then‐ia) using the portcfgfillword command.
The following fillword modes are supported on a Brocade 8G switch running FOS firmware 6.3.1a
and later (see Brocade Fabric OS Administrator’s Guide for more information):
admin> portcfgfillword Usage: portCfgFillWord PortNumber Mode [Passive] Mode: 0/-idle-idle - IDLE in Link Init, IDLE as fill word (default) 1/-arbff-arbff - ARBFF in Link Init, ARBFF as fill word 2/-idle-arbff - IDLE in Link Init, ARBFF as fill word (SW) 3/-aa-then-ia - If ARBFF/ARBFF failed, then do IDLE/ARBFF
Note: The 16G platform (Condor3) automatically detects which fillword it should use, so there is
no need to use the portcfgfillword command.
5.4 Host Connectivity For host connectivity best practices, please refer to the Violin Memory Interoperability Best
Practices Guide, which is available on the Violin Memory Support Portal.
For host operating system support details, please refer to the Violin Memory Interoperability
Matrix.
5.5 iSCFor
700
por
We
clie
Init
Sel
CSI Connectr iSCSI, use IP
00 iSCSI targe
rts.
e recommend
ents. To set th
tiator Propert
ect the Config
ivity Best Paddresses on
et port. An exa
d the use of M
his option, hig
ties Window:
gure Multiple
ractices n different su
ample would
Multiple Conn
ghlight the ap
e Connected S
bnets when u
be using IP a
ected Session
ppropriate tar
Session (MCS
using more th
addresses 1.0
ns to improve
rget, and sele
S) option:
han one port
0.2.x and 1.0.3
e performanc
ect properties
on the Conce
3.x for the tar
ce on Window
s in the iSCSI
16
erto
rget
ws
Sel
ect Add to addd additional connections:
17
Sel
On
and
ect Advanced
ce you are do
d the initiator
d and choose
one, you shou
r.
each initiato
uld have a line
r/target IP co
e displayed fo
ombination:
or each path yyou have bet
tween the tar
18
rget
For
Pra
r additional iS
actices Guide.
SCSI considera
ations, please
e refer to the Violin Memo
ory Interoperaability Best
19
20
6 Snapshots and Clones
A snapshot is a point‐in‐time capture of a LUN at any given moment. The snapshot initially uses no
disk space, but starts to consume space as new data is written to the source volume.
Creation of snapshots, or MemSnaps in Concerto is instantaneous. Snapshot agents on client can be
used to quiesce applications and flush cache to disk for transactional integrity. The vLUN can be
either permanently rolled back to any snapshot state, or a temporary image (MemView) can be
generated.
A MemClone is a virtual device which is created from a MemSnap and allows access to the snapshot
data on the MemSnap. MemClone devices are read/write, but MemSnaps cannot be created on
MemClones.
A MemClone allows you to mount a point‐in‐time capture of a vLUN, based on an existing
MemSnap. A MemSnap Copy can be used if you want to restore files from a given vLUN but do not
want to roll back the original vLUN to a previous point in time. MemSnap copies can also be used to
export a given MemClone to a second host for analysis, metrics, etc. Once you have a MemClone
created and assigned to one or more SAN clients, you can also remap (or refresh) the data on that
MemClone to match the contents of a different MemSnap for that particular vLUN. Refer to
Appendix E for more details.
Refer to Appendix B for steps to create a MemClone on individual MemSnaps.
Refer to Appendix C for steps to create MemClones on a group of MemSnaps.
Refer to Appendix D for details on an automated approach to creating and exporting MemClones.
Term Definition
MemSnap Point‐in‐time snapshot of a vLUN
MemClone Virtual device which is created from a MemSnap and then allows access to the data on that MemSnap
MemSnap Copy A fully allocated and mountable virtual device which is created and copied from a MemSnap. Since a MemSnap Copy is a fully allocated virtual device, a user can create MemSnaps on it.
Appen
Fi
Co1
Set2
dix A. Con
irst, ensure th
- Each
Conce
- Each
- Two L
heads
- It is re
nfigure Net. Set SCI‐0 a
Network. E
communic
t up Configu. Discover th
selecting R
nfiguring
hat pre‐requi
Concerto Con
erto Managem
network inte
LUNs (one pe
s. These LUNs
ecommended
twork for Hand SCI‐1 IPs t
Each of these
cation.
uration Rephe Configurat
Rescan.
HA on Co
sites have be
ntroller is acc
ment Console
rface(eth0) h
r Controller),
s will be used
d that you mir
A to unique val
e must be on a
positories tion Reposito
oncerto C
en met:
essible throu
e.
as unique IPs
each of size
for the confi
rror each con
ues by select
a separate su
ory LUNs by ri
Controller
gh its manag
s on each Con
15G, are crea
iguration rep
nfiguration re
ing System M
ubnet, and are
ight‐clicking o
rs
gement interf
ntroller.
ated and expo
ositories.
pository.
Maintenance ‐
e used for int
on Physical Ad
ace using the
orted to both
‐> Configure
ter‐cluster
dapters and
21
e
h
3
4
. Select Disc
. Click on Ph
the scan. S
Properties
cover New De
hysical Device
Select each de
s.
evices and lea
es‐>Fiber Cha
evice intende
ave defaults, c
nnel Devices
ed to be used
click OK.
to see the ne
for a Configu
ew devices (L
uration Repos
LUNs) found d
sitory and sel
22
during
ect
5
6
. Select “Re
. Enable the
Enable Con
served for Vir
e Configuratio
nfiguration Re
rtual Device”
on Repository
epository.
.
y by right‐clickking on each server and se
electing Optio
23
ons ‐>
7. Walk throu
Device.
ugh the wizarrd on each coontroller and sselect the devvice you alloccated as a Vir
24
rtual
8
En9
. Once the c
on the Gen
able Target. Enable FC
Target Mo
configuration
neral Tab.
t Mode PortTarget Mode
ode. This is on
repository is
ts e by right‐click
nly applicable
s successfully
king on each
for FC config
created, you
server and se
gurations.
will see it ap
electing Optio
ppear as “Onli
ons ‐> Enable
25
ine”
FC
10
N
th
Ru1
0. Select eachclick and s
be used fo
ote: If any of
hose ports sh
n Failover S1. On one co
h adapter po
elect Enable T
or northbound
f the Target M
ould be set b
Setup Wizarntroller, right
rt which you
Target Mode
d connectivity
Mode ports w
ack to Initiato
rd t‐click and se
will be using
. Ports 102, 1
y. This is only
will not be use
or mode.
lect Failover ‐
for northbou
103, 106, 107,
y applicable f
ed or connect
‐> Failover Se
und (client) co
, 110, 111, 11
for FC configu
ted to an upst
etup Wizard.
onnectivity, ri
12 and 113 sh
urations.
tream FC swit
26
ight‐
hould
tch,
122. Walk throuugh the wizarrd and select yes to “Do yoou want to reescan the phyysical devices”
27
”.
13
14
3. Select youensure tha
4. Leave defa
r secondary(f
at “Mutual Fa
ault user acco
failover) Conc
ailover” is sele
ounts.
certo Control
ected.
ler from the list of availab
ble servers, an
28
nd
155. Select “yess” to rescanning physical ddevices on thee failover serrver.
29
16
17
6. Ensure thaController
7. Select onlysubnet, no
at the Storage
.
y eth0 for the
ot the eth0 IP
e Cluster Inte
e Failover Net
address.
rlink (SCI‐0, S
twork Interfac
SCI‐1) IPs are
ces. The IP sh
unique on ea
hown in this w
ach Concerto
window is the
30
e
188. Ensure thaThese are
at the manage
the IPs which
ement IP add
h will be used
dresses (eth0)
to manage t
) of the Conce
he Concerto
erto Controlle
Controllers.
ers are correc
31
ct.
19
20
9. Set uniqueused inter
interface (
Controller
Concerto C
0. Select Stanproperly zo
It is recom
Concerto b
Controller
e IPs for the h
nally by the C
eth0) on each
managemen
Controller to
ndby FC Ports
oned.
mmended that
be configured
.
health monito
Concerto Con
h controller. E
t IPs. These I
monitor each
s for each Tar
t the Standby
d to the Targe
oring addresse
trollers and v
Ensure that t
IPs will be use
h other’s heal
rget Port. Ens
y WWPN for e
et WWPN of t
es. The Healt
virtual IPs add
hese are on t
ed internally
lth.
sure that the s
each Target m
the same ada
h Monitoring
ded to the Ma
the same sub
to the cluster
standby FC po
mode adapter
apter on its pa
g IP addresses
anagement
net as the
r, for each
orts are activ
r on each
artner Conce
32
s are
ve and
rto
2
For examp
failover to
1. Configure etc. setup
reboot of t
ple, if you are
port 100 on
the Power Co
on the serve
the Concerto
configuring p
the second n
ontrol Option
r’s iDRAC mo
Controller.
port 100 on th
ode.
ns to IPMI and
dule. Change
he first node
d enter the pr
es to the iDRA
make sure it
roper usernam
AC configurati
is configured
me, password
ion will requi
33
d to
d,
re a
22
23
2. Review the
3. Once the FFailover St
e Failover Con
Failover Setup
tate is Norma
nfiguration D
p is complete
l.
etails.
ed, ensure thaat the Failoveer Information
n tab shows t
34
hat
35
Appen
Concer This sectio
individual
Resource
First, ensu
-
1. Right
2. Walk
dix B. Cre
rto Mana
on describes
l vLUN. For in
Group, see A
ure that prere
Ensure tha
created.
click on vLUN
through the w
eating Me
gement C
the process f
formation on
Appendix C.
equisites have
at vLUN has b
N, and select
wizard to cre
emClones
Console
for creating a
n creating Me
e been met:
been created,
MemSnap/CD
ate the Mem
on Indivi
MemClone o
emClones from
and that at le
DP ‐> MemClo
Clone resour
idual Mem
of a point‐in‐t
m the MemSn
east one Mem
one.
rce.
mSnaps u
time MemSna
naps of all vL
mSnap of tha
using the
ap from an
UNs in a SAN
t vLUN has b
36
een
3. After proceeding through the wwizard, ensuree that the dessired settings
s are confirmeed.
37
4. Confir
5. Once
Resou
rmation is pro
the MemClo
urces.
ovided that th
ne is created,
he MemClone
, it will be sho
e was created
own in the Co
d.
oncerto Manaagement Console under SA
38
AN
6. Now,
7. Proce
you can right
eed through t
t click on the
he wizard to
MemClone a
assign MemC
nd assign it t
Clone to one o
o a SAN Clien
or more SAN
nt.
Clients.
39
Appen
Concer
When a G
that grou
clicking on
While the
MemClon
each vLUN
all vLUNs
First, ensu
- -
1. For ea
2. Proce
3. Unde
Assign
dix C. Cre
rto Mana
Group is creat
p so that a po
n the Group a
e user can cre
ne of each vLU
N in the group
in a Group.
ure that prere
Ensure tha
Ensure tha
created fo
ach vLUN in t
eed through t
r SAN Clients
n.
eating Me
gement C
ed that conta
oint‐in‐time M
and selecting
ate a MemSn
UN cannot be
p. This Appen
equisites have
at vLUNs have
at Group has
r the snapsho
he group, rig
the wizard to
, select the cl
emClones
Console
ains several S
MemSnap of a
MemSnap‐>C
nap of all vLU
e done this wa
ndix section e
e been met:
e been create
been created
ot group
ht click and s
create the M
lient that you
on a Sna
AN Resource
all vLUNs in th
Create.
Ns in a group
ay. The user m
explains how t
ed
d, and that at
elect MemSn
MemClone.
u would like to
apshot Gr
s (vLUNs), Me
he Group can
p through one
must individu
to create a M
least one Me
nap/CDP ‐> M
o export the
roup using
emSnap can
n be created b
e menu item,
ually create a
MemClone fro
emSnap per v
MemClone.
MemClones t
g the
be enabled o
by simply righ
creating a
MemClone fo
om a MemSna
vLUN has bee
to, and select
40
n
ht‐
or
ap on
n
t
4. Selecct all of the MMemClones that you wouldd like to assignn to the SAN Client.
41
5. Proce
eed through the wizard andd ensure the information oon the confirmation screeen is correct.
42
Appen
The Rema
match the
to remap
Prerequis
‐ M
‐ M
1. Existin
taken
dix D. Ref
ap feature of
e data on a di
an existing M
ites:
Multiple Mem
MemClone cre
ng MemClone
before data
fresh data
Concerto can
ifferent Mem
MemClone.
mSnaps create
eated and ass
e (Disk 6, Mo
was added to
a on an E
n be used to r
mSnap for that
ed on vLUN
signed to SAN
unted to C:\S
o primary vLU
xisting M
refresh the da
t particular vL
N Client
SQL_MemClo
UN).
emClone
ata on an exis
LUN. Refer to
ne) with no d
e
sting/assigned
o the instructi
data (initial M
d MemClone
ions below on
MemSnap was
43
to
n how
s
2. Rema
3. Select
ap MemClone
t newer Mem
e to newer Me
mSnap.
emSnap (withh data):
44
4. Select
5. Resca
autom
t new MemCl
an Host B and
matically bring
lone name.
Bring Disk 7
g device onlin
Online (if des
ne) :
sired, Windowws behavior ccan be modifiied to
45
6. Disk 77 now has thee updated datta:
46
47
Appen
A vLUN ex
the MemS
to clients
When a M
MemClon
When a M
remappin
lead to un
from the c
Mode.
The steps
Cluster:
1. We st
in Fai
2. If the
3. In the
and se
dix F. Rem
xported on a
Snaps, an adm
and mounted
MemClone is m
ne by selecting
MemClone is m
g the MemCl
npredictable b
cluster disk d
below show
tart with Mem
lover Cluster
re is a Cluster
e Failover Clus
elect Turn On
mapping a
Concerto Con
ministrator ca
d to perform
mounted on a
g a different
mounted in a
one causes a
behavior whe
uring Remap
how to prope
mClone device
Manager.
r Role, such a
ster Manager
n Maintenanc
a MemClo
ntroller can c
an create a M
tasks such as
a client, diffe
MemSnap. Th
Windows Clu
n OS disk obj
en the MemC
, it is recomm
erly Remap a
e connected
s SQL Server,
r, set the clus
ce Mode:
one in a W
ontain point‐
MemClone, wh
s restoring da
rent points in
his process is
uster as a clu
ect removal w
Clone is remou
mended to firs
MemClone m
as cluster dis
, using the clu
ter disk to M
Windows
‐in‐time snap
hich is a virtu
ta, running te
n time can be
called a Rem
ster disk or C
which will tak
unted. To pre
st set the clus
mounted in a
k 4 and moun
uster disk ma
Maintenance M
2012 Fai
shots, called
al device that
ests, or execu
e instantly rem
map.
CSV (Cluster S
ke cluster dis
event unpred
ster disk to M
Windows 20
nted as drive
rk the role Of
Mode by right
lover Clu
MemSnaps. F
t can be assig
uting reports.
mapped in the
hared Volum
k Offline. This
ictable behav
Maintenance
012 Failover
M: shown be
ffline.
t‐clicking the
48
ster
From
gned
.
e
e),
s will
vior
elow
disk
Note
the Su
4. In the
Rema
5. After
turn o
Maint
Note
that the clust
uspend‐Cluste
e Concerto Ma
ap. Then selec
the Concerto
off maintenan
tenance Mod
that you can
ter disk can a
erResource Cm
anagement C
ct the MemSn
o remaps the
nce mode by
de.
also use the
lso be set to
mdlet:
Console, selec
nap image (po
MemClone, g
right‐clicking
Resume‐Clust
Maintenance
t the MemClo
oint in time) w
go back into t
the Cluster D
terResource C
e Mode using
one object th
which is desir
the Windows
Disk and selec
Cmdlet to tur
Windows Po
hen right‐click
red.
Failover Clus
cting More A
rn off mainten
owerShell usin
k and select
ster Manager
ctions→Turn
nance mode:
49
ng
r and
n Off
6. When
and it
7. In the
n maintenanc
t will display t
e Failover Clus
ce mode is tur
the updated d
ster Manager
rned off, the
data for the c
r, on‐line the
remap is com
current MemS
Cluster Role
mplete. The us
Snap.
which was of
ser can acces
ff‐lined prior t
ss the cluster
to the Remap
50
disk
p.