Storage Area Network (SAN session Day-2)

1. SAN Introduction – Day2

2. Agenda
 Thin and Thick Provisioning
 Deduplication
 High Availability
 Virtualization
 LUN assignment
 Networking
 Zoning
2

3. Thin Provisioning
Definition-:A thin-provisioned volume is
a volume for which storage is not set
aside up-front. Instead, the storage for
the volume is allocated as it is needed.

4. Thick Provisioning
Definition-: In virtual storage,
thick provisioning is a type of
storage allocation in which the
amount of storage capacity on a
volume is pre-allocated on
physical storage (aggregate) at
the time the volume is created.

5. NetApp Deduplication
Deduplication refers to the elimination
of redundant data in the storage. In
the deduplication process, duplicate
data is deleted, leaving only one copy
of the data to be stored. However,
indexing of all data is still retained
should that data ever be required. De-
duplication is able to reduce the
required storage capacity since only
the unique data is stored.

7. Introduction
of
Storage Area Network

10. High Availability
High availability means the
amount of time the network
services and data are accessible.
In many enterprises ensuring
data availability at any time and
at any place is the highest
priority.

13. Benefits of HA
Data access at anytime
Nondisruptive OS upgrade and hardware upgrade
The nondisruptive upgrade method can be used to replace or upgrade the following components
1.The storage system
2.Motherboard
3.Adapters
4.Nonvolaile RAM(NVRAM)
5.Disks
6.Other network interface components

14. Multi-Tenancy; What is it?
Shared infrastructure: hardware and
software
Administrative isolation and control
Supporting multiple “tenants” (users,
customers, etc.) from single shared
infrastructure while keeping all data isolated
and secure
Customers concerned with security and
privacy require secure multi-tenancy
– Government agencies
– Financial companies
– Service Providers
– Etc.
14

15. Secure Multi-tenancy for virtualized environments
Solution
The only validated solution to support end
to end multitenancy across application and
data
Data is securely isolated from virtual server,
network, to virtual storage

16. Introducing MultiStore
Creates multiple system partitions (vFiler units)
on a single NetApp storage system.
Each vFiler unit is secure (Data owned by one
vFiler unit can’t be accessed by any other vFiler
unit though they are hosted on a same physical
storage system)
16

17. Multistore and Vfiler
A logical partition of N/W and storage resource in Data ONTAP called multistore and it provides a
secure storage consolidation solution.
When enabled, the Multistore license creates a logical unit called vFiler0 which contains all of the
storage and network resources of the physical FAS unit. Additional vFilers can then be created
with storage and network resources assigned specifically to them.
What is Vfiler ?
A lightweight Instance of Data ONTAP Multi protocol server and all the system resource are shared
b/w Vfiler units.
-Storage units in the vfilers are Flexvols and Qtrees
-Network Units are IP Address, VLAN, VIFs, aliases and IPspaces
-Vfiler units are not hypervisors –vfiler resource cannot be accessed and discovered by any other
vfiler units

18. Multi store configuration:
Up to 65 secure partitions (vFiler units) on a single
storage system (64+vfiler0)
IP Storage based (NFS,CIFS & iSCSI servers)
Additional storage and n/w resource can be moved,
added or deleted
NFS, CIFS, iSCSI, HTTP, NDMP, FTP, SSH and SFTP
protocols are supported
-Protocols can be enabled / disabled per vFiler
-Destroying a vFiler does not destroy data

19. What Makes MultiStore Secure?
– IPspaces
– Administrative separation
– Protocol separation
– Storage separation
An IPspace has a dedicated routing table
Each physical interface (Ethernet port) or logical interface (VLAN) is bound to a single Ipspace
A single IPspace may have multiple physical & logical interfaces bound to it
Each customer has a unique IPspace
Use of VLANs or VIFs is a best practice with IPspaces

21. File Services Consolidation

22. Application Hosting

23. Always-On Data Mobility
No planned downtime for-:
Storage capacity expansion
Scheduled maintenance outages
Software Upgrades

24. FC Switch

25. Fabric Address
MAC address in networking is 48 bit like in SAN fabric address is 24 bit address.
01:EF:03:12:08:ef (12*4=48 bit MAC for NIC)
Fabric Address(24bit)-:
Domain ID : Area ID : ALPA
8 bit 8 bit 8 bit
We have decimal numbers -0 -9
Hexadecimal-0-9,A,B,C,D,E,F,10 to 1F,20 to 2F,F0-FF

26. Fabric Address
26
01-EF address are used for addressing and F0 and FF are reserved.
EF= E * 161 + F * 160
=14 * 16 + 15 * 1
=239
So we can connect 239 switches in a single fabric but domain ID will be different for each switch
Area- 8 bit address given to each port so 28 = 256 (Max) ports
First port address is 0 and last is EF
Example-16 ports, 32 ports ..etc.
ALPA- Arbitrated loop physical address 8 bit address.
Single port with multiple servers can be connected.

27. Fiber channel switch port interface
Switch Ports
E_Port :- Expansion port, two switches to make a
fabric
F_Port :- A fabric port to which an N-port attaches
FL_port :- A fabric loop port which a loop attaches
Device Ports
N_Port :- Port designator for direct fabric attached
devices.
NL_Port :- Device that is attached to the loop (host
and storage)

28. Fabric Address for Initiator & Target

29. NETWORKING
Why FC is used in FC SAN?
Advantage-:
-FC carries multiple protocols and it also carries FC
-Existing protocol can carry through FC
-Carrying SCSI data through FCP called SCSI—FCP
-Carrying IP data over FC called FCIP
-Large connectivity (16 millions devices)
-High performance and speed (16gb/sec)
-Low latency (Latency in SAN Microseconds)
Disadvantage-:Costly

30. FC LAYERS
 FC0-Physical layer –understanding of physical components
 FC1- 8b/10bEncoding and Decoding –Internal
 FC2-Data delivery –Fragmentation
 FC3-Common services –Advance components
 FC4-ULP mapping (Upper level protocol mapping)

31. 31

32. ZONING
Zoning= Opening a path between the N-ports
How can we open the path?
Zone can be implemented by-:
1.WWN zoning (Soft Zoning)
2.Port zoning (Hard Zoning)