Azure Stack Hub 存储容量规划Azure Stack Hub storage capacity planning

以下部分提供 Azure Stack Hub 存储容量规划信息,帮助你针对解决方案的存储需求进行规划。The following sections provide Azure Stack Hub storage capacity planning information to assist in planning for the solution's storage needs.

存储容量的使用和组织Uses and organization of storage capacity

Azure Stack Hub 的超融合配置允许共享物理存储设备。The hyperconverged configuration of Azure Stack Hub allows for the sharing of physical storage devices. 可共享的可用存储的三个主要部分包括:基础结构存储、租户虚拟机 (VM) 的临时存储,以及为 Azure 一致存储 (ACS) 服务的 Blob、表和队列提供支持的存储。There are three main divisions of the available storage that can be shared: the infrastructure, the temporary storage of the tenant virtual machines (VMs), and the storage backing the blobs, tables, and queues of the Azure Consistent Storage (ACS) services.

存储空间直通缓存和容量层Storage Spaces Direct cache and capacity tiers

存储容量可以用于操作系统、本地日志记录、转储和其他临时基础结构存储需求。There's storage capacity used for the operating system, local logging, dumps, and other temporary infrastructure storage needs. 此本地存储容量独立于受存储空间直通配置管理的存储设备(设备和容量独立)。This local storage capacity is separate (devices and capacity) from the storage devices brought under management of the Storage Spaces Direct configuration. 其余存储设备置于单个存储容量池中,不管在缩放单元中的服务器数量为多少。The rest of the storage devices are placed in a single pool of storage capacity, regardless of the number of servers in the scale unit.

这些设备分为两种类型:缓存设备和容量设备。These devices are of two types: cache and capacity. 存储空间直通使用缓存设备来写回和读取缓存。Storage Spaces Direct consumes cache devices for write-back and read caching. 这些缓存设备的容量在使用时,并不局限于已格式化虚拟磁盘的格式化“可见”容量。The capacities of these cache devices, while used, aren't committed to the formatted and "visible" capacity of the formatted virtual disks. 相比之下,存储空间直通使用容量设备来实现此目的,并提供托管数据的“主位置”。By contrast, Storage Spaces Direct does use capacity devices for this purpose, providing the "home location" of the managed data.

Azure Stack Hub 基础结构直接分配和管理所有存储容量。The Azure Stack Hub infrastructure directly allocates and manages all storage capacity. 操作人员无需在配置、分配和容量扩展方面做出选择。The operator doesn't need to make choices about configuration, allocation, capacity expansion. Azure Stack Hub 在初始安装和部署期间或容量扩展期间会自动完成这些设计决策,以符合解决方案要求。Azure Stack Hub automates these design decisions to align with the solution requirements, during either the initial installation and deployment or capacity expansion. 在设计过程中,Azure Stack Hub 会考虑到复原能力、用于重新生成的预留容量和其他详细信息。Azure Stack Hub takes into consideration resiliency, reserved capacity for rebuilds, and other details, as part of the design.

操作员可以选择进行全闪存或混合存储配置 :Operators can choose between either an all flash or a hybrid storage configuration:

Azure 存储容量规划示意图

在全闪存配置中,配置可以是双层配置,也可以是单层配置。In the all flash configuration, the configuration can be either a two-tier or a single-tier configuration. 如果配置是单层配置,则所有容量设备将是相同类型(例如 NVMeSATA SSDSAS SSD),并且不使用缓存设备。If the configuration is single-tier, all capacity devices are of the same type (for example, NVMe or SATA SSD or SAS SSD), and cache devices aren't used. 在双层全闪存配置中,典型配置是 NVMe 作为缓存设备,然后 SATA 或 SAS SSD 作为容量设备。In a two-tier all flash configuration, the typical configuration is NVMe as the cache devices, and then either SATA or SAS SSDs as the capacity devices.

在混合双层配置中,缓存可在 NVMe、SATA 或 SAS SSD 之间进行选择,而容量则为 HDD。In the hybrid two-tier configuration, the cache is a choice among NVMe, SATA, or SAS SSD, and the capacity is HDD.

存储空间直通和 Azure Stack Hub 存储配置概述如下:A brief summary of the Storage Spaces Direct and Azure Stack Hub storage configuration is as follows:

  • 每个缩放单元有一个存储存储空间池(所有存储设备在单个池中配置)。One Storage Spaces Direct pool per scale unit (all storage devices are configured within a single pool).
  • 虚拟磁盘创建为三副本镜像,以确保最佳性能和复原能力。Virtual disks are created as a three-copy mirror for best performance and resiliency.
  • 每个虚拟磁盘格式化为一个 ReFS 文件系统。Each virtual disk is formatted as an ReFS file system.
  • 在对虚拟磁盘容量进行计算和分配时,会将池中一个容量设备的数据容量保持取消分配状态。Virtual disk capacity is calculated and allocated in a way as to leave one capacity device's amount of data capacity unallocated in the pool. 这相当于一个服务器一个容量驱动器。This is the equivalent of one capacity drive per server.
  • 每个 ReFS 文件系统都会启用 BitLocker 进行静态数据加密。Each ReFS file system has BitLocker enabled for data-at-rest encryption.

虚拟磁盘自动创建,其容量如下所示:The virtual disks created automatically and their capacities are as follows:

名称Name 容量计算Capacity calculation 说明Description
本地/启动设备Local/boot device 至少 340 GB1Minimum of 340 GB1 用于操作系统映像和“本地”基础结构 VM 的单个服务器存储。Individual server storage for operating system images and "local" infrastructure VMs.
基础结构Infrastructure 3.5 TB3.5 TB 所有 Azure Stack Hub 基础结构使用量。All Azure Stack Hub infrastructure usage.
VmTempVmTemp 见下2See below2 租户 VM 附加了一个临时磁盘,该数据存储在这些虚拟磁盘中。Tenant VMs have a temporary disk attached and that data is stored in these virtual disks.
ACSACS 见下3See below 3 Azure 一致存储容量,为 Blob、表和队列提供服务。Azure Consistent Storage capacity for servicing blobs, tables, and queues.

1 对 Azure Stack Hub 解决方案合作伙伴有最低存储容量要求。1 Minimum storage capacity required of the Azure Stack Hub solution partner.

2 用于租户 VM 临时磁盘的虚拟磁盘大小按服务器中物理内存的比率进行计算。2 The virtual disk size used for tenant VM temporary disks is calculated as a ratio of the physical memory of the server. 临时磁盘是分配给 VM 的物理内存比率。The temporary disk is a ratio of the physical memory assigned to the VM. 在 Azure Stack Hub 中为“临时磁盘”存储进行分配时,会采用能够捕获大多数用例的方式,但这种方式可能无法满足所有临时磁盘存储需求。The allocation done for "temp disk" storage in Azure Stack Hub captures most use cases but might not be able to satisfy all temp disk storage needs. 该比率既要让临时存储可用,又要确保不将解决方案的大多数存储容量仅用于临时磁盘容量。The ratio is a trade-off between making temporary storage available and not consuming a majority of the solution's storage capacity for temp disk capacity only. 在缩放单元中,将为一个服务器创建一个临时存储磁盘。One temporary storage disk is created per server in the scale unit. 在缩放单元的存储池中,临时存储的容量不会超出总体可用存储容量的 10%。The capacity of the temporary storage doesn't grow beyond 10 percent of the overall available storage capacity in the storage pool of the scale unit. 计算如以下示例所示:The calculation is something like the following example:

  DesiredTempStoragePerServer = PhysicalMemory * 0.65 * 8
  TempStoragePerSolution = DesiredTempStoragePerServer * NumberOfServers
  PercentOfTotalCapacity = TempStoragePerSolution / TotalAvailableCapacity
  If (PercentOfTotalCapacity <= 0.1)
      TempVirtualDiskSize = DesiredTempStoragePerServer
  Else
      TempVirtualDiskSize = (TotalAvailableCapacity * 0.1) / NumberOfServers

3 创建的供 ACS 使用的虚拟磁盘对剩余容量进行了简单的划分。3 The virtual disks created for use by ACS are a simple division of the remaining capacity. 如前所述,所有虚拟磁盘都是一个三向镜像,每个服务器的一个容量驱动器的容量值是未分配的。As noted, all virtual disks are a three-way mirror and one capacity drive's worth of capacity for each server is unallocated. 上面列举的各种虚拟磁盘会先进行分配,剩余容量随后用于 ACS 虚拟磁盘。The various virtual disks previously enumerated are allocated first and the remaining capacity is then used for the ACS virtual disks.

后续步骤Next steps

了解 Azure Stack Hub Capacity PlannerLearn about the Azure Stack Hub Capacity Planner.