卷块存储

There are two ways to create vDisks on Nutanix for your VMs:<\/span><\/p>

1. \t

   Nutanix native vDisks.<\/span><\/p>\t<\/li>\t

2. \t

   Nutanix volume groups.<\/span><\/p>\t<\/li><\/ol>

   Nutanix Native vDisks<\/strong><\/h2>

   The Nutanix native vDisk option simplifies VM administration because it doesn\u2019t require Nutanix VGs. When you create a VM using Prism, add more vDisks to the VM for the application or database the same way you add a vDisk to the VM for the boot disk. If you have an application or database that doesn\u2019t have intensive I\/O requirements, native vDisks are the best option.<\/span><\/p>

   Nutanix Volume Groups<\/strong><\/h2>

   Alternatively, you can attach Nutanix VGs, which are collections of vDisks, to the VMs. VGs enable you to separate the data vDisks from the VM\u2019s boot vDisk. This separation allows you to create a protection domain that consists only of the data vDisks for snapshots and cloning. In addition, VGs let you configure a cluster with shared-disk access across multiple VMs. Supported clustering applications include Oracle Real Application Cluster (RAC), IBM Spectrum Scale (formerly known as GPFS), Veritas InfoScale, and Red Hat Clustering. To attach the VG to multiple VMs when you use the aCLI, create it with a <\/span>shared=true<\/strong> attribute. If you use Prism, answer <\/span>yes<\/strong> when you attach the VG to a second VM. There are two ways to use Nutanix VGs: default VG and VGLB.<\/span><\/p>

   Default Volume Group<\/strong><\/h3>

   This type of VG provides the best data locality because it doesn\u2019t load-balance vDisks in a Nutanix cluster, which means all vDisks in default VGs have a single CVM providing their I\/O. For example, in a four-node Nutanix cluster that includes a VG with eight vDisks attached to a VM, a single CVM owns all the vDisks and all I\/O to the eight vDisks goes through this CVM.<\/span><\/p>

   \u00a0<\/p>","url":"\/volumes-block-storage-171\/configuration-for-volumes-vdisks-40537?postid=60183#post60183","creationDate":"2022-01-20T01:50:53+0000","relativeCreationDate":"9 months ago"},"isTopicUnread":true,"privateId":43017,"id":40537,"type":"post","hasCurrentUserLiked":false,"isSticky":false,"features":[],"forum":{"id":171,"isIdeation":false,"url":"\/volumes-block-storage-171","title":"Volumes Block Storage","description":"Scale-Out Volumes Block Storage Built for the Acropolis OS"},"url":"\/volumes-block-storage-171\/configuration-for-volumes-vdisks-40537","title":"Configuration for Volumes (vDisks)","lastPost":{"id":60183,"author":{"id":49844,"url":"\/members\/raaji-49844","name":"raaji","avatar":"","userTitle":"Nutanix Employee","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"icon":"37a898b2-5836-48f7-8638-a2655ab662a1.png","iconUrl":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/37a898b2-5836-48f7-8638-a2655ab662a1.png","avatarIcon":"7e8707dd-f993-470f-800f-3adc68e91f02_thumb.png","avatarIconUrl":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/7e8707dd-f993-470f-800f-3adc68e91f02_thumb.png","name":"Nutanix Employee","color":"#0873ba"},"userLevel":2},"content":"

   In a traditional three-tier architecture, application and database administrators often work with storage administrators to create a custom storage design to suit their environment, which includes designating the RAID level and block size for different types of files, such as database tablespaces or log files. This process can become cumbersome to manage, especially if there are multiple databases. Nutanix eliminates the problems associated with choosing the optimal RAID and block size. Once you create a VG with the required number of vDisks for your database or application, you\u2019re ready to deploy. The following table outlines the recommended minimum disk layout for a database such as Oracle. For other workloads please refer to the specific application\u2019s best practices guide.<\/span><\/p>

   There are two ways to create vDisks on Nutanix for your VMs:<\/span><\/p>

   1. \t

      Nutanix native vDisks.<\/span><\/p>\t<\/li>\t

   2. \t

      Nutanix volume groups.<\/span><\/p>\t<\/li><\/ol>

      Nutanix Native vDisks<\/strong><\/h2>

      The Nutanix native vDisk option simplifies VM administration because it doesn\u2019t require Nutanix VGs. When you create a VM using Prism, add more vDisks to the VM for the application or database the same way you add a vDisk to the VM for the boot disk. If you have an application or database that doesn\u2019t have intensive I\/O requirements, native vDisks are the best option.<\/span><\/p>

      Nutanix Volume Groups<\/strong><\/h2>

      Alternatively, you can attach Nutanix VGs, which are collections of vDisks, to the VMs. VGs enable you to separate the data vDisks from the VM\u2019s boot vDisk. This separation allows you to create a protection domain that consists only of the data vDisks for snapshots and cloning. In addition, VGs let you configure a cluster with shared-disk access across multiple VMs. Supported clustering applications include Oracle Real Application Cluster (RAC), IBM Spectrum Scale (formerly known as GPFS), Veritas InfoScale, and Red Hat Clustering. To attach the VG to multiple VMs when you use the aCLI, create it with a <\/span>shared=true<\/strong> attribute. If you use Prism, answer <\/span>yes<\/strong> when you attach the VG to a second VM. There are two ways to use Nutanix VGs: default VG and VGLB.<\/span><\/p>

      Default Volume Group<\/strong><\/h3>

      This type of VG provides the best data locality because it doesn\u2019t load-balance vDisks in a Nutanix cluster, which means all vDisks in default VGs have a single CVM providing their I\/O. For example, in a four-node Nutanix cluster that includes a VG with eight vDisks attached to a VM, a single CVM owns all the vDisks and all I\/O to the eight vDisks goes through this CVM.<\/span><\/p>

      \u00a0<\/p>","url":"\/volumes-block-storage-171\/configuration-for-volumes-vdisks-40537?postid=60183#post60183","creationDate":"2022-01-20T01:50:53+0000","relativeCreationDate":"9 months ago"},"numberOfUnreadReplies":0,"numberOfReplies":0,"numberOfLikes":0,"relevantPost":{"id":60183,"author":{"id":49844,"url":"\/members\/raaji-49844","name":"raaji","avatar":"","userTitle":"Nutanix Employee","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"icon":"37a898b2-5836-48f7-8638-a2655ab662a1.png","iconUrl":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/37a898b2-5836-48f7-8638-a2655ab662a1.png","avatarIcon":"7e8707dd-f993-470f-800f-3adc68e91f02_thumb.png","avatarIconUrl":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/7e8707dd-f993-470f-800f-3adc68e91f02_thumb.png","name":"Nutanix Employee","color":"#0873ba"},"userLevel":2},"content":"

      In a traditional three-tier architecture, application and database administrators often work with storage administrators to create a custom storage design to suit their environment, which includes designating the RAID level and block size for different types of files, such as database tablespaces or log files. This process can become cumbersome to manage, especially if there are multiple databases. Nutanix eliminates the problems associated with choosing the optimal RAID and block size. Once you create a VG with the required number of vDisks for your database or application, you\u2019re ready to deploy. The following table outlines the recommended minimum disk layout for a database such as Oracle. For other workloads please refer to the specific application\u2019s best practices guide.<\/span><\/p>

      There are two ways to create vDisks on Nutanix for your VMs:<\/span><\/p>

      1. \t

         Nutanix native vDisks.<\/span><\/p>\t<\/li>\t

      2. \t

         Nutanix volume groups.<\/span><\/p>\t<\/li><\/ol>

         Nutanix Native vDisks<\/strong><\/h2>

         The Nutanix native vDisk option simplifies VM administration because it doesn\u2019t require Nutanix VGs. When you create a VM using Prism, add more vDisks to the VM for the application or database the same way you add a vDisk to the VM for the boot disk. If you have an application or database that doesn\u2019t have intensive I\/O requirements, native vDisks are the best option.<\/span><\/p>

         Nutanix Volume Groups<\/strong><\/h2>

         Alternatively, you can attach Nutanix VGs, which are collections of vDisks, to the VMs. VGs enable you to separate the data vDisks from the VM\u2019s boot vDisk. This separation allows you to create a protection domain that consists only of the data vDisks for snapshots and cloning. In addition, VGs let you configure a cluster with shared-disk access across multiple VMs. Supported clustering applications include Oracle Real Application Cluster (RAC), IBM Spectrum Scale (formerly known as GPFS), Veritas InfoScale, and Red Hat Clustering. To attach the VG to multiple VMs when you use the aCLI, create it with a <\/span>shared=true<\/strong> attribute. If you use Prism, answer <\/span>yes<\/strong> when you attach the VG to a second VM. There are two ways to use Nutanix VGs: default VG and VGLB.<\/span><\/p>

         Default Volume Group<\/strong><\/h3>

         This type of VG provides the best data locality because it doesn\u2019t load-balance vDisks in a Nutanix cluster, which means all vDisks in default VGs have a single CVM providing their I\/O. For example, in a four-node Nutanix cluster that includes a VG with eight vDisks attached to a VM, a single CVM owns all the vDisks and all I\/O to the eight vDisks goes through this CVM.<\/span><\/p>

         \u00a0<\/p>","url":"\/volumes-block-storage-171\/configuration-for-volumes-vdisks-40537?postid=60183#post60183","creationDate":"2022-01-20T01:50:53+0000","relativeCreationDate":"9 months ago"},"numberOfViews":223,"contentType":"discussion","featuredImage":"","publicLabel":"","category":{"url":"\/nutanix-unified-storage-169","categoryId":169,"title":"Nutanix Unified Storage","metaRobots":"index, follow","type":0},"lastPostId":"60183"},"isActivityPage":null,"showUnsubscribeBtn":null,"attachmentCdn":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/","isGuest":true,"csrfToken":"da007134f694601da52b4338b0f5777157691009","hideCategoryMetadata":false,"phrases":{"Forum":{"thread.unsubscribe":"Unsubscribe","vraag":"Question","beantwoord":"Solved","topic.list.metadata.asked.in":"asked in","topic.list.metadata.published.in":"published in","topic.list.metadata.shared.in":"shared in","topic.list.metadata.posted.in":"posted in"}}}">

         r

         

         拉阿吉 Nutanix员工

         发布卷块存储

         卷的配置（VDISKS）

         在传统的三层体系结构中，应用程序和数据库管理员经常与存储管理员合作以创建适合其环境的自定义存储设计，其中包括指定RAID级别和不同类型的文件的块大小，例如数据库表或日志文件。此过程可能会变得笨拙，尤其是在有多个数据库的情况下。Nutanix消除了与选择最佳突袭和块大小相关的问题。一旦创建了带有数据库或应用程序所需数量的VDisk数量的VG，就可以部署。下表概述了诸如Oracle之类的数据库的建议的最小磁盘布局。有关其他工作负载，请参阅特定应用程序的最佳实践指南。有两种在Nutanix上为您的VMS创建VDISK的方法：Nutanix本机Vdisks。Nutanix卷组。nutanix本地vdisks the nutanix本机Vdisk选项简化了VM管理，因为它不需要

         0 0

         r

         

         9个月前