Recent Posts

Tuesday, 10 May 2016

Netapp Cluster Tutorial

     NetApp is very popular for NAS (Network Attached Storage) from the past decade. In 2002 , NetApp would like to change the NAS tag to SAN. So they have renamed their product lines to FAS (Fabric Attached SCSI) to support both NAS and SAN.  In the FAS storage product lines, NetApp provides the unique storage solution which supports multiple protocols in single system. NetApp storages uses DATA ONTAP operating system which is based on Net/2 BSD Unix.

1. DATA ONTAB 7G  (NetApp’s Legacy Operating System)
2. DATA ONTAP GX. (NetApp’s Grid Based Operating System)
DATA ONTAP GX is based upon GRID technology (Distributed Storage Model) acquired from Spinnaker Networks.

NetApp 7 Mode vs Cluster Mode:

              In the past, NetApp provided 7-Mode storage. 7-Mode storage provides dual-controller, cost-effective storage systems. In 2010, NetApp Released the new Operating System  called DATA ONTAP 8 which includes the 7 Mode and C Mode. We just need to choose the mode in the storage controller start-up (Similar to Dual Boot OS system).  In NetApp  Cluster Mode , you can easily scale out the environment on  demand basis.

From DATA ONTAP 8.3 operating system version onwards, you do not have option to choose 7 Mode. It’s just available only as Clustered DATA  ONTAP .

Clustered DATA ONTAP Highlights: 

         Here is the some of the key highlights of DATA ONTAP clustered mode. Some of the features are  remain same as 7-Mode.

1. Supported Protocols:
  • FC
  • NFS
  • FCoE
  • iSCSI
  • pNFS
  • CIFS
2. Easy to Scale out
3. Storage Efficiency
  • It supports De-duplication
  • Compression
  • Thin Provisioning.
  • Cloning
4. Cost and Performance
  • Supports Flash Cache
  • Option to use SSD Drives
  • Flash Pool
  • FlexCache
  • SAS and SATA drive Options
5. Integrated Data protection
  • Snapshot Copies
  • Asynchronous Mirroring
  • Disk to Disk or Disk to tape backup option.
6. Management
  • Unified Management. (Manage SAN and NAS using same portal)
  • Secure Multi-tenancy
  • Multi-vendor Virtualization.
Clustered DATA ONTAP – Scalability:
        Clustered Data ONTAP solutions can scale from 1 to 24 nodes, and are mostly managed as one large system. More importantly, to client systems, a cluster looks like a single system. The performance of the cluster scales linearly to multiple gigabytes per second of throughput, and capacity scales to petabytes. Clusters are built for continuous operation; no single failure on a port, disk, card, or motherboard will cause data to become inaccessible in a system. Clustered scaling and load balancing are both transparent.

        Clusters provide a robust feature set, including data protection features such as Snapshot copies, intracluster asynchronous mirroring, SnapVault backups, and NDMP backups.

        Clusters are a fully integrated solution. This example shows a 20-node cluster that includes 10 FAS systems with 6 disk shelves each, and 10 FAS systems with 5 disk shelves each. Each rack contains a high-availability (HA) pair with storage failover (SFO) capabilities.

Note:When you use both NAS and SAN on same system, the supported maximum cluster nodes are Eight. The 24 node cluster is possible when you use the Netapp storage only for NAS.

NetApp – Clustered DATA ONTAP – Objects and Components 
        Physical elements of a system such as disks, nodes, and ports on those nodes?can be touched and seen. Logical elements of a system cannot be touched, but they do exist and use disk space.
        An ONTAP cluster typically consists of fabric-attached storage (FAS) controllers: computers optimized to run the clustered Data ONTAP operating system. The controllers provide network ports that clients and hosts use to access storage. These controllers are also connected to each other using a dedicated, redundant 10 gigabit ethernet interconnect. The interconnect allows the controllers to act as a single cluster. Data is stored on shelves attached to the controllers. The drive bays in these shelves may contain hard disks, flash media, or both.
          A cluster provides hardware resources, but clients and hosts access storage in clustered ONTAP through storage virtual machines (SVMs). SVMs exist natively inside of clustered ONTAP. They define the storage available to the clients and hosts. SVMs define authentication, network access to the storage in the form of logical interfaces (LIFs), and the storage itself, in the form of SAN LUNs or NAS volumes.
          A single cluster may contain multiple storage virtual machines (SVMs) targeted for various use cases, including server and desktop virtualization, large NAS content repositories, general-purpose file services, and enterprise applications. SVMs may also be used to separate different organizational departments or tenants.
        The components of an SVM are not permanently tied to any specific piece of hardware in the cluster. An SVM’s volumes, LUNs, and logical interfaces can move to different physical locations inside the cluster, while maintaining the same logical location to clients and hosts. While physical storage and network access moves to a new location inside the cluster, clients can continue accessing data in those volumes or LUNs, using those logical interfaces.
         Clients and hosts are aware of SVMs, but may be unaware of the underlying cluster. The cluster provides the physical resources the SVMs need in order to serve data. The clients and hosts connect to an SVM, rather than to a physical storage array. A cluster, which is a physical entity, is made up of other physical and logical pieces. For example, a cluster is made up of nodes, and each node is made up of a controller, disks, disk shelves, NVRAM, and so on. On the disks are RAID groups and aggregates. Also, each node has a certain number of physical network ports, each with its own MAC address.
      A Data ONTAP cluster is a physical interconnectivity of storage systems, which are called "nodes". A cluster can include from 2 to 24 nodes in a NAS environment and 2 to 8 nodes in a SAN environment. Nodes are connected to each other by a private, nonroutable 10-Gb Ethernet interconnect. Each node has an HA partner node for storage failover (abbreviated as SFO). Both nodes are also peer nodes within the cluster. The storage of a node can failover to its HA partner, and its logical interfaces can failover to any node within the cluster.
      A cluster is typically composed of physical hardware: controllers with attached storage (solid state drives, spinning media, or both; or a third-party storage array when FlexArray is used), network interface cards, and, optionally, PCI-based flash cards (Flash Cache). Together, all of these components create a physical resource pool.
      This physical resource pool is visible to cluster administrators but not to the applications and hosts that use the cluster. The storage virtual machines (SVMs) in the cluster use these resources to serve data to clients and hosts.
      Storage controllers are presented and managed as cluster nodes, or instances of clustered ONTAP. Nodes have network connectivity and storage. The terms “node” and “controller” are sometimes used interchangeably, but “node” more frequently means a controller, its storage, and the instance of clustered ONTAP running on it.
HA Pair
       An HA pair consists of 2 identical controllers; each controller actively provides data services and has redundant cabled paths to the other controller’s disk storage. If either controller is down for any planned or unplanned reason, its HA partner can take over its storage and maintain access to the data. When the downed system rejoins the cluster, the partner will give back the storage resources.

1 comment:

  1. hi ashok
    it was a very brief and useful introductio . i am new to netapp and want do certification can u guide me how should i start reading.we have 2 node cdot system. plz help me in acheiving my goal