- 浏览: 85908 次
- 性别:
- 来自: 广州
文章分类
- 全部博客 (78)
- 生活 (3)
- 云计算与虚拟化 (26)
- IT技术 (13)
- VDI (7)
- WEB 2.0 (3)
- social network (1)
- API (1)
- java (1)
- tools (1)
- javascript (3)
- framework (1)
- web (1)
- virtualization (3)
- hypervisor (1)
- linux (6)
- kvm (1)
- VDI,vmware (2)
- wine (1)
- android (4)
- NoSQL (1)
- version control (1)
- (1)
- xendesktop (1)
- citrix (1)
- mobile (2)
- ebook (1)
- GUI (2)
- C# (1)
- google map (1)
- 围棋 (1)
- coding (1)
- programming (1)
最新评论
选择Block Storage还是NFS?
ISCSI vs. NFS for virtualization shared storage
Nigel Poulton and Scott Lowe, Contributors
E-mail
Print
AAAAAA
LinkedIn
Facebook
Twitter
Share This
Reprints
Among the many decisions IT managers face when deploying server virtualization is what form of shared storage to use: block-based storage such as Fibre Channel and iSCSI, or file-based NFS?
According to storage expert Nigel Poulton, the vast majority of VMware deployments rely on block-based storage, despite usually being more costly than NFS. That is a testament to the performance and reliability that block-based storage provides, especially in mission-critical production environments.
At the same time, influential virtualization experts like Scott Lowe advocate strongly in favor of NFS storage, citing management simplicity, large datastores and the availability of cost-saving features like data deduplication on some NFS arrays.
Read the following columns to help you choose whether to pick block-based Fibre Channel or iSCSI shared storage, or an Ethernet-based NFS array.
Block storage better than NFS for performance, reliability
By Nigel Poulton, Contributor
Should you use block storage or file storage for your VMware environment?
There is never a perfect answer to a question like this. But in many cases the solution can be boiled down a tried-and-tested guideline: If you plan on doing real work with your VMware estate, the answer is block. If you just plan on playing around, the answer is file. Here's why.
Real work vs. playing around
When I say real work, I think of these common terms: production, critical, high-availability, online-trading, high-performance, mission-critical, data center, non-stop, zero-downtime.
On the other hand, playing around refers to anything that is not described by the above terms. For example, playing around might include scenarios like home networks, labs and maybe test and development scenarios where cost is king.
Performance and reliability
It is common for block storage to have its own dedicated high-speed network, giving it naturally superior performance and reliability. Dedicated networks mean predictability, less contention and usually higher throughput. Less
Show Me More
More on Introduction to virtualization and how-tos
Get help from the community
Powered by ITKnowledgeExchange.com
contention reduces the risk of somebody else's network problem becoming your network problem.
Protocol offloads are also a factor in increasing performance. Fibre Channel and iSCSI host bus adapters (HBAs) normally provide protocol offloads. These HBAs perform protocol-related functions faster than the main CPU and also free up CPU resources for other core ESX tasks.
Another factor to note is that VMware has invested heavily in improving and tuning the iSCSI software initiator in vSphere 4.0, hugely enhancing its performance over version V 3.5.
Going with the pros
Away from pure technological superiority, it is probably fair to say that the vast majority of production VMware deployments over the years have been on block storage -- especially Fibre Channel. When it comes to the crunch, that fact should give you the warm fuzzy feeling we all like when doing real work.
To confirm that point, I recently pinged some friends and colleagues who use and deploy VMware day in and day out to ask what they predominantly deploy. Interestingly, all of them deploy VMware on block storage the vast majority of the time!
I also put a quick poll up on my website recently asking the same question. As of Jan. 5, block storage has 72% of the votes, file storage has 10%, with the remaining percentages made up of options such as a mix of block and file.
The bottom line is that the most mature, well-known and trusted configurations are clearly block-based, despite the fact that block-based solutions are usually more expensive than file-based. So if you plan on doing real work with your VMware estate where you need performance, reliability and peace of mind, you should deploy on block storage. Don't be wooed by jazzy features offered by file-based approaches -- you will likely never use them.
Six reasons to use NFS for VM storage
By Scott Lowe
These are six reasons to choose Network File System (NFS) for your virtual machine (VM) storage over traditional block-based storage.
1. Simplified operational model. NFS offers a greatly simplified operational model versus traditional block storage. Resizing LUNs can sometimes be problematic -- both the LUN and the Virtual Machine File System (VMFS) datastore must be resized. Resizing NFS filesystems/exports is generally much easier. VSphere's new VMFS expansion functionality helps, but it's still generally more cumbersome than with NFS. In addition, the use of deduplication functionality (for those arrays that support this functionality) is far simpler and easier to use when used with NFS instead of block-based storage.
2. Larger datastores. While VMFS LUNs top out just shy of 2 TB in size, NFS has no such limits -- some arrays go as high as 16 TB.
3. Ethernet-based network infrastructure. NFS uses the existing Ethernet infrastructure. On the other hand, the same can be said for iSCSI, so that's an even draw between the two protocols.
4. Advanced functionality via filesystems. NFS can offer advanced functionality above what a traditional block device can offer because the storage device has control of the filesystem. Features like snapshots and clones are more widely supported on NFS than on block storage. For example, consider storage devices like the Sun Storage 7000 or the NetApp FAS, both of which offer nearly instantaneous snapshot functionality and space-conserved clones.
5. Open access. VMware designed VMFS from the ground up to support virtualized environments, but that makes VMFS a bit specific to VMware environments.This means that it can be difficult to gain access to VMFS datastores. NFS, on the other hand, is a mature cross-platform specification that makes it much easier to provide access to virtual machines for backup, replication or other purposes.
6. A bright future. A significant part of NFS' future lies in parallel NFS (pNFS), which provides a standard for scale-out storage involving multiple storage controllers (NAS heads) and multiple volumes. It's expected that pNFS will bring performance and throughput benefits to a wide variety of workloads, including virtualization.
ISCSI vs. NFS for virtualization shared storage
Nigel Poulton and Scott Lowe, Contributors
AAAAAA
Share This
Reprints
Among the many decisions IT managers face when deploying server virtualization is what form of shared storage to use: block-based storage such as Fibre Channel and iSCSI, or file-based NFS?
According to storage expert Nigel Poulton, the vast majority of VMware deployments rely on block-based storage, despite usually being more costly than NFS. That is a testament to the performance and reliability that block-based storage provides, especially in mission-critical production environments.
At the same time, influential virtualization experts like Scott Lowe advocate strongly in favor of NFS storage, citing management simplicity, large datastores and the availability of cost-saving features like data deduplication on some NFS arrays.
Read the following columns to help you choose whether to pick block-based Fibre Channel or iSCSI shared storage, or an Ethernet-based NFS array.
Block storage better than NFS for performance, reliability
By Nigel Poulton, Contributor
Should you use block storage or file storage for your VMware environment?
There is never a perfect answer to a question like this. But in many cases the solution can be boiled down a tried-and-tested guideline: If you plan on doing real work with your VMware estate, the answer is block. If you just plan on playing around, the answer is file. Here's why.
Real work vs. playing around
When I say real work, I think of these common terms: production, critical, high-availability, online-trading, high-performance, mission-critical, data center, non-stop, zero-downtime.
On the other hand, playing around refers to anything that is not described by the above terms. For example, playing around might include scenarios like home networks, labs and maybe test and development scenarios where cost is king.
Performance and reliability
It is common for block storage to have its own dedicated high-speed network, giving it naturally superior performance and reliability. Dedicated networks mean predictability, less contention and usually higher throughput. Less
Show Me More
More on Introduction to virtualization and how-tos
Get help from the community
Powered by ITKnowledgeExchange.com
contention reduces the risk of somebody else's network problem becoming your network problem.
Protocol offloads are also a factor in increasing performance. Fibre Channel and iSCSI host bus adapters (HBAs) normally provide protocol offloads. These HBAs perform protocol-related functions faster than the main CPU and also free up CPU resources for other core ESX tasks.
Another factor to note is that VMware has invested heavily in improving and tuning the iSCSI software initiator in vSphere 4.0, hugely enhancing its performance over version V 3.5.
Going with the pros
Away from pure technological superiority, it is probably fair to say that the vast majority of production VMware deployments over the years have been on block storage -- especially Fibre Channel. When it comes to the crunch, that fact should give you the warm fuzzy feeling we all like when doing real work.
To confirm that point, I recently pinged some friends and colleagues who use and deploy VMware day in and day out to ask what they predominantly deploy. Interestingly, all of them deploy VMware on block storage the vast majority of the time!
I also put a quick poll up on my website recently asking the same question. As of Jan. 5, block storage has 72% of the votes, file storage has 10%, with the remaining percentages made up of options such as a mix of block and file.
The bottom line is that the most mature, well-known and trusted configurations are clearly block-based, despite the fact that block-based solutions are usually more expensive than file-based. So if you plan on doing real work with your VMware estate where you need performance, reliability and peace of mind, you should deploy on block storage. Don't be wooed by jazzy features offered by file-based approaches -- you will likely never use them.
Six reasons to use NFS for VM storage
By Scott Lowe
These are six reasons to choose Network File System (NFS) for your virtual machine (VM) storage over traditional block-based storage.
1. Simplified operational model. NFS offers a greatly simplified operational model versus traditional block storage. Resizing LUNs can sometimes be problematic -- both the LUN and the Virtual Machine File System (VMFS) datastore must be resized. Resizing NFS filesystems/exports is generally much easier. VSphere's new VMFS expansion functionality helps, but it's still generally more cumbersome than with NFS. In addition, the use of deduplication functionality (for those arrays that support this functionality) is far simpler and easier to use when used with NFS instead of block-based storage.
2. Larger datastores. While VMFS LUNs top out just shy of 2 TB in size, NFS has no such limits -- some arrays go as high as 16 TB.
3. Ethernet-based network infrastructure. NFS uses the existing Ethernet infrastructure. On the other hand, the same can be said for iSCSI, so that's an even draw between the two protocols.
4. Advanced functionality via filesystems. NFS can offer advanced functionality above what a traditional block device can offer because the storage device has control of the filesystem. Features like snapshots and clones are more widely supported on NFS than on block storage. For example, consider storage devices like the Sun Storage 7000 or the NetApp FAS, both of which offer nearly instantaneous snapshot functionality and space-conserved clones.
5. Open access. VMware designed VMFS from the ground up to support virtualized environments, but that makes VMFS a bit specific to VMware environments.This means that it can be difficult to gain access to VMFS datastores. NFS, on the other hand, is a mature cross-platform specification that makes it much easier to provide access to virtual machines for backup, replication or other purposes.
6. A bright future. A significant part of NFS' future lies in parallel NFS (pNFS), which provides a standard for scale-out storage involving multiple storage controllers (NAS heads) and multiple volumes. It's expected that pNFS will bring performance and throughput benefits to a wide variety of workloads, including virtualization.
发表评论
-
转:基于 SAN 环境使用 VMControl 2.4 部署虚拟机
2012-05-02 11:17 1655基于 SAN 环境使用 VMControl 2.4 部署 ... -
转:使用 TSAM 扩展来管理 J2EE 应用程序
2012-05-02 11:16 931使用 TSAM 扩展来管理 J2EE 应用程序 ... -
转:将单租户应用程序转换为多租户应用程序
2012-04-17 18:15 1198将单租户应用程序转换 ... -
转:深入浅出桌面虚拟化存储性能的评估
2012-04-10 10:03 1241深入浅出桌面虚拟化存 ... -
Linux虚拟化信息源
2011-10-18 15:06 794The virtualization API QEMU Em ... -
转:通向私有云的实践之旅
2011-10-18 14:14 1286通向私有云的实践之旅,第 1 部分: 概念准备 通向私有云的 ... -
转:KVM: 安装Windows virtio半虚拟化驱动
2011-10-18 13:07 2195KVM: 安装Windows virtio半虚拟化驱动 In ... -
转:实战 IBM BigInsights,轻松实现 Hadoop 的部署与管理
2011-09-21 14:23 1879实战 IBM BigInsights,轻松实现 Hadoop ... -
转:Windows and GPT FAQ
2011-09-19 19:22 1147Windows and GPT FAQ Windows an ... -
转:Using KVM virtualization in the enterprise: RHEV or RHEL?
2011-09-19 19:19 998Using KVM virtualization in the ... -
转:使用 Node.js 作为完整的云环境开发堆栈
2011-09-12 23:40 1000使用 Node.js 作为完整的 ... -
转:一种开放的可互操作的云
2011-09-11 15:25 838一种开放的可互操作的 ... -
转:Warning: Not all cloud licensing models are user-friendly
2011-09-05 21:57 821Warning: Not all cloud licensin ... -
转:操作系统虚拟化之KVM
2011-08-19 10:22 1119操作系统虚拟化之KVM KVM(Kernel-based V ... -
转:选择云服务:货比三家
2011-08-18 15:09 1003选择云服务:货比三家 20 ... -
转:推动云计算标准化的十大组织
2011-08-18 11:17 547推动云计算标准化的十大组织 推动云计算标准化的十大组织 20 ... -
转:云计算合同中需要注意的十大关键条款
2011-08-18 10:16 543云计算合同中需要注意的十大关键条款 2011-8-16 ... -
转:分布式系统领域经典论文翻译集
2011-08-15 12:26 887分布式系统领域经典论文翻译集 分布式系统领域经典论文翻译集 ... -
IBM desktop cloud
2011-07-08 21:43 719Solutions for Smart Business - ... -
威客云
2011-07-08 21:42 5威客云 苏州威客云终端技术有限公司(简称威客云)成立于201 ...
相关推荐
存储虚拟化解决方案HP存储虚拟化和整合解决方案\HP存储虚拟化和整合解决方案.ppt存储虚拟化解决方案HP存储虚拟化和整合解决方案\HP存储虚拟化和整合解决方案.ppt存储虚拟化解决方案HP存储虚拟化和整合解决方案\HP...
FusionSphere虚拟化套件存储虚拟化技术白皮书.pdf
讲述了IBM详细的存储虚拟化方面的解决方案,对于不懂虚拟化或者说存储方面的新人很有用。
存储整合虚拟化及备份解决方案 某证券公司存储虚拟化项目解决方案 异构存储整合方案 中小企业存储系统解决方案
存储虚拟化的对象有多种:包括块虚拟化、磁盘虚拟化、磁带/磁带机虚拟化文件系统虚拟化以及文件/记录虚拟化等。
转自tt存储存储技术手册之存储虚拟化宝典,非常不错的虚拟化材料
VMware虚拟化架构存储LUN复制以及挂载镜像LUN的步骤.pdf
2.2存储虚拟化 2.3网络虚拟化 2.4主流虚拟化技术 实验1 初识虚拟化、绘制主流虚拟化系统架构图 第3章 VMware ESXi技术 3.1 VMware ESXi概述 3.2 VMware ESXi控制台 3.3 VMware ESXi重要功能 3.4 VMware ESX与Vmware ...
云计算虚拟化技术 存储虚拟化技术,云计算虚拟化入门指导
存储虚拟化(Storage Virtualization)最通俗的理解就是对存储硬件 资源进行抽象化表现。通过将一个(或多个)目标(Target)服务或 功能与其它附加的功能集成,统一提供有用的全面功能服务。典型的 虚拟化包括如下...
1、什么是存储虚拟化 2、为什么要存储虚拟化 3、存储虚拟化实现模式 4、存储虚拟化的应用难点
iSCSI 是一种灵活且强大的存储区域网络(SAN)协议,可为各种规模的企业...各种规模的企业都在使用 iSCSI 和高级虚拟化技术构建灵活的存储基础架构,从而动态地分配和转移 SAN 资源来响应其虚拟化服务器环境的需求。
EMC存储虚拟化策略 中文PPT 不错哦
Agenda • 服务器虚拟化 • 桌面虚拟化 • Ops center管理工具 • 存储虚拟化 • 网络虚拟化 • Q/A
存储_虚拟化_SDS_软件定义存储
存储与虚拟化技术,包括安装exsi,vcenter 创建虚拟机,vsphere的操作等等(学校课件)
存储虚拟化(StorageVirtualization)最通俗的理解就是对存储硬件资源进行抽象化表现。典型的虚拟化包括如下一些情况:屏蔽系统的复杂性,增加或集成新的功能,仿真、整合或分解现有的服务功能等。虚拟化是作用在一个...
详细的介绍美国飞康软件公司对于虚拟化存储的理解,并且其相应产品的虚拟化功能!
虚拟化云计算对存储的要求pptx,提供“虚拟化云计算对存储的要求”免费资料下载,主要包括数据中心演进过程对IT架构要求、虚拟化水平提高对存储需求、HP融合存储在数据中心演进过程应用解析等内容,可供学习使用。
中小企业备份存储解决方案.pdf 中小企业存储系统解决方案.pdf 存储整合虚拟化及备份解决方案.pdf 异构存储整合方案.pdf 某证券公司存储虚拟化项目解决方案.pdf 网络存储解决方案.pdf