07 - NAS Foundations - MR-5WP-NASFD-WRAPPER.pdf

8/10/2019 07 - NAS Foundations - MR-5WP-NASFD-WRAPPER.pdf

1/72

MPACT modules consist of focused, in-depth training content that can be consumed in abou

Welcome to NAS Foundations

2004EMC Corporation. All rights reserved.

EMC Global Education IMPACT

For questions or support please contact Global Educatio

Complete C

update your

complete sta

Course Description

Start Training Run/Download the PowerPoint presentation

Student Resource Guide Training slides with notes

Assessment Must be completed online(Note: Completed Assessments will be reflected online within 24-48 hrs.)

Home
mailto:[email protected]?subject=Impact%20Module%20supporthttps://powerlink.emc.com/common/extRedirect.jhtml?target=GForce&op=gotolibrary&type=material&nodeid=guid_10791186191769269385921323421https://powerlink.emc.com/common/extRedirect.jhtml?target=GForce&op=gotolibrary&type=material&nodeid=guid_10791186191769269385921323421https://secure.testcraft.com/emc/assess.asp?aid=MR-7ZN-NASFDQ104&apass=PASSWORDhttps://secure.testcraft.com/emc/assess.asp?aid=MR-7ZN-NASFDQ104&apass=PASSWORDhttps://powerlink.emc.com/common/extRedirect.jhtml?target=GForce&op=gotolibrary&type=material&nodeid=guid_10791186191769269385921323421https://secure.testcraft.com/emc/assess.asp?aid=MR-7ZN-NASFDQ104&apass=PASSWORDmailto:[email protected]?subject=Impact%20Module%20support


2/72

Link to Knowledgelink to update your transcript and indicate that you have completed the cou

EMC Global Education IMPACT Course Completion

NAS FoundationsCourse Completion Steps:

1. Logon to Knowledgelink (EMC Learning management system).

2. Click on 'My Development'.

3. Locate the entry for this learning event you wish to complete.

4. Click on the complete icon [ ].

Note: The Mark Complete button does not apply to items with the Type: Class, D

or Assessment Test. Any item you cancel from your Enrollments will automatica

Development Plan.

Click here to link to Knowledgelink

For questions or support please contact Global Educatio

Back to Home

2004EMC Corporation. All rights reserved.
http://www.knowledge.isus.emc.com/SabaWeb/mailto:[email protected]?subject=Impact%20Module%20supporthttp://www.knowledge.isus.emc.com/SabaWeb/http://www.knowledge.isus.emc.com/SabaWeb/mailto:[email protected]?subject=Impact%20Module%20support


3/72

If you have any questions, please contact us by email at [email protected] Page 1

EMC Global Education

NAS Foundations IMPACT

Course Description

e-Learning

This foundation level course provides participants

with an understanding of Networked Attached

Storage (NAS) and the EMCs Celerra NAS offering.

Course

Number:MR-5WP-NASFD

Method: IMPACT Duration: 3 hour

AudienceThis course is intended for any person who presently or plans to:

Educate partners and/or customers on the value of Networked Attached Storage (NAS) a

the EMCs Celerra NAS offering

Provide technical consulting skills and support for EMC products

Analyze a Customers business technology requirements

Qualify the value of EMCs products

Collaborate with customers as a storage solutions advisor

PrerequisitesPrior to taking this course, participants should have completed the following courses:

None

Course ObjectivesUpon successful completion of this course, participants should be able to:

Describe Network Attached Storage and its benefit

List NAS configuration considerations

Describe Celerra NAS Products

List Celerra Management Software

Identify Celerra opportunities based on platform, benefits, and support services

Modules CoveredThese modules are designed to support the course objectives. The following modules are

included in this course:

This course includes a single module on Networked Attached Storage.

Labs

Labs reinforce the information you have been taught. The labs for this course include: None

AssessmentsAssessments validate that you have learned the knowledge or skills presented during a

learning experience. This course includes a self-assessments test, to be conducted on-line

via KnowledgeLink, EMCs Learning Management System.


4/72

Copyright 2004 EMC Corporation. All Rights Reserved.

NAS Foundation

11

EMC Global Education 2004 EMC Corporation. All rights reserved.

NAS Foundations

Welcome to NAS Foundations.

Copyright 2004 EMC Corporation. All rights reserved.

These materials may not be copied without EMC's written consent.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change

without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO

REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS

PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR

FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC, Celerra, CLARiiON, and Symmetrix are registered trademarks of EMC Corporation.

All other trademarks used herein are the property of their respective owners.


5/72


NAS Foundation

EMC Global Education 2004 EMC Corporation. All rights reserved. 22

EMC Technology Foundations

EMC Technology Foundations consists of AutoIS, SANproducts, NAS products and Storage Platforms, as wellas advanced storage management software.

EMC Technology supports the portfolio of end-to-endservices designed to help accelerate theimplementation of Information Lifecycle Management(ILM).

ILM uses EMC Technology to enable organizations tobetter and more cost-effectively manage, properlyprotect, achieve compliance and improve the availability

of their business information in a way that ties varyinginformation usefulness to business goals and servicelevels.

This course describes Network Attached Storage and the features that contribute to EMC Technology.


6/72


NAS Foundation


NAS Foundations

After completing this course, you will be able to: Describe Network Attached Storage and explain its value

List NAS Configuration Issues

Describe Celerra NAS Platforms

List Celerra Software Features

List Celerra Management Software

List Windows Specific Options

List NAS Business Continuity Options

These are the learning objectives for this training. Please take a moment to read them.


7/72


8/72


NAS Foundation


What Is Network-Attached Storage?

Built on the concept ofshared storage on a LocalArea Network

Leverages the benefits ofa network file server andnetwork storage

Utilizes industry-standardnetwork and file sharingprotocols

Network

File Server+ Network-attached storage = NAS

Client Application Application Application

Unix Client Unix ClientWindows Client

The benefit of NAS is that it now brings the advantages of networked storage to the desktop through file-level sharing of

data.

NAS is network-centric. Typically used for client storage consolidation on a LAN, NAS is a preferred storage capacity

solution for enabling clients to access files quickly and directly. This eliminates the bottlenecks users often encounter when

accessing files from a general-purpose server.

NAS provides security and performs all file and storage services through standard network protocols, using TCP/IP for datatransfer, Ethernet and Gigabit Ethernet for media access, and CIFS, http, and NFS for remote file service. In addition, NAS

can serve both UNIX and Microsoft Windows users seamlessly, sharing the same data between the different architectures.

For client users, NAS is the technology of choice for providing storage with un-encumbered access to files.

Although NAS trades some performance for manageability and simplicity, it is by no means a lazy technology. Gigabit

Ethernet allows NAS to scale to high performance and low latency, making it possible to support a myriad of clients through

a single interface. Many NAS devices support multiple interfaces and can support multiple networks at the same time.


9/72


NAS Foundation


Why NAS?

Highest availability

Scales for growth

Avoids file replication

Increases flexibility

Reduces complexity Improves security

Costs

Firewall

Web

Servers

NAS

Internet

Data CenterS

n

S2

.

.

.

.

S1

Internal

Network

Shared applications can now achieve the availability, scalability benefits of networked storage. Centralizing file storage

reduces system complexity and system administration costs. Backup, restore, and disaster recovery are simplified.


10/72


NAS Foundation


NAS Operations

All IO operations use File level IOprotocols

No awareness of disk volumes or disksectors

File system is mounted remotely using anetwork file access protocol, such as:

Network File System (NFS)

Common Internet File System(CIFS)

IO is redirected to remote system

Utilizes mature data transport (e.g.,TCP/IP) and media access protocols

NAS device assumes responsibility for

organizing data (R/W) on disk andmanaging cacheDisk

IP Network

Application

NAS Device

NAS

SANORDirect

Attach

One of the key differences of a NAS disk device, compared to DAS or other network storage solutions such as SAN, is that

all I/O operations use file level I/O protocols. File I/O is a high level type of request that, in essence, specifies only the file to

be accessed, but does not directly address the storage device. This is done later by other operating system functions in the

remote NAS appliance.

A file I/O specifies the file. It also indicates an offset into the file. For instance, the I/O may specify Go to byte 1000 in

the file (as if the file were a set of contiguous bytes), and read the next 256 bytes beginning at that position.Unlike block I/O, there is no awareness of a disk volume or disk sector in a file I/O request. Inside the NAS appliance, the

operating system keeps tracks of where files are located on disk. The OS issues a block I/O request to the disks to fulfill the

file I/O read and write requests it receives.

The disk resources can be either directly attached to the NAS device, or they can be attached using a SAN.


11/72


NAS Foundation


NAS Architecture

Application

Remote I/O

request

Operating System

NFS/CIFS

TCP/IP Stack

Network Interface

File I/O to NAS

I/O Redirector

Network Interface

TCP/IP Stack

Network FileProtocol Handler

NASOperatingSystem

To Storage

NFS and CIFS handle file

requests to remote file

system

I/O is encapsulated by

TCP/IP Stack to move

over the network

NAS device converts

requests to block IO and

reads or writes data to

NAS disk storage

Drive Protocol (SCSI)

Storage NetworkProtocol

(Fibre Channel)

The Network File system (NFS) protocol and Common Internet File system (CIFS) protocol handle file I/O requests to the

remote file system, which is located in the NAS device. I/O requests are packaged by the initiator into the TCP/IP protocols

to move across the IP network. The remote NAS file system converts the request to block I/O and reads or writes the data to

the NAS disk storage. To return data to the requesting client application, the NAS appliance software re-packages the data

to move it back across the network.

Here we see an example of an IO being directed to the remote NAS device and the different protocols that play a part inmoving the request back and forth to the remote file system located on the NAS server.


12/72


NAS Foundation


NAS Device

Single-purpose machine orcomponent, serves as a dedicated,high-performance, high-speed

communication of file data Is sometimes called a filer or a

network appliance,

Uses one or more Network InterfaceCards (NICs) to connect to thecustomer network

Uses proprietary optimized operatingsystem; DART, Data Access in RealTime, is EMCs NAS operatingsystem

Use storage protocols to connect tonetworked storage resources Disk

Storage

IP Network

Client Application

NAS Device

Network Drivers and Protocols

NFS CIFS

NAS Device OS (DART)

Storage Drivers and Protocols

A NAS server is not a general-purpose computer significantly reduced/tuned OS in comparison to general purpose

computer. It is sometimes called a filer because it focuses all of its processing power solely on file service and file storage.

The NAS device is sometimes called a network appliance, referring to the plug and play design of many NAS devices.

Common network interface cards (NICs) include gigabit Ethernet (1000 Mb/s) or Fast Ethernet (10Mb/s), ATM, and FIDDI.

Some NAS also supports NDMP, Novell Netware, and HTTP protocols.

The NAS operating system for Network Appliance products is called Data ONTAP. The NAS operating system for EMCCelerra is DART - Data Access in Real Time. These operating systems are tuned to perform file operations including

open, close, read, write, etc.

The NAS device will generally use a standard drive protocol to manage data to and from the disk resources.


13/72


NAS Foundations


NAS Applications

CAD/CAM environments, wherewidely dispersed engineers have to

share and modify design drawings Serving Web pages to thousands of

workstations at the same time

Easily sharing company-wideinformation among employees

Database application

Low transaction rate

Low data volatility

Smaller in size

Not performance constrained

Database applications have traditionally been implemented in a SAN architecture. The primary reason is the deterministic

performance of a SAN. This characteristic is especially applicable for very large, on-line transactional applications with

high transaction rates and high data volatility.

However, NAS might be appropriate where the database transaction rate is low and performance is not constrained.

Extensive application profiling should be done in order to understand the specific database application requirement and, if in

fact, a NAS solution would be appropriate.When considering a NAS solution, the databases should:

be sequentially accessed, non-indexed or have a flat file structure

have a low transaction rate

have a low data volatility

be relatively small

do not have performance / timing constraints


14/72


NAS Foundations

1111


NAS Configuration

An Introduction

This section will introduce NAS configurations.


15/72


NAS Foundations


What is a Network?

Site 1

Site 2

LAN

Physical Media

WAN

LAN

A network is any collection of independent computers that communicate with one another over a shared network medium.

LANs are networks usually confined to a geographic area, such as a single building or a college campus. LANs can be small,

linking as few as three computers, but often linking hundreds of computers used by thousands of people.

Physical Media

An important part of designing and installing a network is selecting the appropriate medium. There are several types in use

today: Ethernet, Fiber Distributed Data Interface (FDDI), Asynchronous Transfer Mode (ATM), and Token Ring.

Ethernet is popular because it strikes a good balance between speed, cost, and ease of installation. These benefits, combined

with wide acceptance in the computer marketplace and the ability to support virtually all popular network protocols, make

Ethernet an ideal networking technology for most computer users today.

WAN

Wide area networking combines multiple LANs that are geographically separate. This is accomplished by connecting the

different LANs using services such as dedicated leased phone lines, dial-up phone lines (both synchronous and

asynchronous), satellite links, and data packet carrier services. Wide area networking can be as simple as a modem and

remote access server for employees to dial into, or it can be as complex as hundreds of branch offices globally linked using

special routing protocols and filters to minimize the expense of sending data sent over vast distances.


16/72


NAS Foundations


Physical Components

NetworkInterface Card

(NIC) Switches

Routers

NIC

NIC

NIC

NIC

Switch

Switch

Router

155.10.10.XX

155.10.20.XX

Network Interface Card

A network topology is the geometric arrangement of nodes and cable links in a LAN, and is used in two general

configurations: bus and star.

Network interface cards, commonly referred to as NICs, are used to connect a Host, Server, Workstation, PC, etc. to a

network. The NIC provides a physical connection between the networking cable and the computer's internal bus. The rate at

which data passes back and forth can be different.

Switches

LAN switches can link multiple network connections together. Todays switches will accept and analyze the entire packet of

data to catch certain packet errors and keep them from propagating through the network before forwarding it to its

destination. Each of the segments attached to an Ethernet switch has the full bandwidth of the switch

10Mb/100Mb/1Gigabit.

Routers

Routers pass traffic between networks. Routers also divide networks logically instead of physically. An IP router can divide

a network into various subnets so that only traffic destined for particular IP addresses can pass between segments.


17/72


NAS Foundations


Network Protocols

TransportProtocols

File systemProtocols

NIC

NIC

NIC

NIC

Switch

Switch

Router

155.10.10.XX

155.10.20.XX

Network protocols are standards that allow computers to communicate. A protocol defines how computers identify one

another on a network, the form that the data should take in transit, and how this information is processed once it reaches its

final destination. Protocols also define procedures for handling lost or damaged transmissions, or "packets."

Network transport protocols are used to manage the movement of data packets to devices communicating across the

network. UDP and TCP are examples of transport protocol. UDP is used in non-connection oriented networks, while TCP is

used to manage the movement of data packets in connection oriented networks.TCP/IP (for UNIX, Windows NT, Windows 95 and other platforms), IPX (for Novell NetWare), DECnet (for networking

Digital Equipment Corp. computers), AppleTalk (for Macintosh computers), and NetBIOS/NetBEUI (for LAN Manager and

Windows NT networks) are examples of network transport protocols in use today.

Network files system protocols are use to manage how data requests will be processed once it reaches its final destination.

The NFS, Network File System protocol, is used to manage file access in a networked UNIX environment and it supports

both UDP and TCP transport protocols.

The CIFS, Common Internet File system protocol, is used to manage file access in a networked Windows environment and it

supports both UDP and TCP transport protocols.


18/72


NAS Foundations


Network Addressing

IP Addressing

DHCP

DNS

155.10.10.13

Host Name Peter

155.10.10.11

Switch

Router

155.10.20.11

DNS Server

155.10.10. 14

Host name Mary

Host Name = Account1

155.10.10.XX

155.10.20.XX

DHCP

Server

155.10.10.12

Several things must happen in order for computers, attached to a network, to be able to communicate data across the

network. First, the computer must have a unique network address, referred to as the IP Address. It is a four octet number, for

example 155.10.20.11, that uniquely identifies this computer to all other computers connected to the network.

An address can be assigned in one of two ways; dynamically or statically. A static address requires entering the IP address

that the computer will use in a local file. This can be quite a problem from an administrative view, as well as a source of

conflict. If two computers on the same subnet are assigned the same IP address, they would not be able to communicate.Another approach is to set up a computer on the network to dynamically assign an IP address to a host when it joins the

network. This is called the Dynamic Host Configuration Protocol (DHCP Server). In our example, the host Mary is assigned

an IP address 155.10.10.14, and the host Peter is assigned an IP address 155.10.10.13 by the DHCP server. The NAS

device, Account1, is a File server. Servers normally will have a statically assigned IP address. In this example, it has the IP

address 155.10.20.11.

A second requirement for communications is to know the address of the recipient of the communication. The more common

approach is to communicate by name, for example, the name you place on a letter. However, the network uses numerical

addresses. IP addresses can be managed in three ways. The first approach is to enter the IP address into the application (IP

address in place of www.x.com in your browser). The second is to maintain a local file with host names and associated IP

addresses. The third is a hierarchical database called Domain Name Service (DNS), which resolves host names to IP

addresses. In our example, if someone on host Mary wants to talk to host Peter, it is the DNS server that resolves Peter to

155.10.20.13.


19/72


NAS Foundations


Volume and Files

Create VolumesVolume

Create NetworkFilesystem

155.10.10.13

Host Name Peter

155.10.10.11

Router

DNS Server

155.10.10. 14

Host name Mary

Account1

Array

/Acct_ RepFile System

NAS

155.10.20.11

DHCP

Server

155.10.10.12

Create Array Volume

The first step in a network attached storage environment is to create logical volumes on the array and assign it a LUN

Identifier. The LUN will then be presented to the NAS device.

Create NAS VolumeThe NAS device will perform a discovery operation when it first starts or when directed. In the discovery operation, the

NAS device will see the array LUN as a physical drive. The next task is to create logical volume at the NAS device level.

The Celerra will create meta volumes using the volume resources presented by the array.

Create Network File

When the logical volumes are created on the Celerra, it can use them to create a file system.

In this example, we have created a file system /Acct_Rep on the NAS server Account1.

Mount File system

Once the file system has been created, it must be mounted. With the file system mounted, we can then move to the next step,

which is publishing the file system on the network.


20/72


NAS Foundations


Publish

Export

Share

155.10.10. 13

Host name Peter

User Peter

Unix

Export

155.10.10.11

Router

DNS Server

155.10.10. 14

Host name Mary

User Mary

MS Windows

Share

Array

ACCOUNT1 /Acct_ Rep

155.10.20.11

Group Name = SALES

Group Name = Accounting

NAS

DHCP

Server

155.10.10.12

Now that a network file system has been created, there are two ways it can be accessed using the network. The first method

is through the UNIX environment. This is accomplished by performing an Export. The Export also publishes those

UNIX clients who can mount (access) the remote file system. The export is published using NFS. Access permissions are

assigned when the export is published.

The second method is through the Windows environment. This is accomplished by publishing a share. The share publishesthose Windows clients who map a drive to access the remote file system. The share is published using CIFS. Access

permission are assigned when the share is published.

In our example, we may only allow Mary and Peter, who are in the Sales organization, share or export access. At this

level, NFS and CIFS are performing the same function but are used in different environments. In our example, all members

of the Group SALES, which include the users Mary and Peter, are granted access to /Acct_Rep.


21/72


NAS Foundations


Client Access

Mount

MAP

155.10.10. 13

Host name Peter

User Peter

Unixnfsmount

155.10.10.11

Router

DNS Server

155.10.10. 14

Host name Mary

User Mary

MS Windows

MAP

Array

ACCOUNT1 /Acct_ Rep

155.10.20.11

Group Name = SALES

Group Name = Accounting

NAS

DHCP

Server

155.10.10.12

To access the network file system, the client must either mount a directory or map a drive pointing to the remote file system.

Mount is a UNIX command performed by a UNIX client to set a local directory pointer to the remote file system. The

mount command uses NFS protocol to mount the export locally.

For a UNIX client to perform this task, it will execute the nfsmount command. The format for the command is:

nfsmount /name of the NAS server:name of the remote file system / name of the local directoryFor example:

nfsmount /Account1:Acct_Rep /localAcct_Rep.

For a Windows client to perform this task, it will execute a map network drive. The sequence is my computer> tools>map

network drive. Select the drive letter and provide the server name and share name in the Folder field.

For example:

G:

\\Account1\Acct_Rep

If you make a comparison, the same information is provided: the local drive (Windows) or the local directory and the name

of the NAS server and the name of the export or the share.


22/72


23/72


NAS Foundations

2020


EMC NAS Platforms

Products

Let examine the current NAS products offered by EMC.


24/72


NAS Foundations


EMC NAS Platforms

High Availability

1 or 2 Data Movers

Integrated NAS

Replication

Celerra /CLARiiON

Golden Eagle /Eagle frame

Celerra /Symmetrix

Golden Eagle /Eagle frame

CelerraNS X00SNSX00

Advanced Clustering

214 Data Movers

SAN and NAS

Replication

Celerra Family DART OS BasedCelerra Family DART OS Based

Advanced Clustering

214 Data Movers

SAN, NAS and MPFS

Replication and advanced

business continuity

High Availability

1 or 2 Data Movers

SAN and NAS

Replication

CelerraNS X00GSNS X00G

Netwin

Data Integrity

1 Intel Based

Windows NAS

Replication

Spanning the Enterprise

Microsoft OSMicrosoft OS

BasedBased

EMC offers four DART Operating System alternatives, the Celerra NS range, Celerra / CLARiiON range, and Celerra /

Symmetrix range.

The processing power, supported storage capacity, number of Ethernet connections, and functionality provided are listed on

the slide to differentiate the offerings. The most full-function, high capacity offering is the Celerra / Symmetrix, offering

capacity up to 52 TB and 224 Ethernet connections. It also provides the most sophisticated business continuance anddisaster recovery solutions through TimeFinder/FS and SRDF.

The Celerra / Symmetrix SE offers both the Symmetrix and Celerra technology in one cabinet. It provides an excellent

solution for customers who have floor space constraints, as a proof of concept solution, or a lower end need that requires

Symmetrix functionality.

Another option the customer has is to front-end a CLARiiON CX600 with the Celerra. This fits well in an environment with

existing CLARiiONs and associated experience. Full function disaster recovery requirements are better suited for a Celerra /

Symmetrix solution.

As we progress through this module, you will see that the functionality provided through DART, running on the Celerra

Data Mover, is the same, regardless of the back-end storage used. The differences will be noted.

Note: These numbers are maximums and may require non-standard configurations.


25/72


NAS Foundations


Celerra NAS - SAN Scalability

Consolidated storageinfrastructure for all applications

NAS front end scalesindependently of SAN back end

Connect to multiple Symmetrix,CLARiiON

Improved utilization

Allocate storage to Celerra andservers as needed

Easy to move filesystems amongData Movers

Online filesystem growth

Centralized management for SAN

and NASWindows

UNIX

CLARiiONCX Family

ConnectrixSAN

Celerra

GoldenEagle/Eagle

SymmetrixDMX Family

CelerraNSX00GNSX00GS

One of the reasons that Celerra Golden Eagle scales impressively is due to the architecture that separates the NAS front end

(Data Movers) from the SAN back end (Symmetrix or CLARiiON).

This allows the front end and back end to grow independently. Customers can merely add Data Movers to the Celerra

Golden Eagle to scale the front-end performance to handle more clients. As the amount of data increases, you can add more

disks, or the Celerra Golden Eagle can access multiple Symmetrix or CLARiiON. This flexibility leads to improved disk

utilization.Celerra Golden Eagle supports simultaneous SAN and NAS access to the CLARiiON and Symmetrix. Celerra Golden Eagle

can be added to an existing SAN, and general purpose servers can now access unused back-end capacity. This extends the

improved utilization, centralized management, and TCO benefits of SAN plus NAS consolidation to Celerra Golden Eagle,

Symmetrix, and CLARiiON.

The configuration can also be reconfigured via software. Since all Data Movers can see the entire file space, it is easy to

reassign filesystems to balance the load. In addition, filesystems can be extended online as they fill.

Even though the architecture splits the front end among multiple Data Movers and a separate SAN back end, the entire NAS

solution can be managed as a single entity.

The Celerra NSx00G (configured with two Data Movers) and the Celerra NSx00GS (configured with a single Data Mover)

connects to a CLARiiON CX array through a fibre channel switch. Celerra NSx00G / NSx00GS supports simultaneous SAN

and NAS access to the CLARiiON CX family.


26/72


NAS Foundations

2323


Celerra Family Hardware

Lets take a closer look at the hardware components of the Celerra family.


27/72


NAS Foundations


Celerra Family Control Station Hardware

Two form factors

Golden Eagle and Eagle

Frame

Control Station

NS XXX Frame

Control Station

Control Station

Control

Station

NS XXX Frame

Golden Eagle

and Eagle

Frame

Control Station provides the controlling subsystem of the Celerra, as well as the management interface to all file server

components. The Control Station provides a secure user interface as a single point of administration and management for the

whole Celerra solution. Control Station administrative functions are accessible via the local console, Telnet, or a Web

Browser.

The Control station is single Intel processor based, with high memory capacity. Dependant upon the model, the Control

Stations may have internal storage. Currently, the NS and Golden Eagle frame series only have this feature.


28/72


NAS Foundations


Celerra Family Data Mover Hardware Single or Dual Intel Processors

PCI or PCI-X based

High memory capacity Multi-port Network cards

Fibre Channel connectivity tostorage arrays

No internal storage devices

Redundancy mechanism

Data Mover

Golden Eagle and Eagle Frame

NS XXX

Frame

Data Mover

Each Data Mover is an independent, autonomous file server that transfers requested files to clients and will remain unaffected, should aproblem arise with another Data Mover. The multiple Data Movers (up to 14) are managed as a single entity. Data Movers are hotpluggable and can be configured with standbys to implement N to1 availability. A Data Mover (DM) connects to a LAN through FE,GigE, FDDI, and ATM. The default name for a Data Mover is server n, where n is its slot location. For example, in the Golden Eagle/Eagle frame, a Data Mover can be in slot location 2 through 15 (i.e. server_2 - server_15 in Celerra Golden Eagle/ Eagle frame). There isno remote login capability on the DM, nor do they run any binaries (very secure).

Data Mover redundancy is the mechanism by which the Celerra family reduces the network data outage in the event of a Data Moverfailure. The ability to failover the Data Movers is achieved by the creation of a Data Mover configuration database on the Control Stationsystem volumes and is managed via the Control Station. No Data Mover failover will occur if the Control Station is not available for somereason.

Standby Data Mover configuration options: 1. Each standby Data Mover, as a standby for a single primary Data Mover 2. Each standbyData Mover, as a standby for a group of primary Data Movers 3. Multiple standby Data Movers for a primary Data Mover. These StandbyData Movers are powered and ready to assume the personality of their associated Primary Data Movers, in the event of a failure. If aPrimary Data Mover fails, the Control Station will detect the failure and initiate the failover process. The failover procedure, in anAutomatic configuration, is as follows.

The Control Station will:

1. Remove power from the failed Data Mover

2. Set the location for the Standby Data Mover to assume its new personality in the configuration database.

3. Control the personality take over and allow the Standby Data Mover to assume the primary role, therebyenabling clients to re-access their data.

Once the failed Data Mover is repaired, the failback mechanism is always manually administrator initiated. This process isthe reverse of the failover process and restores the primary functionality to the repaired Primary Data Mover and returns the Standby DataMover into its standby state in preparation for any future outage. There are three operational modes of operation for Failover: Automatic,Retry, and Manual. Automatic Mode: the Control Station detects the failure of a Data Mover. The failover process occurs without tryingany recovery process first. Retry Mode: the Control Station detects the failure, an attempt to reboot the failed Data Mover is tried first

before the failover procedure is initiated. Manual Mode: the Control Station will detect the failure and remove power from the failed DataMover. However, no further Data Mover recovery action will be taken until administrative intervention. Recovery after a Data Moverfailover is always a manual process.


29/72


NAS Foundations


NAS Reference Documentation

NAS Interoperability Matrix Data Movers

Control Stations Software supported features

www.emc.com/horizontal/interoperability

The NAS interoperability Guide provides support information on the Data Movers and Control Station models, NAS

software version, supported features, storage models, and microcode. This interoperability reference can be found at:

http://www.emc.com/horizontal/interoperability


30/72


NAS Foundations

2727


Celerra Family Software

Software Operating System

Now lets look at operating system software used by the Celerra Family.


31/72


NAS Foundations


Celerra Software Operating Systems

Linux 7.2 This is an industry hardened and EMC modified Operating system loaded on the

Control Station to provide Secure NAS management environment Growing in popularity and corporate acceptance

DART Data Access in Real Time This is a highly specialized Operating system designed to optimize network traffic

Input/Output throughput and is loaded on the Data Movers

Is multi-threaded to optimize load balancing capabilities of the multi-processor DataMovers

Advanced volume management - UxFS Large file size and filesystem support

Online filesystem extensibility

Metadata logging for fast recovery

Striped volume support

Feature rich to support the varied specialized capabilities of the Celerra range

Data Mover Failover Networking functionality Port Aggregation, FailSafe Network device, multi-protocol support

Point in time Filesystem copies

Windows environmental specialties

Linux OS is installed on the Control Station. Control Station OS software is used to install, manage, and configure the Data

Movers, monitor the environmental conditions and performance of all components, and implement the Call Home and dial-in

support feature. Typical Administration functions include the volume and filesystem management, configuration of network

interfaces, creation of filesystems, exporting filesystems to clients, performing filesystem consistency checks, and extending

filesystems.

The OS that the Data Movers run is EMCs Data Access in Real Time (DART) embedded system software, which isoptimized for file I/O, to move data from the EMC storage array to the network. DART supports standard network and file

access protocols: NFS, CIFS, and FTP.


32/72


33/72


NAS Foundations


Network FailSafe Device

Network outages, due to environmental failure, aremore common than Data Mover failures

Network FailSafe Device DART OS mechanism to minimize data access disruption due

to these failures

Logical device is created using either physical ports or otherlogical ports combined together to create redundant groups ofports

Logically grouped Data Mover network ports monitor networktraffic on the ports

Active FailSafe Device port senses traffic disruption

Standby (non-active) port assumes the IP Address and MediaAccess Control address in a very short space of time, thusreducing data access disruption

Having discussed the maintenance of data access via redundant Data Movers, we will now discuss the same concept utilizing

network port mechanisms, first the Network Failsafe device.

Unlike Data Mover failure, network outages due to environmental failures are more common.

To minimize data access disruption due to these failures, the DART OS has a mechanism that is environment agnostic, the

Network FailSafe Device.

This is a mechanism by which the Network ports of a Data Mover may be logically grouped together into a partnership that

will monitor network traffic on the ports. If the currently active port senses a disruption of traffic, the standby (non-active)

port will assume the active role in a very short space of time, thus reducing data access disruption.

The way that this works is a logical device is created, using either physical ports or other logical ports, combined together to

create redundant groups of ports.

In normal operation, the active port will carry all network traffic. The standby (non active port) will remain passive until a

failure is detected. Once a failure has been detected by the FailSafe Device, this port will assume the network identity of the

active port, including IP Address and Media Access Control address.

Having assumed the failed port identity, the standby port will now continue the network traffic. Network disruption due to

this change over is very minimal and may only be noticed in a high transaction oriented NAS implementation or in CIFS

environments due to the connection-oriented nature of the protocol.

There are several benefits achieved by configuring the network FailSafe device: 1. Configuration is handled transparently toclient access; 2. the ports that make up the FailSafe device need not be of the same type; 3. Rapid recovery from a detected

failure; 4. can be combined with logical Aggregated Port devices to provide even higher levels of redundancy.

Although the ports that make up the FailSafe device need not be of the same type, care must be taken to ensure that once

failover has occurred, that client expected response times remain relatively the same and data access paths are maintained.


34/72


35/72


NAS Foundations


Channel

CISCO Switch

Celerra

Link Aggregation - High Availability (cont)

CISCO FastEtherChannel Port grouping for improved

availability Combines 2,4, or 8 Ethernet

ports into a single virtualdevice

Inter-operates with trunking-capable switches

High availabilityif one portfails, other ports take over

Does not increase single clientthroughput

Ethernet Trunking (Ether Channel) increases availability. It provides statistical load sharing by connecting different clients

to different ports. It does not increase single-client throughput. Different clients get allocated to different ports. With only

one client, the client will access Celerra via the same port for every access. This DART OS feature interoperates

FastEtherChannel capable Cisco switches. FastEtherChannel is Cisco proprietary.

IEEE 802.3ad / FastEtherChannel - Comparison


36/72


NAS Foundations


Network Redundancy - High Availability

An example of FSN and Port aggregation co-operation

This example shows a fail-safe network device that consists of a FastEtherChannel comprising the four ports of an Ethernet

NIC and one Gigabit Ethernet port. The FastEtherChannel could be the primary device, but as per recommended practices,

the ports of the FSN would not be marked primary or secondary. FSN provides the ability to configure a standby network

port for a primary port, and the two or more ports can be connected to different switches. The secondary port remains

passive until the primary port link status is broken, then the secondary port takes over operation.

A FSN device is a virtual device that combines 2 virtual ports. A virtual port can consist of a single physical link or anaggregation of links (EtherChannel, LACP). The port types or number need not be the same when creating a failsafe device

group. For example, a quad Ethernet card can be first trunked and then coupled with a single Gigabit Ethernet port. In this

case, all four ports in the trunk would need to fail before FSN would implement failover to the Gigabit port. Thus, Celerra

could tolerate four network failures before losing the connection. Note: an active primary port/active standby port

configuration on the Data Mover is not supported. Unlike Data Mover failure, network outages, due to environmental

failures, are more common. To minimize data access disruption due to these failures, the DART OS has a mechanism that is

environment agnostic; the Network FailSafe Device. This is a mechanism by which the Network ports of a Data Mover may

be logically grouped together into a partnership that will monitor network traffic on the ports. If the currently active port

senses a disruption of traffic, the standby (non-active) port will assume the active role in a very short space of time, thus

reducing data access disruption.

The way that this works is a logical device is created using either physical ports or other logical ports, combined together to

create redundant groups of ports.

In normal operation, the active port will carry all network traffic. The standby (non active port) will remain passive until a

failure is detected. Once a failure has been detected by the FailSafe Device, this port will assume the network identity of the

active port, including IP Address and Media Access Control address.

Having assumed the failed port identity, the standby port will now continue the network traffic. Network disruption due to

this change over is very minimal and may only be noticed in a high transaction oriented NAS implementation or in CIFS

environments due to the connection-oriented nature of the protocol.


37/72


NAS Foundations

3434


Celerra Family ManagementSoftware

In this section, we will examine Celerra management software. This family includes VLAN support, and user interfaces,

(Celerra Native Manager, Celerra WebUI, Celerra Monitor, EMC ControlCenter). It also includes Filesystem controls, as

well as MS Windows environment management software.


38/72


NAS Foundations

3535


Celerra Family SoftwareManagement

Virtual Local Area Networks

We will begin by looking at Virtual Local Area Networks, or VLANS.


39/72


NAS Foundations


VLAN Support

Create logical LANsegment

Divide a single LAN

into logicalsegments

Join multipleseparate segmentsin one logical LAN

VLAN Tagging 802.1q

SimplifiedManagement

No networkreconfiguration

required formemberrelocation

Hub Hub

Hub Hub

Bridge

or

Switch

Bridge

or

Switch

Hub Hub

Router

Workstation VLAN B

VLAN B

VLAN A

VLAN A

Collision Domain

LAN Segment

Collision Domain

LAN Segment

Collision Domain

LAN Segment

Broadcast Domain

LAN

Broadcast Domain LAN

Network domains are categorized into Collision, a LAN segment within which data collisions are contained or Broadcast

and the portions of the network through which broadcast and multicast traffic is propagated. Collision domains are

determined by hardware components and how they are connected together. The components are connected together and are

usually Client computers, Hubs, and repeaters. Separation of a Collision domain from a Broadcast domain is accomplished

by a network switch or a router that generally do not forward broadcast traffic. VLANs allow multiple, distinct, possibly

geographically separate network segments to be connected in to one logical segment. This can be done either by subnettingor by using VLAN tags (802.1q.), which is an address added to network packets to identify the VLANs to which the packet

belongs. This could allow servers that were connected to physically separate networks to communicate more efficiently and

it could prevent servers that were attached to the same physical network from impeding one another.

By using VLANs to logically segment the Broadcast Domains, the equipment contained within this logical environment need

not be physically located together. This now means that if a mobile client moves location, an administrator need not do any

physical network or software configuration for the relocation as bridging technology would now be used, and a router would

only be needed to communicate between VLANS.

There are two commonly practiced ways of implementing this technology - 1. IP Address subnetting or 2. VLAN

Ethernet packet tagging. When using the IP address subnetting methodology, the administrator will configure the broadcast

domains to encompass the whole network area for specific groups of computers by using BridgeRouter technology. When

using the VLAN tagging methodology, the members of a specific group will have an identification tag embedded into all of

their Ethernet packet traffic.

VLAN Tagging allows a single Gigabit Data Mover port to service multiple logical LANs (Virtual LANs). This allows data

network nodes to be configured (added and moved as well as other changes) quickly and conveniently from management

console, rather than in the wiring closet. VLAN also allows a customer to limit traffic to specific elements of a corporate

network and protect against broadcasts (such as denial of service) affecting whole networks. Standard router based security

mechanisms can be used with VLANs to restrict access and improve security.


40/72


NAS Foundations


VLAN - Benefits

Performance

Reduced OverheadReduced Costs

Security

VLAN-A VLAN S VLAN E

The benefits of VLAN support include:

Performance: In all networks, there is a large amount of broadcast and multicast traffic and VLANS can reduce the

amount of traffic being received by all clients.

Virtual Collaborative Work Divisions: by placing widely dispersed collaborative users into a VLAN, broadcast and

multicast traffic between these users will be kept from affecting other network clients and reduce the amount of

routing overhead placed on their traffic.

Simplified Administration: with the large amount of mobile computing today, physical user relocation generates a

lot of administrative user reconfiguration (adding, moving and changing). If the user has not changed company

functionality, but has only re-located, VLANs can perpetuate undisrupted job functionality.

Reduced Cost by using VLANS: expensive routers and billable traffic routing costs can be reduced.

Security, by placing users into a tagged VLAN environment, external access to sensitive broadcast data traffic can

be reduced.

VLAN support enables a single Data Mover with Gigabit Ethernet port(s) to be the standby for multiple primary Data

Movers with Gigabit Ethernet port(s). Each primary Data Mover's Gigabit Ethernet port(s) can be connected to different

switches. Each of these switches can be in a different subnet and different VLAN. The standby Data Mover's Gigabit

Ethernet port is connected to a switch which is connected to all the other switches.


41/72


NAS Foundations

3838


Celerra Family SoftwareManagement

User Interfaces

In this section, we will examine the different user interfaces. These interfaces include the Command line, Celerra Native

Manager, Celerra WebUI, Celerra Monitor, and EMC ControlCenter.


42/72


NAS Foundations


Celerra Management Command Line

The command line can be accessed on the ControlStation via An ssh interface tool i.e. PuTTy

Telnet

Its primary function is for the scripting of commonrepetitive tasks that may run on a predeterminedschedule to ease administrative burden

It has approximately 60 UNIX command-like commands

Telnet access is disabled, by default, on the Control Station due to the possibility of unauthorized access if the Control

Station is placed on a publicly accessible network. If this is the case, it is strongly recommended that this service is not

enabled.


43/72


NAS Foundations


Celerra Web User Interface prior to NAS 5.2

Supports the most commontasks

Network configuration Hardware configuration

Management: Data Movers

Filesystems

Shares

Checkpoints

Status

Utilization

Integrated help for specific

tasks and fields Graphical indicators report

system health

With the exception of the Celerra Native Manager, the other GUI tools are installed and run from the Control Station. The

Native Manager is loaded as an add-on product onto a management workstation/server.

The Celerra Web Manager is launched from a Netscape or Internet Explorer browser. The GUI supports the most common

administrative tasks. Celerra Web Manager uses a dual-frame approach. The left-hand frame contains an expandable tree

view of administration. The right-hand frame contains the system health, links to on-line help, and the data output and form

inputs for the selected administration including:NetworkConfiguration of network settings including DNS, NIS, WINS, link aggregations, and network identity

(IP addresses, subnet masks, VLAN ID).

HardwareTools required to manage and inventory the physical hardware in the system. This includes operations

to configure shelves of disks when the back-end storage array is CLARiiON, managing global spares, and upgrades

(disk, bios, firmware, software).

StatusMonitor the status of the Celerra, including uptime, software versions, release notice link, network

statistics, event logs, and hardware status (any hardware components that are in a degraded state).

UtilizationMonitor the CPU and memory utilization for the Data Movers.

Data MoverManagement of CIFS shares, NFS exports and User Mapping. Other functions include reboot,

shutdown, number of reboots, date/time and NTP configuration, Data Mover name, Data Mover type, and character

encoding. FilesystemsThe tools required to list, create, modify, expand, check, and delete file systems.CheckpointsIncludes screens to list, create, modify, refresh, and delete SnapSure checkpoints. It also provides a

way to restore file system to one of its checkpoints. Admin accessUsed to manage administrative access to the

Control Station. This includes host name, IP address, user name, password, etc.

Notification (phone home)Used to configure the phone home capability of the Control Station. This includes

configuration of destinations for SMTP e-mail, SNMP traps and modem call outs.


44/72


NAS Foundations


Celerra Native Manager - prior to NAS 5.2

Filesystem management

Quotas configuration and

reconfiguration

Wizard capabilities forinitial configuration

Offline editing

Batch program generation

Template import / export

Online operation (live changes andupdates)

Reconfiguration (modifications anddeletes)

Automation and expert systemsupport

Celerra Native Manager is a native Windows 2000 application that exhibits a familiar Windows look and feel. The

application runs from a network client communicating with the Control Station. Native Manager simplifies the tasks of

configuration, reconfiguration, ongoing operation, and observation with features like Targeted Views, simple navigation,

rules-based automation, and configuration check-pointing and comparisons.

Specific features of this management interface include the following:

File system management, Quotas configuration and reconfiguration, Wizard capabilities for initial configuration, Offlineediting; Batch program generation; Online operation (live changes and updates), reconfiguration (mods and deletes)

Automation and expert system support.

It also provides smart features such as rule-based automation and diagnosis, configuration checkpoint, and comparison. In

addition, Native Manager provides status and configuration monitoring, basic statistics, events, and logs.


45/72


NAS Foundations


Celerra Monitor - prior to NAS 5.2

Performance Data Movers

CLARiiON

Symmetrix

View System ID

Status

Alerts

Celerra Monitor is a Java client/server application which runs from the Control Station. It allows you to closely monitor

specific performance data about the Data Movers in the Celerra cabinet and the attached Symmetrix or CLARiiON from a

network client.

Celerra Monitor consists of a Java server (poller) that runs on the Control Station and a Java applet (or in the case of

Windows, an application) that runs in your browser.

Use Celerra Monitor to perform the following tasks for the CLARiiON or Symmetrix and the Data Movers:

View System ID and version information

View overall system status

View hardware components with error conditions

View system alertsevents that may require administrator intervention

Acknowledge (delete) system alerts

Receive online alerts of events posted to the system log

View performance

View configuration

View statistics

View logs

View summaries of past configurations

Control access and polling of monitored data


46/72


NAS Foundations


Celerra Manager v5.2 Management

With the release of DART v5.2, the GUI management has become consolidated into one product with two options 1. Celerra

Native Manager Basic Edition and 2. Celerra Management Advanced Edition

The Basic Edition will be installed, along with the DART OS, and will provide a comprehensive set of common management

functionality for a single Celerra at a time. The Advanced Edition will add multiple Celerra support, along with some

advanced feature GUI management, and will be licensed separately from the DART code.


47/72


NAS Foundations


Celerra Manager v5.2 - Wizards

Celerra Manager V5.2 will offer a number of configuration Wizards for various tasks to assist with new administrator ease

of implementation.


48/72


49/72


NAS Foundations


EMC ControlCenter V5.x.x NAS Support

Discovery and monitoring

Data Movers

Devices and volumes

Network adapters and IPinterfaces

Mount points

Exports

Filesystems (includingsnapshots and checkpoints)

The EMC flagship management product, EMC ControlCenter, has the capability of an assisted discovery of both EMC NAS

and third party NAS products, namely NetApps filers

Currently, management of the EMC NAS family is deferred to the specific product management products due to the highly

specialized nature of the NAS environment. Therefore, this product functionality (shown on this slide) is focused mainly

around discovery, monitoring, and product management software launch capability

ControlCenter V5.x.x has enhanced device management support for the Celerra family. The ControlCenter Celerra Agentruns on Windows and has enhanced discovery and monitoring capabilities. You can now view properties information on

Celerra Data Movers, devices, network adapters and interfaces, mount points, exports, filesystems (including snapshots and

checkpoints), and volumes from the ControlCenter Console. You can also view alerting information for the Celerra family as

well.


50/72


NAS Foundations

4747


Celerra Family FilesystemManagement

Quotas

Lets examine filesystem controls supported by the Celerra Management software.


51/72


NAS Foundations


Filesystem Controls - User Quota Restrictions

One of the most common concerns in a distributed dataenvironment is users tend to save many copies of the

same information

When working in a collaborative distributedenvironment, the amount of data space required byeach use expands rapidly and, in some cases,uncontrollably

To minimize data space outages, the user space canbe controlled by imposing Quotas on users, or groupsof users, to limit either the number of blocks of disk

space they can use or the number of files they cancreate

There are three main types of quota used in data space control:

Soft Quota: This is defined as the amount of data space or number of files used under normal working conditions. It

is a logical limit placed upon a user that can be exceeded without the need for any administrative intervention. Once

the soft quota limit has been exceeded, the user has a grace period to use the extra space defined by the hard quota

limit. However, the user/group cannot exceed the hard limit

Hard Quota: This is defined as the total space or number of files a user/group can use or create on a filesystem

Tree Quota: This is defined as the total space or number of files that a user/group can use or create on a data

directory tree. Tree Quotas are used as a logical mechanism to segment large filesystems into smaller administrative

portions that do not affect each others operation

The grace period is is a time limit during which the user, or group, can continue to increase the amount of disk space used or

number of files created. If the grace period expires, the user/group must reduce the amount of space used or the number of

files to below the soft limit before any new space or files can be created.

The Celerra family will support all of these Quota methodologies, thereby assisting administrators used to these management

tools, with a seamless transition into an EMC NAS environment.


52/72


NAS Foundations

4949


Celerra Family ManagementSoftware

Windows Specific Options

Now we will examine Windows specific options that are supported by the Celerra family.


53/72


NAS Foundations


Usermapper

Maps Windows Security ID to UNIX Permissions

Two Methodologies

Single Mode - one Primary Server only Distributed Mode - One Primary -> Many Secondaries

Maintains Master DB

Provides NewUID/GID to

specific Secondary issuing the

request.

Maintains Cache of entries

used on particular secondary

from the Master DB

Resolves Queries for any

request that is in cache

Requests update if an entry is

requested that is not in Cache

Secondary ServerPrimary Server

As the EMC DART OS is a UNIX based solution, the integration into the Windows environment requires a special set of

tools to ease this process.

One of the most crucial tools is the ability to map Windows Security Identifiers to the UNIX User/Group/Other file/folder

permission structures of the DART OS filesystem.

There is no industry standard methodology to achieve this, and the EMC NAS solution uses two methodologies of

usermapper to achieve this goal. The first is the Single Mode, which only uses a primary server for handling a request toaccess a data resource; or the Distributed Mode, which uses both a single primary and multiple secondary server to handle a

request to access a data resource. The best practices are that the Primary server is configured on the Control Station for

highest availability and ease of management.

Data Consistency and High Availability requires that each Usermapper Server must be designated as either a Primary or a

Secondary (Only one Primary Server can be specified).

In the event that the Primary Server becomes temporarily unavailable, no new user entries will be mapped. Entries already

contained within the Secondary Server cache will be used to resolve queries. When the Primary Server becomes available

again, new mappings will occur automatically. In the event that the Primary Server needs to be replaced, a Secondary

Usermapper Server can be made the Primary by manually reconfiguring the server. This procedure is not recommended as a

common practice and should be done with the help of EMC support. Some of the procedures required for this process

include verifying the Secondary Server was entirely synchronized with the Primary in order to avoid duplicate and/or lost

mapping. This will also involve restarting all servers in the correct sequence. Refer to the most up to date correspondingdocumentation for the exact procedures. Unlike previous versions, Secondary Usermapper Servers must be up and running

before the Primary starts.


54/72


NAS Foundations


Configuration/Installation

Secondary Server

Data Mover

Usermapper

Resolver

Example:

New User Requests Resource(New mapping required)

(1) Resolver queriesFirst server configured

Usermapper DB

(3)New Mapping

Request

(2) Mapping is not in DB

Primary Server

Usermapper DB

(4)Adds a new entry from specifiedUID/GID range

(6)New Entry

(5) Notifies all other Secondary Servers thatthey should initiate a cache update request

(8) Replies to the DataMover's request with the

UID/GID mapping

(7) Updates cache with new mapping

Usermapper DB

DART

v5.2Pre - DART

v5.2

Usermapper - pre & post DART v5.2

This slide steps through the granting of access process.

Step 1 A client request is received at a Data Mover, with the resolver stub running, without a valid UID / GID. The

resolver will then contact the first usermapper server configured in the configuration file with a request for a UI / GID

Step 2 and 3 As the secondary servers are configured before the primary server, a secondary server will be contacted. If

this secondary server does not have a listing for the particular user making the request in its cache, a request will be raised

to the primary server for a UID / GID new mapping.

Step 4 and 5 When the primary server receives a request for a new mapping, an entry from the specified UID / GID range

is added to the database and a notification is issued to all secondary servers that their cache entries will need to be updated.

Step 6 and 7 The secondary server making the request for the new mapping will update its cache with new information

from the primary server upon the receipt of the notification to update cache from the primary.

Step 8 The secondary server that received the initial request will now respond back to the requesting Data Mover with the

new mapping information and the user will be granted access (or denied access) to the requested resource.

NOTE: DART v 5.2 introduces a fundamental upgrade to the usermapper process. This upgrade is that each Data Mover

now maintains its own usermapper data base of user mappings. This now assists with Data Mover failover connectivity

continuance and access is unaffected by possible Control Station failure.


55/72


NAS Foundations


Virtual Data Movers DART v5.2

Virtual Data Movers on Single Physical Data Movers DART v5.2 Another improvement to the Windows integration is the ability

to create multiple virtual CIFS servers on each Data Mover

This is achieved by creating Virtual Data Mover environments

This is a huge benefit to the consolidation of multiple server fileserving functionality onto single Data Movers as each virtualData Mover can maintain isolated CIFS servers with their ownroot filesystem environment

This will allow whole Virtual Data Mover environments to beloaded, unloaded, or even replicated between physical DataMovers for ease in Windows environmental management

Currently, in pre DART v5.2, a Data Mover supports one NFS server and multiple CIFS servers, where each server has the

same view of all the resources. The CIFS servers are not logically isolated and although they are very useful in consolidating

multiple servers into one data mover, they do not provide the isolation between servers as needed in some environments such

as data from disjoint departments hosted on the same data mover.

In v5.2, VDMs support separate isolated CIFS servers, allowing you to place one or multiple CIFS servers into a VDM,

along with their file systems. The servers residing in a VDM store their dynamic configuration information (such as localgroups, shares, security credentials, and audit logs, etc.) in a configuration file system. A VDM can then be loaded and

unloaded, moved from Data Mover to Data Mover, or even replicated to a remote Data Mover as an autonomous unit. The

servers, their file systems, and all of the configuration data that allows clients to access the file systems are available in one

virtual container.

VDMs provide virtual partitioning of the physical resources and independently contain all the information necessary to

support the contained CIFS servers. Having the file systems and the configuration information contained in a VDM does the

following: 1. enables administrators to separate CIFS servers and give them access to specified shares; 2. allows replication

of the CIFS environment from primary to secondary without impacting server access, and 3. enables administrators to easily

move CIFS servers from one physical Data Mover to another.

A VDM can contain one or more CIFS servers. The only requirement is that you have at least one interface available for

each CIFS server you create. The CIFS servers in each VDM have access only to the file systems mounted to that VDM, and

therefore can only create shares on those file systems mounted to the VDM. This allows a user to administratively partitionor group their file systems and CIFS servers.


56/72


NAS Foundations


Additional Tools - MMC Snap-ins

UNIX User Management

Active Directory migration tool

MMC plug-in extension for Active

Directory uses and computers

Celerra Management tool snap-in

(MMC Console)

Virus Checker Management

Celerra Management tool:

(MMC Console)

Home Directory snap-in

Allows multiple points of entry toa single share

Data Mover security snap-in

Manage user rights and auditing

Celerra offers a number of Windows 2000 management tools with the Windows 2000 look and feel. For example, Celerra

shares and quotas can be managed by the standard Microsoft Management Console (MMC).

The tools include:

The Celerra Management Tool (MMC Console)Snap-in extension for Dart Virus Checker Management which

manages parameters for the DART Virus Checker.

The Active Directory (AD) Migration tool Migrates the Windows/UNIX user and group mappings to Active

Directory. The matching users/groups are displayed in a property page with a separate sheet for users and groups.

The administrator selects the users/groups that should be migrated and de-selects those that should not be migrated

or should be removed from Active Directory.

The Microsoft Management Console (MMC) Snap-in extension for AD users and computers. This adds a

property page to the users property sheet to specify UID (user ID) /GID (group ID)/Comment and adds a property

page to the group property sheet to specify GID/Comment. You can only manage users and a group of the local

tree.

The Celerra Management Tool (MMC Console) Snap-in extension for Dart UNIX User Management displays

Windows users/groups which are mapped to UNIX attributes. It also displays all domains that are known to local

domain (Local Tree, Trusted domains).

The Home Directories capability in the Celerra allows a customer to set up multiple points of entry to a singleShare/Export so as to avoid sharing out many hundreds of points of entry to a filesystem for each individual user for

storing their Home Directories. The MMC Snap-in provides a simple and familiar management interface for

Windows administrators for this capability.

The Data Mover Security Settings Snap-in provides a standard Windows interface for managing user rights

assignments, as well as the settings for which statistics Celerra should audit, based on the NT V4 style auditing

policies.


57/72


NAS Foundations

5454


Celerra Family BusinessContinuity

Disk Based Replication and Recovery Solutions

Now we can examine some of the replication and recovery solutions available in the Celerra family.


58/72


NAS Foundations


Disk-Based Replication and Recovery Solutions

Celerra / Symmetrix

Celerra / FC4700

SynchronousSynchronousDisasterDisaster

RecoveryRecoverySRDFSRDF

Seconds

FileFileRestorationRestoration

Celerra SnapSureCelerra SnapSure

Hours

FileFile--basedbasedReplicationReplicationTimeFinder/FSTimeFinder/FS

Celerra ReplicatorCelerra ReplicatorEMC OnCourseEMC OnCourse

Minutes

Celerra /CLARiiON

CelerraNS600

FUNCTIONALITY

RECOVERY TIME

High-end environments require non-stop access to the information pool. From a practical perspective, not all data carries the

same value. The following illustrates that EMC Celerra provides a range of disk-based replication tools for each recovery

time requirement.

File restoration: This is the information archived to disk and typically saved to tape. Here we measure recovery in hours.

Celerra SnapSure enables local point-in-time replication for file undeletes and backups.

File-based replication: This information is recoverable in time frames measured in minutes. Information is mirrored to diskby TimeFinder, and the copy is made accessible with TimeFinder/FS. The Celerra Replicator creates replicas of production

filesystems either locally or at a remote site. Recovery time from the secondary site depends on the bandwidth of the IP

connection between the two sites. EMC OnCourse provides secure, policy-based file transfers.

The Replicator feature supports data recovery for both CIFS and NFS by allowing the secondary filesystem (SFS) to be

manually switched to read/write mode after the Replicator session has been stopped, either manually or due to a destructive

event. Note: There is no re-synch or failback capability.

Synchronous disaster recovery: This is the information requiring disaster recovery with no loss of transactions. This strategy

allows customers to have data recovery in seconds. SRDF, in synchronous mode, facilitates real-time remote mirroring in

campus environments (up to 60 km).

File restoration and file-based replication (Celerra Replicator, EMC OnCourse) are available with Celerra /CLARiiON. The

entire suite of file restoration, file-based replication, and synchronous disaster recovery are available with Celerra

/Symmetrix.


59/72


NAS Foundations

5656


Disaster Recovery

Celerra Symmetrix Remote Data Facility

In this section, we will look at the Celerra disaster recovery solution.


60/72


NAS Foundations


Celerra SRDF Disaster Recovery

Celerra synchronous disaster recovery solution Allows an administrator to configure remote standby Data Movers waiting to

assume primary roles in the event of a disaster occurring at the primary datasite

SRDF allows administrator to achieve a remote synchronous copy ofproduction filesystems at a remote location

Real-time, logically synchronized and consistent copies of selected volumes

Uni-directional and bi-directional support

Resilient against drive, link, and server failures

No lost I/Os in the event of a disaster

Independent of CPU, operating system, application, or database

Simplifies disaster recovery switchover and back

CelerraCelerraUni or bi-directional

Campus (60 km) distance

Network

Increases data availability by combining the high availability of theCelerra family with the Symmetrix Remote Data Facility

In the NAS environment, data availability is one of the key aspects for implementation determination. By combining the

high availability of the Celerra family with the Symmetrix Remote Data Facility, data available increases exponentially.

What the SRDF feature allows an administrator to achieve is a remote synchronous copy of production filesystems at a

remote location. However, as this entails the creation of Symmetrix specific R1 and R2 data volumes, this functionality is

currently restricted to Celerra / Symmetrix implementations only.

This feature allows an administrator to configure remote standby Data Movers waiting to assume primary roles in the eventof a disaster occurring at the primary data site. Due to data latency issues, this solution is restricted to a campus distance of

separation between the two data sites (60 network km).

The SRDF solution for Celerra can leverage an existing SRDF transport infrastructure to support the full range of supported

SAN (storage area network) and DAS (direct-attached storage) connected general purpose server platforms. The Celerra

disaster recovery solution maintains continuously available filesystems, even with an unavailable or non-functioning Celerra.

Symmetrix technology connects a local and remote Celerra over a distance of up to 40 miles (66 km) via an ESCON or Fiber

Channel SRDF connection. After establishing the connection and properly configuring the Celerra, users gain continued

access to filesystems in the event that the local Celerra and/or the Symmetrix becomes unavailable. The Celerra systems

communicate over the network to ensure the primary and secondary Data Movers are synchronized with respect to meta

data, while the physical data i

07 - NAS Foundations - MR-5WP-NASFD-WRAPPER.pdf

Documents