21. NAS Evolution Network Attached Storage (NAS) Stand Alone PC Networked File Sharing Networked PCs Portable Media for File Sharing
22.
23. General Purpose Servers vs. NAS Devices Network Operating System I/O File System Print Drivers Applications General Purpose Server (NT or Unix Server) Network Operating System File System Single Function Device (NAS Server)
24.
25. NAS Device Components NAS Device CIFS NFS Network Interface Storage Interface NAS Device OS SCSI, FC, or ATA IP Network
26. NAS File Services Protocols: NFS and CIFS NAS Device Network Interface Storage Interface NAS Device OS SCSI, FC, or ATA CIFS NFS IP Network Windows Unix NFS CIFS
27.
28.
29.
30. Integrated vs. Gateway NAS Integrated NAS NAS Gateway IP Network IP Network FC Fabric NAS Head NAS Head
31. Integrated NAS System Integrated NAS System NAS Head Storage Direct Attach IP Network
32. Gateway NAS System Clients Application Servers Storage NAS Gateway FC Switch IP Network
33.
34. Fibre Channel Storage Area Networks (SAN) Module 3.3
35.
36.
37.
38.
39.
40. Evolution of Fibre Channel SAN SAN Islands FC Arbitrated Loop Interconnected SANs FC Switched Fabric Enterprise SANs FC Switched Fabric HUB
41.
42.
43.
44.
45. Nodes, Ports, & Links Node HBA Port 0 Port 0 Port 1 Port 1 Port n Port n Link Port 0 Port 0 Rx Tx
56. World Wide Names: Example World Wide Name - HBA 1 0 0 0 0 0 0 0 c 9 2 0 d c 4 0 Reserved 12 bits Company OUI 24 bits Company Specific 24 bits World Wide Name – Array 5 0 0 6 0 1 6 0 0 0 6 0 0 1 B 2 0101 0000 0000 0110 0000 0001 0110 0000 0000 0000 0110 0000 0000 0001 1011 0010 Company ID 24 bits Port Model seed 32 bits
82. IP Storage Approaches iSCSI FC FC FC FC FC IP Network IP Network IP Network IP Network iFCP FCIP iFCP Switch iFCPSwitch FCIP Router FCIP Router iSCSI/FC Gateway
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94. iSCSI Model Layers IP Header TCP Header iSCSI Header SCSI Data SCSI Command Descriptor IP Datagram Storage IP Payload IP Payload SCSI CDB encapsulation
112. How CAS Stores a Data Object Application Server Client CAS API Object ID Client presents data to API to be archived 1 Unique Content Address is calculated 2 Object is sent to CAS via CAS API over IP 3 CAS authenticates the Content Address and stores the object 4 Acknowledgement returned to application 5 Object-ID is retained and stored for future use 6
113. How CAS Retrieves a Data Object Application Server Client CAS Object is needed by an application 1 CAS authenticates the request and delivers the object 4 Application finds Content Address of object to be retrieved 2 Retrieval request is sent to the CAS via CAS API over IP 3 API Object ID