What is Block Storage?

What is Block Storage?

There are three common ways to organize and store data on modern enterprise storage devices – File Level, Object Level and Block Level. Block Level Storage refers specifically to saving data in volumes called blocks. Block storage is when a raw volume of data storage is presented to a server, usually from a storage attached network (SAN), and each volume block can function as an individual hard drive or storage repository.

Block storage can be presented to any operating system as a mounted drive volume. A storage consultant can allocate almost any size of data volume to a server. The end user will simply see this as a mapped drive or a local hard drive on the server’s operating system. The server operating systems can access the storage blocks over high-speed Fiber Channel or iSCSI connectivity options, according to ENTERPRISEstorageFORUM.

The target server operating system can be either physical or virtual; however, physical servers require additional storage controllers to access the raw SAN block volumes. On a SAN, files are split into evenly sized blocks of data, and the size of each block is determined by the manufacturers hardware capabilities and the storage architect’s infrastructure design, according to Data Center Knowledge. Block sizes can vary if flash storage or standard disk storage is used, and choosing the correct block size for the client data is vital to ensure maximum performance. Each data block is then given a location ID by the operating system to keep track of where each block of data is written to on the SAN.

In Object and File level storage principles, metadata is used to arrange the data in a specific hierarchical method on disk, and this metadata usually contains information such as name of file, size and where and when it was written to disk. In object data, metadata also includes the object ID. With block storage (sometimes referred to as virtual storage), metadata is not used for tracking the data, and instead the operating system must track the read/write block unique location identifiers.

Typically, block storage is used where high IO throughput and a low latency network-based storage operation is needed. This might be the case with database servers or business critical software application servers that demand fast, reliable performance. Databases such as Oracle or SAP Hana frequently reside on block level storage. Block storage is also natively supported by VMware virtual machines, as this enables service providers to build fast and versatile virtual infrastructure. Block storage can be used in almost any typical datacenter scenario, whether it be a standard file system for a server or a resilient RAID implementation. The user will need to consider the cost of block level implementation and the performance requirements of any given technical solution, weighing the benefits of block level storage.

Block Storage in the Cloud

Block storage is a very popular service offered by managed service providers. It enables users to have on-demand storage allocated to any cloud instance; in many cases this process takes minutes to complete. This data on demand is protected by high availability and data replication technology, and volumes can be amended by an automated service. Data is secure and encrypted at rest, ensuring that it is impossible for other target servers to access your data. In a cloud scenario, block storage can be an affordable option to extend volume capacity as needed.

Advantages of Block Storage

Block storage is a very popular storage method in the modern data center, says CloudAcademy, thanks to many distinct advantages. Those advantages include:

• Performance – block storage is extremely fast storage and is most frequently used by applications requiring rapid input output operations per seconds (IOPS), such as database servers. This low latency, rapid IO data access is one of the key reasons block storage is so popular.
• Flexibility – data volumes are extremely flexible, volumes can be extended easily with no downtime as your business grows, and new block volumes can be added as needed.
• Agility – another key advantage is that Block Storage can be moved from one server to another server with relative ease. With a simple amendment of the iSCSI target path, the data can be pointed to another server.
• Reduced filesystem overhead – many applications are block storage aware, such as PHP, Apache, Exchange, SharePoint etc. When the software can write direct to the storage blocks, it removes the additional overhead put on the Operating System filesystem read/write activities. This approach almost eliminates IO bottlenecks, as the system does not need to write the data twice.
• Bootable – operating systems can boot direct from block storage presented via storage area networks. All that is needed is a physical or virtual server with a BIOS capable of SAN boot.
• Permissions – access management and data permissions are easy to manage with block storage and can be controlled directly by the storage or the host operating system.ⁱ

Disadvantages of Block Storage

Block storage is not always the perfect storage solution, and it’s important to consider the few drawbacks of using it. The user must determine if the disadvantages overshadow the advantages of block storage.

• Locked to server – the storage block volume is locked to one individual server at a time and cannot be accessed elsewhere in the environment from a different target server. There are some software workarounds to combat this, but this all adds to IO overhead.
• Limited Metadata – the limited amount of information stored in block storage metadata is significantly less than in file or object level storage (more from DigitalOcean). Some applications which rely on detailed metadata may suffer.
• Cost – in cloud scenario, block storage can be an affordable option for many; however, for managed service providers, there is a costly outlay as Storage Attached Networks (SAN) are expensive to buy and often require highly skilled storage subject matter experts to manage the data arrays optimization.

References

ⁱDufrasne, B. (2014). IBM XIV storage system architecture and implementation. [Poughkeepsie, New York]: IBM Corporation, International Technical Support Organization.