She manages NetApp storage onsite for a government customer. Network Attached Storage (NAS) is more abstracted than SAN storage. E-Series SAN is purpose-built for security, speed, reliability, scalability, and manageability, which makes it ideal for video surveillance storage, even among other NetApp SAN systems. I have another question Can same volume can  contain both LUN and NAS ? As security organizations grow their video surveillance deployments by adding and upgrading cameras, they look to enterprise storage for speed, scalability, manageability, and reliability to support crucial video systems. So is this the way i can differentiate between NAS and SAN volume. SAN functionality is a "bolt on" on top of the NAS functionality. Any property from volume ? I furhter recommend to install the OnCommand System Manager to administrate your storage system. From this abstraction comes one of NAS’ biggest advantages: simplicity. NAS Protocols; NetApp and SAN; SAN Use Cases. It was the best of storage protocols, it was the worst of storage protocols. The ability to shrink volumes to reclaim over-allocated space is a pretty big benefit. And for decades that’s been just fine. SAN (Storage Area Network) is a block-level storage protocol, meaning data is stored and accessed in blocks. It's a VM an can be used with VMware Player/Workstation/ESX/Fusion. File shares and home directories make up a lot of this unstructured data. Instead of blocks, data lives in volumes that are made up of files and folders. SAN and NAS each have their own benefits and trade-offs. How Can i find the capacity (Used or free) for block and file part for netapp filer? Another caveat is, depending on the file system, you may be limited to having a single host read and write data. Okay, I’ll stop with the Tale of Two Cities spoof. Her enthusiasm for all things tech and her desire to share knowledge has earned her the unofficial title "Trainer of Sys Admins" for her team. NFS datastores comprise another part of NAS data. See That's a bit more complicated, but in principle you should use dedicated volumes for LUNs, which should make checking capacity fairly straightforward (e.g. Natively, everything is NAS with a NetApp. NetApp ® NAS solutions simplify data management and help you keep pace with growth while optimizing costs. From the doc i understand NAS filer can be connected to NAS or SAN  but i would like to know about the internal drive which is present in netapp filer ? While some enterprise storage vendors push scale-out file systems (NAS) for video, the NetApp® video surveillance storage solution is built on NetApp E-Series SAN storage. Clients access folders and files from a UNC path that the NAS server shares. I recommend doing a little bit more basic reading of Netapp documentation to get a better understanding of how your filer works. there is do difference between internal and external disks. Even though NetApp FAS and AFF systems can do both SAN and NAS, we don’t try to shoehorn our flagship products into every use case. If you serve data using the SAN protocol, you may have specialized hardware for transporting storage area network traffic. From this aggregate you create several volumes. To an end device like a server, these LUNs look like direct-attached-storage (DAS) or a local drive. Separate hardware is actually an advantage to using SAN as a storage protocol. OCI Type Reports Whats changed Traditional video surveillance deployments that record data to dedicated digital video recorders (DVRs) or network video recorders (NVRs) don’t need a lot of specialized skills to manage—if they’re small, that is. A caveat to block storage is that you need to format the drive with an operating system-specific file system. When using SAN as a storage protocol, you really can only grow those LUNs. I can see reasons to keep them separate for usability, tidiness, and 'why not' reasons but I'm more interested in 'real gotchas' that mixing SAN/NAS might introduce. For instance, if you serve your SAN data using Fibre Channel Protocol, you have Fibre Channel switches and HBAs (host-based adapters) dedicated for this traffic. It’s the typical client-server architecture. When used as a SAN yes, it is truly a SAN. Like most IT questions on which approach to take when selecting a storage protocol to use, the answer is, “It depends.” Fortunately, it’s not an either-or question. Files that lie inside the LUN cannot be seen from the Filer, the Filer only sees a big chunk of Data (LUNs).