Internal Evaluation - 5 Marks (For Storage as a Service)

• As per given questions the assignment must be hand written in an A4 sized notebook or sheets.

• Every page of the assignment on top must contain your name and roll number

• The assignment must be photographed or scanned and submitted as pdf online

Questions List for Assignment

1. What is Direct Attached Storage? Also explain its limitations.

2. What are the three primary functions of storage networking?

3. What are the performance requirements for storage I/O?

4. What are the three basic types of storage subsystems that are used in backup & recovery?

5. Explain the role of file system in storage.

6. What are the factors affecting NAS performance?

7. Explain IEEE 802 reference Model.

8. Explain any two modern SCSI networking protocols.

9. What are the different types of file systems? Discuss

10. Explain cache management and cache data protection in detail

11. What is FCIP? Explain the FCIP protocol stack.

12. Explain various NAS File-Sharing Protocols

13. What is Restore and Restart Considerations in local replication

14. Discuss the security implementation FC SAN

15. Explain the various Storage Management Activities in in a storage infrastructure

16. Explain features of SMI-S simplify SAN management

1. What is Direct Attached Storage? Also explain its limitations.

 Direct Attached Storage (DAS) refers to a storage system that is directly connected to a host
computer (server, workstation, or PC) without any network device in between.
 It is one of the simplest and earliest forms of digital storage technology.
 A DAS device could be an internal hard disk inside the server, or an external storage device
connected via SCSI, SATA, SAS, or USB interfaces.
 Since the storage is directly tied to the server, the server itself is responsible for controlling
and managing the I/O operations.
  DAS is typically used in small to medium environments where applications do not require
large-scale data sharing or advanced storage management.
 Examples include small businesses using local hard drives, departmental servers, or
individual workstations that store their own data.
 While DAS is affordable and simple, its limitations in scalability, sharing, and management
make it unsuitable for enterprise-level applications where NAS (Network Attached Storage)
or SAN (Storage Area Network) are preferred.

Limitations of DAS:

1. Scalability Issues – Expansion requires physically adding more disks to the server, which is
limited by available slots. Once maximum capacity is reached, scaling becomes costly and
inefficient.

2. Limited Data Sharing – Unlike NAS or SAN, DAS cannot be easily shared among multiple
servers or users. Each server has its own dedicated storage.

3. Complex Management – In environments with multiple servers, each having its own DAS,
administration becomes complicated as storage cannot be centrally managed.

4. Availability Constraints – DAS lacks built-in redundancy features such as clustering or

mirroring across servers. If the host server fails, the data stored in its DAS becomes
unavailable.

5. Resource Underutilization – Since storage is tied to a single server, unused capacity on one
DAS cannot be shared with another system, leading to inefficiency.

2. What are the three primary functions of storage networking?

 Storage Networking refers to the use of dedicated high-speed networks to connect and
manage storage devices and servers.
 It is essential in enterprise environments where massive volumes of data need to be stored,
accessed, and protected efficiently.
 Together, these three functions ensure that enterprise storage systems are efficient,
accessible, scalable, and resilient.

The three primary functions of storage networking are:

1. Storage Consolidation

o Instead of maintaining multiple, isolated storage devices attached to individual

servers, storage networking consolidates them into a central storage pool.

o This centralization improves resource utilization, simplifies management, reduces

redundancy, and allows dynamic allocation of storage to applications as needed.

o Example: A SAN environment where multiple servers share a pool of Fibre Channel
storage arrays.

2. Data Sharing

o Storage networking allows multiple servers, users, and applications to share access
to the same data simultaneously.
 o This is particularly useful in collaborative environments such as enterprise databases,
cloud applications, or virtualized environments.

o Example: In a NAS system, multiple clients can access the same files using file-
sharing protocols like NFS or CIFS.

3. Data Protection and Management

o Storage networks enable advanced features like backup, recovery, replication,

snapshots, and disaster recovery across the enterprise.

o Security mechanisms such as encryption, zoning, and access control lists ensure data
confidentiality and integrity.

o Example: An enterprise SAN replicating data to a remote site for disaster recovery.

3. What are the performance requirements for storage I/O?

 Storage I/O (Input/Output) performance determines how effectively a system can handle
data requests from applications.
 Since modern businesses rely heavily on data-intensive applications such as databases,
virtualization, and big data analytics, optimizing I/O performance is critical.

The key performance requirements are:

1. Throughput

o Refers to the volume of data transferred per unit of time.

o High throughput ensures faster file transfers, database queries, and backup
operations.

2. Response Time (Latency)

o Latency is the time taken from when a request is made until it is completed.

o Low latency is vital for real-time applications, financial transactions, and database
performance.

3. Availability & Reliability

o Storage systems must ensure 24/7 data availability.

o Techniques like clustering, multipathing, and replication are used to achieve

reliability.

4. Scalability

o The system should handle increasing workloads without degrading performance.

o Cloud-based storage that can dynamically scale storage and IOPS based on demand.

5. Consistency

o Ensures data accuracy across multiple transactions.

 o Important in distributed environments where multiple servers may read/write to the
same data simultaneously.

6. Service Time & Queue Depth

o Service time is the actual time required to process an I/O request.

o Efficient queue handling ensures fair and fast request completion even under heavy
loads.

4. What are the three basic types of storage subsystems that are used in backup & recovery?

 Backup and recovery rely on storage subsystems that can store copies of data securely and
allow quick recovery in case of failures.
 In practice, modern enterprises often use a combination of disk for operational recovery and
tape/optical for long-term archival, following the “Disk-to-Disk-to-Tape (D2D2T)” strategy.

The three main types are:

1. Tape-Based Storage

o Traditionally used for backups and archives.

o Pros: High capacity, cost-effective, portable, and useful for offsite storage.

o Cons: Slow data access, sequential read/write makes recovery time longer.

o Example: LTO (Linear Tape-Open) cartridges for archiving enterprise data.

2. Disk-Based Storage

o Uses hard disk drives (HDDs) or solid-state drives (SSDs) for backup.

o Provides faster backup and restore compared to tapes.

o Often used with RAID configurations for redundancy.

o Example: Disk-based backup appliances used for short-term and operational

recovery.

3. Optical Storage

o Uses CDs, DVDs, or Blu-ray disks to store backups.

o Typically used for archival storage where data does not change often.

o Less common today due to capacity limitations but still used in specific industries
requiring long-term archiving.

5. Explain the role of file system in storage.

 A file system is the software layer that provides a structured way to store, manage, and
retrieve data on storage devices such as hard drives, SSDs, and NAS systems.
 It acts as the interface between the application layer and the physical storage devices.
Roles and Functions of a File System:

1. File Organization & Naming

o Provides a hierarchical structure (files and directories) so users can easily store and
retrieve data.

o Example: NTFS in Windows organizes files under folders and drives.

2. Space Allocation

o Divides the physical storage into blocks or clusters.

o Tracks which blocks are allocated and which are free.

o Prevents fragmentation and ensures efficient use of space.

3. Metadata Management

o Maintains information such as file size, type, owner, permissions, and timestamps.

o This metadata allows efficient searching and indexing.

4. Access Control & Security

o Implements authentication and permission models to protect data.

o Example: UNIX file permissions (read, write, execute).

5. Data Integrity & Fault Tolerance

o Journaling file systems (e.g., EXT4, NTFS) can recover quickly after crashes.

o Supports replication, snapshots, and consistency checks.

6. User Transparency

o Provides a logical abstraction of data storage, hiding the complexity of underlying

physical storage.

6. What are the factors affecting NAS performance?

 Network Attached Storage (NAS) is a file-level storage solution that connects to a network
and provides centralized data sharing across multiple clients.
 Its performance can vary significantly depending on several factors:

1. Network Bandwidth and Latency

o Since NAS operates over a TCP/IP network, its performance is directly influenced by
the available bandwidth.

o Latency also plays a role — even if bandwidth is high, excessive delay in data packets
will reduce application responsiveness.

2. File System Efficiency

 o NAS devices rely on internal file systems.

o The way a file system manages data, handles fragmentation, and maintains metadata
affects overall I/O speed.

3. Disk Subsystem Performance

o The underlying physical disks significantly affect NAS performance.

o RAID configuration (RAID 0, 5, 10) also influences read/write efficiency and fault
tolerance.

4. Caching Mechanisms

o NAS devices often use DRAM or NVRAM caches to store frequently accessed data.

o Proper cache management improves read/write performance, but insufficient or

poorly tuned caches can cause bottlenecks.

5. Concurrency (Number of Simultaneous Users)

o NAS devices serving too many users at once may experience performance
degradation.

o Protocol overhead adds to the load when multiple clients request access
simultaneously.

6. NAS Protocol Overheads

o File-sharing protocols introduce extra communication steps compared to block

storage.

7. Explain IEEE 802 Reference Model.

 The IEEE 802 Reference Model is a set of standards developed by the Institute of Electrical
and Electronics Engineers (IEEE) to define how communication occurs in Local Area
Networks (LANs) and Metropolitan Area Networks (MANs).
 It expands upon the OSI reference model by focusing specifically on the Data Link Layer
(Layer 2).

The IEEE 802 model divides the Data Link Layer into two distinct sublayers:

1. Logical Link Control (LLC) Sublayer

o Provides logical addressing and error control.

o Ensures reliable communication between network devices.

o Interfaces with the upper layers of the OSI model (particularly the Network Layer).

2. Media Access Control (MAC) Sublayer

o Manages how devices gain access to the transmission medium.

o Controls frame synchronization, addressing, and error detection.

 o Examples: Ethernet (802.3), Wi-Fi (802.11), Token Ring (802.5).

 Key IEEE 802 Standards:

 802.3 (Ethernet): Defines wired LAN communication.

 802.11 (Wi-Fi): Defines wireless LAN standards.

 802.15 (Bluetooth): Wireless Personal Area Network (WPAN).

8. Explain any two modern SCSI networking protocols.

 The SCSI (Small Computer System Interface) protocol was originally developed for
connecting peripheral devices directly to computers.
 Two major modern SCSI networking protocols are:

1. iSCSI (Internet SCSI)

o Uses TCP/IP to transmit SCSI commands over standard Ethernet networks.

o Allows creation of SAN-like environments without requiring expensive Fibre Channel

infrastructure.

o Benefits include cost-effectiveness, easy integration, supports long-distance

connections.

o Limitation: Performance can be affected by network congestion.

2. Fibre Channel Protocol (FCP)

o Maps SCSI commands over Fibre Channel networks.

o Provides high-speed, low-latency communication designed specifically for SANs.

o Benefits include reliablity and scalability.

o Limitation: Requires specialized hardware, making it more expensive than iSCSI.

9. What are the different types of file systems? Discuss.

 A file system provides the rules and structures for how data is stored, organized, and
retrieved on a storage device.
 Different file systems are optimized for different operating systems and workloads.

Types of File Systems:

1. FAT (File Allocation Table)

o One of the oldest file systems, used in DOS and early Windows.

o Pros: Simple, widely supported, ideal for portable storage.

o Cons: Limited file size and partition size.

2. NTFS (New Technology File System)

 o Default file system for modern Windows systems.

o Supports large file sizes, disk quotas, compression, encryption, and journaling.

o Provides better reliability and security compared to FAT.

3. EXT (Extended File System Family: EXT2, EXT3, EXT4)

o Commonly used in Linux distributions.

o EXT3 introduced journaling, while EXT4 supports very large volumes and faster
performance.

4. XFS

o High-performance file system developed by Silicon Graphics.

o Ideal for handling large files and parallel I/O operations.

o Popular in enterprise Linux environments.

5. ZFS (Zettabyte File System)

o Designed by Sun Microsystems.

o Provides advanced features like built-in volume management, data deduplication,

snapshots, and end-to-end checksumming.

o Extremely reliable for enterprise storage and cloud platforms.

6. HFS/HFS+ and APFS (Apple File Systems)

o HFS and HFS+ were used in older Mac OS versions.

o APFS (Apple File System) is optimized for SSDs, providing encryption and snapshots.

10. Explain cache management and cache data protection in detail.

 Cache in storage systems refers to high-speed memory (typically DRAM or NVRAM) used to
temporarily store frequently accessed data or I/O requests, reducing latency and improving
performance.
 Cache Management

 Read Cache: Stores frequently read data so that subsequent requests can be served quickly
without accessing slower disks.

 Write Cache: Temporarily holds write operations before committing them to disk, improving
perceived performance.

 Cache Policies:

o Write-Through: Data is written to both cache and disk simultaneously (safer, but
slower).

o Write-Back: Data is written first to cache, and later flushed to disk (faster, but risk of
data loss if cache fails).
  Cache Replacement Policies: Use algorithms like LRU (Least Recently Used) or MRU (Most
Recently Used) to decide which data to evict when cache is full.

 Cache Data Protection

Since cache is volatile memory, sudden power loss can result in data corruption. Protection
techniques include:

1. Battery-Backed Cache (BBWC): Keeps cache alive using batteries until power is restored.

2. Non-Volatile Memory (NVRAM): Uses persistent memory technologies so cached data

survives reboots.

3. Mirrored Cache: Data written to cache is duplicated across multiple controllers, ensuring
redundancy.

4. Error Detection & Correction (ECC): Protects against bit-level errors in cache memory.

11. What is FCIP? Explain the FCIP protocol stack.

 FCIP (Fibre Channel over IP) is a tunneling protocol that enables geographically dispersed
Fibre Channel SANs to be interconnected over existing IP-based networks.
 It is part of the FC-BB (Fibre Channel Backbone) standard and allows organizations to
leverage cost-effective IP WANs instead of expensive dedicated fibre connections.
 FCIP encapsulates native Fibre Channel frames into TCP/IP packets and transports them
across an IP network.
 At the destination, these packets are de-encapsulated and converted back into Fibre Channel
frames, making remote SANs appear as if they are locally connected.

FCIP Protocol Stack:

1. Fibre Channel Layer – Generates the native Fibre Channel frames from applications and
storage devices.

2. FCIP Encapsulation Layer – Encapsulates FC frames into IP packets.

3. TCP Layer – Provides reliable transport with error detection, retransmission, and congestion
control.

4. IP Layer – Routes encapsulated packets across the WAN.

5. Underlying Network Layer – Physical medium, such as Ethernet or MPLS.

12. Explain various NAS File-Sharing Protocols.

 NAS (Network Attached Storage) uses standard file-sharing protocols that allow clients to
access files over a TCP/IP network.
 NAS devices often support multiple protocols simultaneously to serve heterogeneous
environments (Windows, Linux, Mac).
 The major protocols include:
 1. NFS (Network File System)

o Developed by Sun Microsystems for UNIX/Linux environments.

o Provides file access over TCP/IP using RPC (Remote Procedure Calls).

o Common in enterprise data centers and HPC (High-Performance Computing).

2. CIFS/SMB (Common Internet File System / Server Message Block)

o Originally developed by Microsoft, widely used in Windows environments.

o Provides file and printer sharing across networked computers.

3. FTP (File Transfer Protocol)

o Provides file sharing between systems using a client-server model.

o Commonly used for large file transfers but less secure without encryption.

4. HTTP/HTTPS

o NAS systems may use web-based interfaces to provide file access.

o HTTPS ensures secure file transfer using SSL/TLS.

13. What is Restore and Restart Considerations in Local Replication?

 Local replication refers to creating a copy of data within the same storage array or data
center for operational recovery.
 Examples include snapshots, clones, and mirrors.
 When performing restores from local replicas, two considerations are crucial:

1. Restore Considerations

o Point-in-Time Copies: The replica must be consistent and reflect the desired
recovery point.

o Minimal Downtime: Restoration should not disrupt live applications for extended
periods.

o Granularity: Some restores may require individual files, while others may require
entire volumes.

2. Restart Considerations

o After restore, applications and databases must restart correctly without corruption.

o Database consistency requires techniques like write-order fidelity and application-

aware snapshots.

o Replication must ensure transaction logs are synchronized so systems can resume
operations from the point of failure.

14. Discuss the security implementation in FC SAN.

  Fibre Channel SANs (Storage Area Networks) require robust security because they carry
mission-critical enterprise data.
 FC SAN security is achieved through zoning, masking, authentication, and encryption to
ensure confidentiality, integrity, and availability of enterprise data.
 Security in FC SAN is typically implemented at multiple layers:

1. Zoning

o Defines communication paths within a SAN fabric.

o Two main types:

a. Hard Zoning: Enforced at the switch hardware level (more secure).

b. Soft Zoning: Based on WWNs (World Wide Names) and can be bypassed if
not properly configured.

2. LUN Masking

o Restricts host access to specific Logical Unit Numbers (LUNs) on storage devices.

o Prevents unauthorized hosts from accessing sensitive data.

3. Authentication and Authorization

o Techniques like DH-CHAP (Diffie-Hellman Challenge Handshake Authentication

Protocol) validate hosts and switches.

o Role-based access control ensures administrators only have appropriate privileges.

4. Encryption

o Data-at-rest encryption ensures that data stored in SAN disks is protected.

o Data-in-transit encryption secures traffic across Fibre Channel or FCIP links.

5. Audit and Monitoring

o Logging and monitoring SAN activities help detect intrusions and misconfigurations.

15. Explain the various Storage Management Activities in a storage infrastructure.

 Storage management is a critical function in any enterprise IT environment, ensuring that

storage resources are used efficiently, securely, and reliably. The key activities include:

1. Capacity Planning

o Monitoring usage trends and forecasting future requirements.

o Prevents over-provisioning and storage shortages.

2. Provisioning

o Allocating storage to servers, applications, and users.

o Includes tasks like creating LUNs, assigning file shares, and configuring RAID.
 3. Performance Management

o Monitoring IOPS, latency, and throughput.

o Identifying bottlenecks and tuning storage for optimal application performance.

4. Data Protection & Backup

o Implementing strategies like snapshots, replication, RAID, and backup scheduling.

o Ensures data can be recovered after failures.

5. Security Management

o Applying access controls, encryption, and compliance policies.

o Protects sensitive data against unauthorized access.

6. Monitoring & Reporting

o Using management software (e.g., EMC Unisphere, NetApp OnCommand) for

centralized visibility.

o Generates reports for audits, compliance, and optimization.

7. Troubleshooting & Maintenance

o Identifying and resolving issues in storage arrays, SAN fabrics, or NAS devices.

o Includes firmware upgrades and patching.

16. Explain features of SMI-S simplify SAN management.

 SMI-S (Storage Management Initiative Specification) is an industry standard defined by the

Storage Networking Industry Association (SNIA) to simplify and unify SAN management
across multi-vendor environments.
 In essence, SMI-S brings vendor-neutral, centralized, and simplified SAN management,
which is especially useful in complex enterprise environments with heterogeneous storage
systems.

Features of SMI-S:

1. Standardized Interface

o Provides a common API for managing storage devices from different vendors.

o Eliminates the need for vendor-specific management tools.

2. Interoperability

o Ensures storage arrays, switches, and software from multiple vendors can work
together.

o Example: An EMC storage array and an HP switch can be managed under the same
framework.

3. Automation and Simplification

 o Automates routine tasks such as provisioning, zoning, and monitoring.

o Reduces administrative overhead and configuration errors.

4. Extensibility

o Supports new technologies and storage features as they emerge.

5. Security and Compliance

o Provides secure management operations, supporting role-based access control.

o Helps organizations meet regulatory compliance requirements.

6. Monitoring and Reporting

o Collects standardized performance metrics for analysis.

o Enables proactive capacity planning and troubleshooting.