Block Storage vs. File Storage
Vložit
- čas přidán 25. 02. 2019
- To learn more about block and file storage, visit ibm.biz/BdPSYE
Check out IBM Cloud Block Storage: ibm.biz/BdPSYX
Check out IBM Cloud File Storage: ibm.biz/BdPSYH
In this lightboarding video, Amy Blea gives an overview of two types of traditional cloud storage: block storage and file storage.
What are the advantages of each? How are the two types of storage set up? Which type of storage should you use if you need low latency, high scalability or the ability to share data with multiple users?
Get started for free on IBM Cloud → ibm.biz/sign-up-today
Subscribe to see more videos like this in the future → ibm.biz/subscribe-now
#BlockStorage #FileStorage #ObjectStorage - Věda a technologie
Very nice explained, thank you!
Thanks, this is nice summary.
Thank you for the breakdown!
So helpful! Thank you for this video, clarifies this concept for me!
Thanks for the easy to understand info!
very well expained! thanks
Really simplistic and insightful.
Nice! Brief and insightful.
Thanks Joseph!
Perfectly done.
Great summary! Really appreciate it.
Glad it was helpful!
This was excellent! Easy to understand.
Thanks Michael! Appreciate you watching.
Hmm I guess it's just me..but what you describe, they both sound the same?? So both are stored on Hard Disk Drives..or SSD's...but after that what you're descibing sounds the same for both..I'm not seeing the difference
Block mean raw : file system presented to any OS ......... Now that os will format, put the filesystem on this HDD and SSD..... wheras file means Some intermim OS has carved out file system on top of thos SSD/HDD enabled SMB/NFS and presented the Logical disk onto the network....
"Block vs File" is really about how your operating system sees the device. In terms of Linux whenever you attach a USB or a new hard-drive to your motherboard, once the device is detected Linux Kernel (with the help of UDEV process) exposes the device in the '/dev' directory. All devices in '/dev' or '/mnt' directories are block devices. This means OS will send blocks (512 bytes or 4K or 8K) data at a time to the controller of the device. On the contrary when you have a NAS the OS will only see the Network Card. The actual disks are not directly attached to the OS. In that case OS will send a whole file (instead of byte blocks as explained before) using TCP/IP. Having said that, SAN does have network attached storage controllers but the device appears to the OS as a local device writable at block byte level.
Good, but seems to indicate a choice between file and block data. File data and block data are both a part of any enterprise environment, they just serve different purposes.
Brilliant post
Thanks, so simply described.
Thanks for the feedback! 👍
Amy, I've read that File Storage allows to connect via NFS (network shares). An IBM Sales representative was not able to answer this question: is it possible to access IBM Cloud File Storage via NFS from outside IBM Cloud, by attaching the network share to our local workstations? We would not be using File Storage from VM's or applications within the IBM Cloud network, just from outside. Thanks
Hi Florian! NFS and block mounts/endpoints are not available outside of IBM Cloud infrastructure space.
Gracias por compartirlo...
3:31 --- traditional . . . yes, in those drawn config. Nonetheless stylishly presented 👍 and an useful video in terms of showing the building blocks.
Among other things, one now may witness HA/failover with HCI for power (mains & battery), network (NICs, switches, cables), storage (spinning and nand), and compute (cpu+mem).
Kindest regards, neighbours and friends.
Thank you!
File storage is usually compared to NAS and one of draw back of NAS is scalability; while SAN has the advantage of scalability. So not sure why file storage is considered highly scalable.
thank you
Thank you
So NAS has single volume? if it goes down file is lost ? Or it is also redundant, if it is also redundant then both looks same. Confused.
I would imagine the NAS is set up as RAID 1 configuration, creating redundancy in case of drive failure. But keep in mind, I am only a college student...so take what I say with a grain of salt.
depending on the RAID configuration the drivers may be redundant among themselves however, they're attached to the NAS device, so if the power goes down you won't be able to access the shared files because the drivers are attached to the NAS that has no power to keep it up and running.
So In background This NAS volume can have RAID configured as desired Could be RAID 1, 10,5 or whatsoever desired.. But in Front end its just 1 volume which will be shared on network... and all the other server connected to network if authorized can access the same.
great explanation
Thank you Yatanveer.
Thanks!!!
Thanks 👌
After this I am most confounded. By this: how do you write backward so well?!!!
No worries, Brooks. We wrote a post to explain how we make these videos here: ibm.co/2SA1vGd Thank you for visiting our channel. Amy
Saludos al profe Sánchez Lara!
How do they record these?
Does the presentator really draw mirrored?
The video is reversed after being recorded. So even though it looks like she's using her left hand, it's actually her right hand.
Video of type of API´s different technologies
It is really hard to focus not to notice but to think are you really writing backwards? I might have to watch your video again to understand the subject this time.
❤️❤️❤️
wait... I read SAN is scalable and NAS is not... Here it is reversed.... lol
are you actually writing reverse
1000th like
Differently now have a much better idea about SAN .
😂
this is an academic view, real world is otherwise
She's says "um" too much,. Other than that, thank you!
bus have more knowledge about storage .
Very nice explained, thank you!