Anyone who has used a Storage Area Network (SAN) has probably used block
level storage before. Block level storage presents itself to servers
using industry standard Fibre Channel and iSCSI connectivity mechanisms.
In its most basic form, think of block level storage as a hard drive in
a server except the hard drive happens to be installed in a remote
chassis and is accessible using Fibre Channel or iSCSI.
When it comes to flexibility and versatility, you can't beat block level storage. In a block level storage device, raw storage volumes are created, and then the server-based operating system connects to these volumes and uses them as individual hard drives. This makes block level storage usable for almost any kind of application, including file storage, database storage, virtual machine file system (VMFS) volumes, and more. You can place any kind of file system on block level storage. So, if you're running Windows, your volumes will be formatted with NTFS; VMware servers will use VMFS.
Remember, when you use a block-based volume, you're basically using a blank hard drive with which you can do anything.
From a use case standpoint, there are a lot of applications that make use of this block-level shared storage, including:
The two most popular storage system technologies are file level
storage and block level storage. File level storage is seen and
deployed in Network Attached Storage (NAS) systems. Block level storage
is seen and deployed in Storage Area Network (SAN) storage. In the
article below, we will explain the major differences between file level
storage vs. block level storage.
File Level Storage - This storage technology
is most commonly used for storage systems, which is found in hard
drives, NAS systems and so on. In this File Level storage, the storage
disk is configured with a protocol such as NFS or SMB/CIFS and the files
are stored and accessed from it in bulk.
When it comes to flexibility and versatility, you can't beat block level storage. In a block level storage device, raw storage volumes are created, and then the server-based operating system connects to these volumes and uses them as individual hard drives. This makes block level storage usable for almost any kind of application, including file storage, database storage, virtual machine file system (VMFS) volumes, and more. You can place any kind of file system on block level storage. So, if you're running Windows, your volumes will be formatted with NTFS; VMware servers will use VMFS.
Remember, when you use a block-based volume, you're basically using a blank hard drive with which you can do anything.
From a use case standpoint, there are a lot of applications that make use of this block-level shared storage, including:
- Databases. This is especially true when you want to cluster databases, since clustered databases need shared storage.
- Exchange. Although Microsoft has made massive improvements to Exchange, the company still does not support file level or network-based (as in, CIFS or NFS) storage. Only block level storage is supported.
- VMware. Although VMware can use file level storage via Network File System (NFS), it's very common to deploy VMware servers that use shared VMFS volumes on block level storage.
- Server boot. With the right kind of storage device, servers can be configured to boot from block level storage.
No comments:
Post a Comment