Showing posts with label netapp basic introduction. Show all posts
Showing posts with label netapp basic introduction. Show all posts

Thursday, 6 October 2011

NetApp architecture


The NetApp architecture consist of hardware, Data ONTAP operating system and the network. I have already shown you a diagram of a common NetApp setup but now i will go into more detail.

Hardware
NetApp have a number of filers that would fit into any company and cost, the filer itself may have the following
  • can be a Intel or AMD server (up to 8 dual core processors) 
  • can have dual power supplies 
  • can handle up to 64GB RAM and 4GB NVRAM (non-volatile RAM) 
  • can manage up to 1176GB storage 
  • has a maximum limit of 1176 disk drives 
  • can connect the disk shelves via a FC loop for redundancy 
  • can support FCP, SATA and SAS disk drives 
  • has a maximum 5 PCI and 3 PCI-express slots 
  • has 4/8/10GbE support 
  • 64bit support
The filer can be attached to a number of disk enclosures (shelves) which expands the storage allocation, these disk enclosures are attached via FC, as mentioned above the disk enclosures can support the following disks

FCP       These are fibre channel disks, they are very fast but expensive
SAS       Serial attached SCSI disks again are very fast but expensive , due to replace the FC disks
SATA    Serial ATA are slow disks but are cheaper, ideal for QA and DEV environments


One note to remember is that the filer that connects to the top module of a shelf controls (owns) the disks in that shelf under normal circumstances (i.e. non-failover).

The filers can make use of VIF's (Virtual Interfaces), they come in two flavors

Single-mode VIF

  • 1 active link, others are passive, standby links 
  • Failover when link is down
  • No configuration on switches


Multi-mode VIF

  • Multiple links are active at the same time 
  • Loadbalancing and failover 
  • Loadbalancing based on IP address, MAC address or round robin
  • Requires support & configuration on switches

Software

I have already touched on the operating system Data ONTAP, the latest version is currently version 8 which fully supports grid technology (GX in version 7). It is fully compatible with Intel and AMD architectures and supports 64bit, it borrows the idea's from FreeBSD.

All additional NetApp products are activated via licenses, some require the filer to be rebooted so check the documentation.

Management of the filer can be accessed via any of the following
  • Telnet or SSH
  • Filerview (HTTP GUI)
  • System Manager (client software GUI)
  • Console cable
  • snmp and ndmp
Storage Terminology

When talking about storage you probably come across two solutions

NAS (Network Attached Storage)
   NAS storage speaks to a file, so the protocol if a file based one. Data is made to be shared examples are
  • NFS (Unix)
  • CIFS or SMB (Windows)
  • FTP, HTTP, WebDAV, DAFS
SAN (Storage Area Network)

SAN storage speaks to a LUN (Logical Unit Number) and accesses it via data blocks, sharing is difficult examples are
  • SCSI
  • iSCSI
  • FCAL/FCP


There are a number of terminologies associated with the above solutions, I have already discussed some of them in my EMC section

    Terminology
Solution
Description
    share/export
NAS
CIFS servers makes data available via shares, a Unix server makes data available via exports
    Drive                     g  mapping/mounting
NAS
CIFS clients typically map a network drive to access data stored on a storage server, Unix clients typically mount the remote resource
    LUN
SAN
Logical Unit Number , basically a disk presented by a SAN to a host, when attached it looks like a locally attached disk.
    Target
SAN
The machine that offers a disk (LUN) to another machine in other words the SAN
    Initiator
SAN
The machine that expects to see the disk (LUN) the host OS, appropriate initiator software will be required
    Fabric
SAN
One or more fibre switches with targets and initiators connected to them are referred to as a fabric. Cisco, McData and Brocade are well know fabric switch makers
See my EMC architecture section for more details
    HBA
SAN
Host Bus Adapter, the hardware that connects the server or SAN to the fabric switches. There are also iSCSI HBA's
    Multipathing (MPIO)
SAN
The use of redundant storage network components responsible for transfer of data between the server and the storage (Cabling, adapters, switches and software)
    Zoning
SAN
The partioning of a fabric into smaller subsets to restrict interference, added security and simplify management, it's like VLAN's in networking
See my EMC zoning section for more details
          

                                            





NetApp Terminology

Now that we know how a NetApp is configured from a hardware point of view, we now need to know how to present the storage to the outside world, first some NetApp terminologies explained


Aggregate:
A collection of disks that can have either of the below RAID levels, the aggregate can contain up to 1176 disks, you can have many aggregates with the below different RAID levels. An aggregate can contain many volumes (see volumes below).
  • RAID-4
  • RAID-DP (RAID-6) better fault tolerance
One point to remember is that a aggregate can grow but cannot shrink, the disadvantage with RAID 4 is that a bottleneck can happen on the dedicated parity disk, which is normally the first disk to fail due to it being used the most, however the NVRAM helps out by only writing to disks every 10 seconds or when the NVRAM is 50% full.
Raid Group (Pool)
Normally there are three pools 0, 1 and spare
  • 0 = normal pool
  • 1 = mirror pool (if syncMirror is enabled)
spare = spares disks that be used for growth and replacement of failed disks

Plex

When a aggregate is mirrored it will have two plexes, when thinking of plexes think of mirroring. A mirrored aggregated can be split into two plexes.

Volume (Flexible)

This is more or like a traditional volume in other LVM's, it is a logical space within an aggregate that will contain the actual data, it can be grown or shrunk as needed

WAFL

Write anywhere filesystem layout is the filesystem used, it uses inodes just like Unix. Disks are not formatted they are zeroed.
By default WAFL reserves 10% of a disk space (unreclaimable)

LUN

The Logical Unit Number is what is present to the host to allow access to the volume.

SNAPSHOT
A frozen read-only image of a volume or aggregate that reflects the state of the new file system at the time the snapshot was created, snapshot features are
  • Up to 255 snapshots per volume
  • can be scheduled
  • Maximum space occupied can be specified (default 20%)
File permissions are handled




Please write your valuable comments, About This Blogspot.

Wednesday, 5 October 2011

NetApp


Network Appliance (NetApp)

This section is short introduction into Network Appliance (NetApp).

History

NetApp was created in 1992 by David Hitz, James Lau and Michael Malcolm, the company become public in 1995 and grew rapidly in the dot com boom, the companies headquarters are in Sunnyvale, California, US. NetApp has acquired a number of companies that helped in development of various products. The first NetApp network appliance shipped in 1993 known as a filer, this product was a new beginning in data storage architecture, the device did one task and it did it extremely well. NetApp made sure that the device was fully compatible to use industry standard hardware rather than specialized hardware. Today's NetApp products cater for small, medium and large size corporations and can be found in many blue-chip companies.


NetApp Filers can offer the following

•           Supports SAN, NAS, FC, SATA, iSCSI, FCoE and Ethernet all on the same platform
•           Supports either SATA, FC and SAS disk drives
•           Supports block protocols such as ISCSI, Fibre Channel and AoE
•           Supports file protocols such as NFS, CIFS , FTP, TFTP and HTTP
•           High availability
•           Easy Management
•           Scalable

NetApp Filer

The NetApp Filer also know as NetApp Fabric-Attached Storage (FAS), is a data storage device, it can act as a SAN or as a NAS, it serves storage over a network using either file-based or block-based protocols

File-Based Protocol     :  NFS, CIFS, FTP, TFTP, HTTP

Block-Based Protocol :  Fibre Channel (FC), Fibre channel over Ethernet (FCoE), Internet SCSI (iSCSI)

The most common NetAPP configuration consists of a filer (also known as a controller or head node) and disk enclosures (also known as shelves), the disk enclosures are connected by FC or parallel/serial ATA, the filer is then accessed by other Linux, Unix or Window servers via a network (Ethernet or FC). An example setup would be like the one in the diagram below

Filer Back view

The filers run NetApp's own adapted operating system (based on FreeBSD) called Data ONTAP, it is highly tuned for storage-serving purposes.

All filers have a battery-backed NVRAM, which allows them to commit writes to stable storage quickly, without waiting on the disks.

It is also possible to cluster filers to create a highly-availability cluster with a private high-speed link using either FC or InfiniBand, clusters can then be grouped together under a single namespace when running in the cluster mode of the Data ONTAP 8 operating system.

The filer will be either Intel or AMD processor based computer using PCI, each filer will have a battery-backed NVRAM adaptor to log all writes for performance and to replay in the event of a server crash. The Data ONTAP operating system implements a single proprietary file-system called WAFL (Write Anywhere File Layout).

WAFL is not a filesystem in the traditional sense, but a file layout that supports very large high-performance RAID arrays (up to 100TB), it provides mechanisms that enable a variety of filesystems and technologies that want to access disk blocks. WAFL also offers

  • snapshots (up to 255 per volume can be made)
  • snapmirror (disk replication)
  • syncmirror (mirror RAID arrays for extra resilience, can be mirrored up to 100km away)
  • snaplock (Write once read many, data cannot be deleted until its retention period has been reached)
  • read-only copies of the file system
  • read-write snapshots called FlexClone
  • ACL's
NetApp Backups

The last point to touch on is backups, NetApp offers two types

Dump
  • backs up files and directories 
  • supports level-0, incremental and differential backups 
  • supports single file restore 
  • capable of backing only the base snapshot copy 

SMTape 

  • Backs up blocks of data to tape 
  • Supports only level-0 backup 
  • does not support single file restore 
  • capable of backing up multiple snapshot copies in a volume 
  • does not support remote tape backups and restores 

The filer will support either SCSI or Fibre channel (FC) tape drives and can have a maximum of 64 mixed tape devices attached to a single storage system.

Network Data Management Protocol (NDMP) is a standardized protocol for controlling backup, recovery and other transfers of data between primary and secondary storage devices such as storage systems and tape libraries. This removes the need for transporting the data through the backup server itself, thus enhancing speed and removing load from the backup server. By enabling NDMP support you enable that storage system to carry communications with the NDMP-enabled commercial network-attached backup application, it also provides low-level control of tape devices and medium changers. The advantages of NDMP are 
  • provide sophisticated scheduling of data protection across multiple storage systems
  • provide media management and tape inventory management services to eliminate tape handling during data protection operations
  • support data cataloging services that simplify the process of locating specific recovery data
  • supports multiple topology configurations, allowing sharing of secondary storage (tape library) resources through the use of three-way network data connections
  • supports security features to prevent or monitoring unauthorized use of NDMP connections

Friday, 30 September 2011

Operating System (OS)

Operating System:

  • Operating system which controls the hardware and kernel.
  • DATA ONTAP is the operating system for NETAPP.
  • In ontap we have several version like 6.x, 7.x & 8.x
  • Version depends on the Fas model (filer)
  • WAFL is the file system for Ontap OS
  • Operating system is made up of modules. module means it restart the own services with out restart the machine.

Data ONTAP Features

  1. Deduplication and Compression
  2. FilerView® 
  3. Flash Pool 
  4. FlexShare®
  5. FlexVol® 
  6. RAID-DP®
  7. Snapshot™ 
  8. SnapValidator®