Order by
17 terms
Terms | Definitions |
|---|---|
 Def: NAS Implementation - Unified NAS | **
consolidates NAS-based and SAN-based data access within a unified
(single) storage platform and provides a unified management interface
for managing both the environments |
| NAS Implementation - Unified NAS | - performs file serving and storing of file data along with providing access to block-level data - supports both CIFS and NFS protocols for file access and iSCSI and FC protocols for block level storage - Provides unified management for both NAS head and storage |
| Def: NAS head | ** are connected to the storage controllers (SCs) which provide access to the storage - these storage controllers also provide connectivity to iSCSI and FC hosts - Storage may consist of different type of drives, ex. SAS, ATA, FC and flash drives to meet different workload requirements |
| Unified NAS Connectivity | - Each NAS head in a unified NAS has front-end Ethernet prots, which connect to the IP network - Front-end ports provide connectivity to the clients and service the file I/O requests - Each NAS head has back-end ports to provide connectivity to the storage controllers - iSCSI and FC ports on a storage controller enable hosts to access the storage directly or through a storage network at the block level |
| NAS Implementation - Gateway NAS (def) | ** device consists of one or more NAS heads and uses external and independently managed storage * NAS heads acces SAN-attached or direct-attached storage arrays |
| NAS Implementation - Gateway NAS | - NAS heads share storage with other apps servers that perform block I/O - Requires separate management of NAS head and storage - more scalable compared to unified NAS because NAS heads and storage arrays can be independently scaled up when required |
| Gateway NAS Connectivity | - Communications between the NAS gateway and the storage system in a gateway solution is achieved through a traditional FC SAN - to deploy a gateway NAS solution, factors, such as multiple paths for data, redundant fabrics, and load distribution must be considered |
| NAS Implementation - Scale-out NAS (def) | ** pools multiple nodes together in a cluster that works as a single NAS device * pool in managed centrally |
| NAS Implementation - Scale-out NAS | - Scales performance and/or capacity with addition of nodes to the pool non-disruptively - Creates a single file system that runs on all nodes in the cluster * clients, connected to any node, can access entire file system * file system grows dynamically as nodes are added - Stripes data across all nodes in a pool along with mirror or parity protection |
| Scale-out NAS Connectivity | - clusters use separate interneal and external networks for back-end and front-end connectivity, respectively - internal network provides connections for intracluster communication - external network connection enables clients to access and share file data - each node in the cluster connectes to the internal network - internal network offers high throughput and low latency and uses hgh-speed networking technology such as Infiniband or gigabit ethernet - to enable a client to access a node, the node must be connected to the external Ethernet network - Redundant internal or external networks may be used for high availability (read slide for connectivity page 21) |
| NAS Use Case 1 - Server Consolidation with NAS | -
traditionally network file system for UNIX and Windows are housed
together in a single system while still maintaining their integrity - Using NAS, the same file system can be access via diff protocols, either NFS or CIFS & still maintain the integrity of the data & security structures as long as the apps used for both methodologies understand the data structures presented |
| Def: File-level Virtualization | **eliminates dependency between data accessed at the file-level and the location where the files are physically storage |
| File-level Virtualization | - creates a logical pool of storage, enables users to use a logical path, rather than a physical path, to access files - Uses global namespace that maps logical path of file resources to their physical path - Provides non-disruptive file mobility across file servers or NAS devices (clients able to access their files nondisruptively) |
| Comparison Before File-level Virtualization | - Dependency between client access and file location - Underutilized storage resources - Downtime is caused by data migrations |
| Comparision After File-level Virtualization | - Break dependencies between client access and file locations - Storage utilization is optimized - Non-disruptive migrations |
| EMC Isilon | - Scale-out NAS solutions - Includes 'ONeFS' OS that creates a single file system across Isilon cluster - Provides ability to nondisruptively add nodes to Isilon cluster - Includes 'SmartPools' that enables different node types to be mixed in a single cluster - Monitors component health and transparently reallocates files - Uses 'Autobalance' that rebalances data automatically when a new node is added to the cluster - Uses 'FlexProtect' that protects from up to four simultaneous failures of either nodes or individual drives |
| EMC VNX Gateway | - Gateway NAS solution - Provided multi-protocol network file system access, dynamic expansion of file system, high availablility, and high end performance - Comprises one or more NAS heads called 'X-blades' that run VNX operating environment - Includes 'control station' that provides a single point for configuring X-Blades http://quizlet.com/14506169/network-attached-storage-nas-nas-implementation-and-file-level-virtualization-flash-cards/ |
0 comments:
Post a Comment