Data Network Fundamentals

NetApp module number three! I have to admit I wasn’t a total fan of this module, don’t get me wrong I love learning new things. However, the person talking in this module was a few times inaudible to me, as well as having to correct himself a lot and speaking in one tone. I find that incredibly difficult to follow, plus this subject isn’t the most exciting :-D, anyway let’s begin 🙂

Course objectives

NAS and SAN

Heading back into some of the things talked about in the Storage Fundamentals module, but expanding on them a bit more.

Data Storage and Data Networking

  • Storage: Storing and protecting data for as long as you need it – data over time
    • Information repository
    • Capacity
    • RAID, JBOD
  • Networking: Transporting data from one location to another quickly and reliable – data over distance
    • Information movement
    • Speed
    • Hubs, switches

Direct Attached Storage/DAS

20150326_135954-1337826546

Hello, DAS our old friend :-). Simpliest type of storage outside the system it is used. Simple, self contained system where the application, file system and storage are connected directly to each other. Two methods were developed to provide additional storage and data access across mutiple users, workstations, they are; Network Attached storage/NAS and Storage Area Networks/SAN.

Network Attached Storage/NAS

20150326_140008-923435136

In NAS the device is attached directly to the network, will appear as another system. A system where files are stored, because it’s on the network other machines are able to access it, a single NAS device could provide data to a variety of network application machines.

Storage Area Network/SAN

20150326_140018-704186959

In a SAN system storage appears to the network as another hard drive that is shared among various systems.

NAS versus SAN

NAS

  • File system and storage in one device which is then connected to the network
  • Easier to network
  • Simplier to manage
  • Storage appears to other computers as a file server

SAN

  • Storage is on its own network for tranporting files.
  • Work of transporting files is moved off the LAN and on to the dedicated fabric of the SAN.
  • Storage appears as a disk drive that can be mounted on computers that use it.

Both NAS and SAN have their own strengths.

NAS: Connections, Attachments and Access

20150326_140030292699181

Client computers are connected via LAN. The NAS system is attached to the LAN network both the filer and the storage systems contained within the NAS system.

  • Data treated as files/file access
  • Files managed within the NAS system
  • Management simplified

SAN: Connections, Attachments and Access

20150326_140038-691552148

Client computers are connected via LAN. A SAN network is attached to the LAN network. The SAN network is a network of hardware that is dedicated to their data storage. Usually SAN systems are more flexible and handle disaster recovery better than NAS systems but can usually be more difficult to set up.

  • Broken up into blocks and stored as data blocks/Block access
  • Files managed outside the SAN system
  • Configuration flexible
  • Performance high

SAN Connections: iSCSI, SAS and FC

iSCSI
Which stands for “Internet small computer system interface”, IP based standard that is the primary alternative to FC (fibre channel). Uses standard cables and switches and can send signals longer distances. Supports all ethernet interfaces. It has high speeds and is the less expensive choice. However, it has low dependability.

SAS
Which stands for “Serial attached SCSI”, uses aerial cables and carries SCSI packets. It is created with serial cables rather than ethernet cables. Data cables cannot be longer than 8M and the hard ware limits the number of connections that can be provided. Is inexpensive and more reliable than iSCSI.

FC
Which stands for “Fibre channel”, protocol designed to allow the SAN environment to signal information. Can use either optic cabling, fibre optics or copper wiring. FC is very reliable and scalable. Enables you to add storage without destructing operations. Is very flexible.

FC: Topologies and Zoning

  • FC-P2P (point to point): Is the simpliest topology. Host server is connected directly to the storage appliance. However, it’s very limited.
  • FC-AL (arbitrated loop): All devices are within a loop which can cause problems because if there is a failure of any one device it can cause a break in the loop. Allows more connections than FC-P2P.
  • FC-SW (switched fabric): All devices including the host and storage systems are interconnected through fibre channel switches, these switches maintain the state of the fabric providing optimized interconnections and security.

Zoning: A group of fibre channel ports that can communicate with each other only if their in their zone or zones.

  • Hard zoning: zone members are defined by a fibre channel switch and its ports. Offers improved security and can be easier to manage.
  • Soft zoning: A cable can be moved from one port to another without reconfiguring the zone. Offers excellent flexibility and scalability.

Does any one of my classmates understand this part of the module? The topologies and zoning, I’m having a hard time wrapping my head around. It always catches me by surprise how indepth you can go with a single aspect of networking and a lot of the time I lose myself in it and get confused!

File and Block Storage, High Availability and High Performance Computing

File Storage versus Block Storage

  • Block Storage
    • Uses configurable length or block size
    • Set standard chucks of data
    • Better flexiblity and high performance
    • Administrators can choose the configuration that best suits their needs
    • More complicated
  • File Storage
    • Much simplier for the end user and the system
    • Less flexible
    • Sacrifices performance to achieve simplicity
    • Data organised as files

A nice comparison they used in the module to compare the two, was the difference between manual driving (block storage) and automatic driving (file storage). Thought I would mention it because anyone struggling with understanding file and block storage would make some sort of sense of it from that excellent comparison :-).

Although this module was definitely not my favourite one, it was still a helpful and informative module. It is also helpful writing these summarised blogs, helps me go through the information of the module and understand it fully. Four modules left to go :-), Cloud fundamentals next :-).

Virtualis(z)ation Technology Fundamentals

The next NetApp module I completed was on Virtualisation! I know right! Awesome!

The module started off talking about what virtualisation actually is. Which I think is an important aspect of the whole module because you have to know what something actually is before you can even begin to understand what it does.

What is Virtualisation.

So, “breaking the bond between hardware and applications”. Basically the creation of some “virtual” rather than “physical”. It is there but you can’t “touch, feel” it.

Server Virtualisation

virtualserver
http://databasics.com.au/products/helios/virtual_server_app

Having a virtual environment rather than a physical environment changes everything radically; less space due to a single box, the ability to run multiple operating systems and multiple applications. All of these applications share the CPU and RAM of the server which offer much greater utilization of those valuable resources. Utilization increases to 60% or more. Having a virtual environment can also save time, due to less time having to be spent on upgrading, maintaining and backing up.

So, what are the summarised benefits of sever virtualisation?

  • Lower costs
  • Less power
  • Less cooling
  • Less space needed
  • Increased flexibility
  • Faster implementation of new applications
  • Higher availability

That all seems to good to be true, right? Well unfortunately there are some challenges to server virtualisation.

  • Hardware outages are more serious
  • Backup of a virtualised environment could be impossible within the traditional backup window
  • Storage failure can wipe out numerous applications

Although there are challenges to using a virtual environment in place of a physical one. There are no more than there would be running a physical environment in fact there would probably be more. Virtual environments are the future, slowly but surely each and every business who have thought about ways to save money and time have done the switch over to virtual and it won’t be long before every business runs virtual. What do my classmates think on this matter? Is a virtual environment better than a physical one?

Storage Virtualisation

Storage-Virtualization01
http://www.sanstorageworks.com/Compellent-Storage-Virtualization

Why storage virtualisation?

Storage virtualisation doesn’t lower any costs, in fact it’s server virtualisation that lowers the costs. For example; $1 of VMware requires $3 to $5 of storage.

Data storage requirements are growing

20150326_100619-1506335287
Oliver Wyman VMware Storage Total Cost Comparison Interviews Aug-Sept 2007

The actual total cost benefits organisations achieve vary depending on the storage solution deployed with VMware”.
– Oliver Wyman

NetApp Storage Virtualisation

Where VMware is the king of server virtualisation, NetApp are the kings of storage virtualisation.

  1. Pooled resources
  2. Multiprotocol
  3. Higher utilization
  4. Lower TCO (total cost of ownership)
    1. Operational costs
    2. Management
    3. Training

NetApp solves storage problems with their superior data protection by using RAID-DP, which is significantly less expensive than RAID 10.

NetApp allows back ups to be a much easier process by using a feature they call “Snapshot”, basically taking a snapshot of the data, doesn’t copy old data just updates as it comes and stores it in a bit of disk reserved called SnapReserve.

Virtual Environment without Storage Virtualisation

20150326_105328816760086

Most storage disks used today do not utilize all the available space, some is left to waste, applications cannot get to the space and fills up in other places (example in picture on the left). This leads to having to buy more storage. Whereas NetApp uses every little tiny nook and cranny of space (example in picture on the right).

Additional benefits of NetApp Storage

  • Poded storage
  • Disaster recovery more accessible
  • Investment protection

Virtualisation course summary

That wraps up the NetApp virtualisation module. This module was excellent and incredibly easy to follow! I love everything virtual so I had no doubt that I would love this one. It was also interesting to learn about the services that NetApp provides and what makes them the kings of storage virtualisation. It was helpful to learn why virtual environments outshines almost in every way a physical environment, useful for our NET601 assignment as well as for future reference 😀

Hello there!

Hello, my name is Anna Norman and I am a student at Nelson Marlborough Institute of Technology! I am currently in my second year of a Bachelor in Information Technology and I’m loving it! This blog is for my Networking Fundamentals (NET601) class, to record my progress with my online NetApp University Academic Alliance course. I will post after I have successfully completed a module. My posts will include;

  • a summary of what the material was about.
  • screenshots of what I believe shows important material
  • any questions that I would like the ask my class – something I didn’t understand or something interesting that I would like to point out.

So, off we go to explore how networking makes the world go round!