Sei sulla pagina 1di 33

EMC VMAX Storage

EMC VMAX Arrays in Disney Data Centre's


2
3










EMC VMAX Dashboard
EMC VMAX Inventory Details
4
Site Scope Usage Name Vender Model S/N
Current
Code Level
Columbus SAN Storage Production VMAXCOL1-2461 EMC EMC VMAX HK192602461
5874.248.194

Columbus SAN Storage Production VMAXCOL2-3747 EMC EMC VMAX HK192603747
5875.231.172

Columbus SAN Storage DREAMS VMAXCOL3-0816 EMC EMC VMAX
HK192600816

5875.231.172

Columbus SAN Storage Production VMAXCOL4-4927 EMC EMC VMAX HK192604927
5875.231.172

Orlando SAN Storage Production VMAXORL1-1911 EMC EMC VMAX HK192601911 5874.248.194
Orlando SAN Storage Production VMAXORL2-2443 EMC EMC VMAX HK192602443 5874.248.194
Orlando SAN Storage DREAMS VMAXORL3-0613 EMC EMC VMAX HK192600613 5875.198.148
Orlando SAN Storage DREAMS VMAXORL4-0603 EMC EMC VMAX HK192600603 5875.198.148
Orlando SAN Storage Production VMAXORL5-0991 EMC EMC VMAX HK192600991 5875.231.172
Disney Standards for EMC VMAX
The current supported Micro code version is 5874.248.194 & 5875.231.172
No Thin provisioning in VMAX. (Thin devices with 100% subscription)
All hosts require at least 2 HBAs for storage connectivity; HBAs must be added in
pairs, and HBAs cannot be used for both Disk and Tape Drives.
HBA driver differences are not acceptable. Which means all the HBA connected to
host must have one driver.
Path manager incompatibilities are not acceptable in any sense.
A single host cannot have storage directly allocated from multiple vendors
simultaneously
A host cannot have storage directly allocated from different storage technologies.
For example; a host should not have storage allocated to it from both VMAX and XIV.
Best practice is to only allocate storage to a server from one storage unit. If required,
storage can be allocated from up to 2 storage arrays as long as theyre the same
technology.








5
Disney Standards for EMC VMAX
All Disney Storage servers( EMC) must deploy storage management agents ECC
agent V6.1.0.12. This Agent is used for monitoring of host connected to VMAX
storage.
The Team deploying the Servers within the SAN is responsible for requesting and
connecting the SAN related cables to their host; to the SAN switch ports provided to
them as part of the Storage Allocation Request.
The Storage Team is responsible for requesting Floor space, power, fiber SAN
connections, and copper network connection as needed.
All Array names, pool names or configuration related name should be in lowercase.

6
VMAX Logical Naming Conventions
VMAXCOL1-2461


VMAX - EMC VMAX Storage
COL - Columbus
2461 - Serial number of the VMAX box

7
VMAX Storage Pool Naming Convention

8
Virtual (thin) pools are named as follows
drive size_RAID_poolnumber

Where 600_3r5_vp1 =
600Gb drive, RAID 5 3+1, virtual pool 1

VMAX Zoning Standards

The default Host Zoning to a EMC VMAX Storage Array will be a
total of 4 paths from the host, 2 connections to the EMC VMAX
Storage Array FA ports from each of the host 2 HBAs. For fault
tolerance each EMC VMAX FA port will be on separate engines and
SAN Fabrics.
For High Performance hosts we can provide up to a max of 16 paths
to the EMC VMAX Storage Array, 2 connections to the EMC VMAX
Storage Array from each of the host 8 HBAs.
Zoning will follow the EMC rule of 17 for FA usage. Host HBAs will
use the same processor and port on the odd and Even FAs.
9

EMC VMAX LUN Sizes


10
LUN Size Operating System Notes
16.86GB All Legacy size for migrations only
34 GB All None
68 GB All None
100GB Windows, VMware None
1TB VMware None
32GB AIX/SAP only Specific to Corporate SAP
256GB AIX/SAP only Specific to Corporate SAP
2 GB All - clusters Quorum


EMC VMAX Hardware and Configuration


New VMAX arrays will be ordered with a 4 or 8 engines
This requirement is to spread RAID 5 3+1 across 4 engine
4 engine VMAXs can only be upgrade to 8 engines
This requirement is to spread RAID 5 3+1 across 4 engine
Storage cabinets will be ordered in pairs
This requirement is to keep the drives spread evenly
across all engines
Current supported RAID types Set by current best practice per
disk type and policy.

11

EMC VMAX Policies

GOLD defined as
Standard high performance policy
200GB EFD drives RAID 5 3+1 use only 50% of drives
450GB FC drives RAID 1 use 100% drives
2TB SATA drives RAID 6 use 50% of drives
SILVER defined as
default policy
200GB EFD drives RAID 5 3+1 - use only 20% of drives
600GB FC drives RAID 5 3+1 use 100% drives
2TB SATA drives RAID 6 use 100% of drives

12
BRONZE defined as
Copy service / target policy
600GB FC drives RAID 5 3+1 use 100% drives
2TB SATA drives RAID 6 use 100% of drives

13

EMC VMAX Policies

VMAX Supported FAST Devices
tdev (normal production LUN)
Tdev meta (normal production LUN)
R2 tdev meta (DR target device)
Clone tdev (Clone / BCV)
Clone tdev meta (Clone / BCV)

14
VMAX SMC Summary
15
16
VMAX SMC Summary
Naming Conventions
Masking view : servername_arrayname_mv
Initiator group : servername_arrayname_ig
Storage group : servername_arrayname_sg
Port group : servername_arrayname_fa_fa_pg
17
Creating Masking View for new hosts
18
Creating new initiator group
19
Creating new Storage Group
20
Creating new Port group
21
Creating the new Masking View
22
Existing Masking view details in SMC
23
EMC VMAX SPA
24
25
26
VMAX Performance Summary
EMC Ionix Control Center (ECC)Summary
27
ECC Storage Scope
28

EMC VMAX Replication (Copy Services)

Remote Disaster Recovery Replication is handled through SRDF/AR
with a 6 hour RPO. The SRDF devices must be divisible by 16.84
and not Virtual Pool (thin) devices. The source production device will
be GOLD, the BCV/R1 is BRONZE, the remote R2 is GOLD, the
remote BRONZE BCV.
Local Replication, Data base refresh, backup, etc, is handled by
EMC TimeFinder using either BCVs for non-thin devices or clones for
thin devices. The source devices for Local replication will be GOLD,
all target devices clones or BCVs will be SILVER or BRONZE.
This is so the source and target devices are not on the same
physical disk.

29

Copy Services list (VMAX BCV)

30
Source Server Cluster Name O/S DB Designation
Media Server or
Target Server
SAN Type Array
db or
flat files
Purpose
OHOSP006-OHOSP010 DPIPPKG HP-UX dpi ch-flor-bm32 Vmax BCV db backup
OHOSP009-OHOSP010 ODSPPKG HP-UX odsp ch-flor-bm32 Vmax BCV db backup
OHOSP009-OHOSP010 ODSPPKG HP-UX odsua OHOND005 Vmax BCV db refresh
OHOSP009-OHOSP010 ODSPPKG HP-UX odss OHONS001 Vmax BCV db refresh
OHOSP009-OHOSP010 ODSPPKG HP-UX odsua OHONT004 Vmax BCV db refresh
OHOSP018-OHOSP010 CRMPPKG HP-UX crmp ch-flor-bm32 Vmax BCV db backup
OHOSP018-OHOSP010 CRMPPKG HP-UX crmr OHONP004 Vmax BCV db refresh
OHOSP018-OHOSP010 CRMPPKG HP-UX crms OHONS002 Vmax BCV db refresh
OHOSP018-OHOSP010 CRMPPKG HP-UX cmrua OHONT004 Vmax BCV db refresh
OIANP053 n/a AIX drmsp ca-flor-bm18 Vmax BCV db backup
OIANP053 n/a AIX drmsrp ca-flor-bm18 Vmax BCV db backup
OIANP053 n/a AIX krmsp ca-flor-bm18 Vmax BCV db backup
OIANP053 n/a AIX krmsrp ca-flor-bm18 Vmax BCV db backup
OIONP003 n/a AIX wrmsp ca-flor-bm18 Vmax BCV db backup
OIONP003 n/a AIX wrmsrp ca-flor-bm18 Vmax BCV db backup

Copy Services list (VMAX Clone)

31
Source Server Cluster Name O/S DB Designation
Media Server or Target
Server
SAN Type Array
db or flat
files
Purpose
HEDPEDR n/a AIX disco HEDPXDR Vmax Clone db clone
OHOSP016-OHOSP017 TLOGPKG HP-UX rtp ch-flor-bm32 Vmax Clone db backup
OIXVP001-OIXVP002 WDWDBACC AIX wdwaccoviap ca-flor-bm18 Vmax Clone db backup
OIXVP001-OIXVP002 WDWDBACC AIX POC oixvt001 Vmax Clone db refresh
OIXVP001-OIXVP002 WDWDBACC AIX DOC oixnt001 Vmax Clone db refresh
OIXVP001-OIXVP002 WDWDBACC AIX Bashful oixnt003 Vmax Clone db refresh
OIXVP001-OIXVP002 WDWDBACC AIX Snow White oixnt006 Vmax Clone db refresh
OIXVP001-OIXVP002 WDWDBACC AIX Evil Queen oixvt005 Vmax Clone db refresh
OIXVP001-OIXVP002 Via SRDF R2 WDWDBACC AIX Training cixnp001 Vmax Clone db refresh
OIXVP001-OIXVP002 Via SRDF R2 WDWDBACC AIX Grumpy cixnt001 Vmax Clone db refresh
OIXVP001-OIXVP002 Via SRDF R2 WDWDBACC AIX Sleepy cixng001 Vmax Clone db refresh
OIXVP001-OIXVP002 Via SRDF R2 WDWDBACC AIX DR cixnx002 Vmax Clone db refresh
OIXVP003-OIXVP004 DLRDBACC AIX dlraccoviap ca-flor-bm18 Vmax Clone db backup
OIXVP003-OIXVP004 DLRDBACC AIX POC oixvt002 Vmax Clone db refresh
OIXVP003-OIXVP004 DLRDBACC AIX POC oixvt002 Vmax Clone db refresh
OIXVP003-OIXVP004 DLRDBACC AIX DOC oixnt002 Vmax Clone db refresh
OIXVP003-OIXVP004 DLRDBACC AIX Bashful oixnt003 Vmax Clone db refresh
OIXVP003-OIXVP004 DLRDBACC AIX Snow White oixnt007 Vmax Clone db refresh
OIXVP003-OIXVP004 DLRDBACC AIX Evil Queen oixvt006 Vmax Clone db refresh
OIXVP003-OIXVP004 via SRDF R2 DLRDBACC AIX Training cixnp001 Vmax Clone db refresh
OIXVP003-OIXVP004 via SRDF R2 DLRDBACC AIX Grumpy cixnt002 Vmax Clone db refresh
OIXVP003-OIXVP004 via SRDF R2 DLRDBACC AIX Sleepy cixng002 Vmax Clone db refresh
OIXVP003-OIXVP004 via SRDF R2 DLRDBACC AIX DR cixnx003 Vmax Clone db refresh
TLSRV001-TLSRV002 TLSRVRQA AIX rqa ca-flor-bm18 Vmax Clone flat files backup
TLSRV048 n/a AIX rps Vmax Clone flat files backup
TLSRV226-TLSRV227 TLSRVRPR AIX rpr ca-ohco-bm03 Vmax Clone flat files backup
TLSRV815-TLSRV832 TLSRVRPR (DR) AIX rpr ca-flor-bm18 Vmax Clone flat files DR Restore
EMC Data Mgt Security and Access
32
Server Name Location IP Domain Reason For Use USERID Notes
orldwsmeccvm001 Orlando 153.6.23.241 IBMDWS ECC Domain ECC Repository
orldwsmeccvm002 Orlando 153.6.23.242 IBMDWS ECC Domain StorageScope
orldwsmeccvm003 Orlando 153.6.22.34 IBMDWS ECC Domain ECC Store
coldwsmeccvm001 Columbus 139.104.42.241 IBMDWS ECC Domain ECC Repository
coldwsmeccvm002 Columbus 139.104.42.159 IBMDWS ECC Domain StorageScope
coldwsmeccvm003 Columbus TBD IBMDWS ECC Domain Planned ECC Store
orldwsmdbvm001 Orlando 153.6.24.51 WDW BI Domain
orldwsmdbvm002 Orlando 153.6.24.52 WDW BI Domain
orldwsmdbvm003 Orlando 153.6.24.53 WDW BI Domain
orldwsmdbvm004 Orlando 153.6.24.54 WDW BI Domain
coldwsmdevvm001 Columbus 139.104.42.165 WDW BI Domain
coldwsmdevvm002 Columbus 139.104.42.166 WDW BI Domain
coldwsmdevvm003 Columbus 139.104.42.167 WDW BI Domain
coldwsmdevvm004 Columbus 139.104.42.168 WDW BI Domain
orldwsmedgvm001 Orlando 153.6.23.4 IBMDWS EDG Domain EDG Server
orldwsmedgvm002 Orlando 153.6.23.8 IBMDWS EDG Domain EDG Database Server
orldwsmsrsvm001 Orlando 153.6.20.19 IBMDWS ESRS Domain
orldwsmsrsvm002 Orlando 153.6.20.98 IBMDWS ESRS Domain
coldwsmsrsvm001 Columbus 139.104.79.160 IBMDWS ESRS Domain
orldwsecc001 Orlando 153.6.61.84 IBMDWS ECC agents Domain VMAXORL1 VMAXORL2
dis1sem005 Columbus 139.104.221.201 Local ECC agents Local VMAXORL1 VMAXORL2
cissrv162 Orlando 153.6.22.162 WDW SRDF Local
VMAXORL1 VMAXORL2
VMAXORL5 VMAXCOL1
orldwsmap001 Orlando 153.6.174.5 IBMDWS SMAS Domain VMAXORL3 VMAXORL4
orldwsmap002 Orlando 153.6.174.12 IBMDWS ECC agents Domain VMAXORL3 VMAXORL4
EMC Data Mgt Security and Access
orldwsmap003 Orlando 153.6.190.119 IBMDWS SMAS Domain VMAXORL1
VMAXORL2
orldwsmap004 Orlando 153.6.244.44 WDW ECC agents Domain VMAXORL1
VMAXORL2
orldwsmap006 Orlando 153.6.63.241 IBMDWS SMAS Domain VMAXORL5
VMAXORL06
orldwsmap007 Orlando 153.6.63.242 IBMDWS ECC agents Domain VMAXORL5
VMAXORL06
coldwsmap001 Columbus TBD IBMDWS SMAS Domain Planned
VMAXCOL3
coldwsmap002 Columbus 139.104.192.33 IBMDWS ECC agents Domain Planned
VMAXCOL3
coldwsmap003 Columbus 139.104.192.30 IBMDWS SMAS Domain Planned
VMAXCOL1
VMAXCOL2
coldwsmap004 Columbus 139.104.192.64 IBMDWS ECC agents Domain Planned
VMAXCOL1
VMAXCOL2
coldwsmap005 Columbus TBD IBMDWS SMAS Domain Planned
VMAXCOL04
VMAXCOL05
coldwsmap006 Columbus TBD IBMDWS ECC agents Domain Planned
VMAXCOL04
VMAXCOL05
hvlux201 Orlando 10.92.62.96 Local Grab Server Local Legacy Grab
Server
orldwslapvm003 Orlando 153.6.22.77 Local Grab Server Local New Grab Server
33

Potrebbero piacerti anche