Popular New Releases in Network Attached Storage
Popular Libraries in Network Attached Storage
by jmathai python
An EXIF-based photo assistant, organizer, manager and workflow automation tool.
by dstamoulis python
Single-Path NAS: Designing Hardware-Efficient ConvNets in less than 4 Hours
by flipkart-incubator python
Flipkart's visual search and recommendation system
by wuseman shell
Cheatsheet and bash scripts sripts for Synology Nas Stations cheet cheat sheet nas networkdisk
by AlexPresso shell
Patcher to enable DTS, EAC3 and TrueHD support to Synology VideoStation (DSM 7.0 ready)
by luckylz2git shell
Perfect shell scripts to auto mount exfat disk partition on Synology DiskStation NAS (x86 platform), and more post-mount functions are coming soon! Use this at your own risks.
Trending New libraries in Network Attached Storage
Top Authors in Network Attached Storage
Trending Kits in Network Attached Storage
No Trending Kits are available at this moment for Network Attached Storage
Trending Discussions on Network Attached Storage
How can I read/write data from/to network attached storage with kedro?
About NAS and SAN(protocols, architecture, etc..)
How can I read/write data from/to network attached storage with kedro?Asked 2020-May-14 at 09:24
ANSWERAnswered 2020-May-14 at 09:24
So I'm a little rusty on network attached storage, but:
If you can mount your network attached storage onto your OS and access it like a regular folder, then it's just a matter of providing the right
filepathwhen writing the config for a given catalog entry. See for example: Using Python, how can I access a shared folder on windows network?
Otherwise, if accessing the network attached storage requires anything special, you might want to create a custom dataset that uses a Python library for interfacing with your network attached storage. Something like pysmb comes to mind.
The custom dataset could borrow heavily from the logic in existing
kedro.extras.datasets datasets, but you replace the filepath/fsspec handling code with
About NAS and SAN(protocols, architecture, etc..)Asked 2020-Apr-07 at 09:44
I am currently kind of having trouble to understand between NAS and SAN.
As far as I figured out, NAS and SAN are kind of defined as below.
NAS(Network attached storage)
- Usually used as file storage and use Ethernet Infrastructure to communicate
- As file storage, support protocols like NFS, CIFS, SMB, HTTP(S)
SAN(Storage Area Network)
- Network Protocol to communicate with block storage for data access.
- Configured with separated network system
- Commonly based on Fibre Channel(FC) technology.
- Could use iSCSI(in small and medium sized business) or FCoE for less expensive alternative to FC
So, below is my questions.
1. Is File Storage and Block Storage are the solutions? I researched and found that NAS is File Storage Solution and SAN Storage is Block Storage Solution.
- In that case, are their base infrastructure(storage device) same? Only different with protocols, network devices, may be storage os something that controls underline device and way of usage?
2. I found there are NAS Solutions that support iSCSI. But I found that iSCSI is SCSI Protocol that use TCP/IP Network system and SCSI is for block level storage communication protocols.
- And Now I am confused. NAS is a file storage solution and how could that support iSCSI Protocol?
3. Are AWS root disk and EBS storage SAN Storage?
- I read that SAN Storage configuration could be expensive so iSCSI or FCoE are less expensive way to configure.
- With what technology AWS storage Infrastructure is configured??
I am kind of newly studying of these storage part computer science and got some questions.
Is there anyone can explain those questions clearly?
ANSWERAnswered 2020-Apr-07 at 09:44
It depends on what you call a "Solution". The basic infrastructure is the same it's a some kind of a "storage server" (storage system) with physical disk(s), but it very much dependent of technologies, vendors and various options. Typically, a storage system provides access to its physical disks with different protocols of 2 main groups: block-level protocols like SCSI or rarely ATA on one hand, or file-level protocols like NFS, CIFS, etc on the other. It doesn't mean, a storage system can't work in both, block and file modes.
Storage network - SAN can be build over FC, FCoE, converged infrastructure, pure TCP/IP for iSCSI, Infiniband or any other infrastructure. Typically, when people say "SAN" they mean Block storage devices and FC protocol, but it doesn't mean, that a file storage - NAS can't be connected with SAN and vice verse.
Tutorials and Learning Resources in Network Attached Storage
Tutorials and Learning Resources are not available at this moment for Network Attached Storage