ASR支持超过4095GB大小的磁盘 [英] ASR support for disks over 4095GB Size

问题描述

您好，

我们正在使用ASR将混合的v-v guest虚拟机和物理机迁移到Azure。我们的机器和虚拟机超过了ASR支持的4095GB大小。 

微软建议迁移这些机器是什么？

---

TIA TP

解决方案

嗨 - 好奇，大小每个VM的数据磁盘和操作系统磁盘，你有，请再分享一次。您提到的大小是VM大小或每个磁盘大小。

您可以随时查找各种大小，并且它不像Azure支持的，它总是感觉很好，你的计划方式并根据您从Azure获得的丰富资源和选项为您设计解决方案。您可能需要将VM大小隔离到关键的
中低级别VM中，并相应地计划一些波动以进入Azure。 Azure是您的自然选择，因为大多数具有丰富人员的办公工具大多是MS工具，它们是  Azure上非常支持。

对于大小超过4095GM的VM， 您可能希望重新设计适合其需要的应用或工具，因为此尺寸您也需要大量的IOPS，

请从以下网址查看以下详细信息：

VM兼容性：表示给定VM与Site Recovery不兼容的原因。针对VM的每个不兼容磁盘描述了原因，并根据已发布的存储
限制，可以是以下任何一种：

• 
  < p style ="">磁盘大小> 4095 GB。 Azure存储目前不支持大于4095 GB的数据磁盘大小。
  
  
• 
  

  操作系统磁盘大于2048 GB。 Azure存储当前不支持大于2048 GB的操作系统磁盘大小。

  
  
• 
  

  总VM大小（复制+ TFO）超出了支持的存储帐户大小限制（35 TB）。当VM中的单个磁盘的性能特征超过标准存储的最大支持Azure或Site Recovery
  限制时，通常会发生此不兼容性。这样的实例将VM推入高级存储区域。但是，高级存储帐户的最大支持大小为35 TB，并且无法跨多个存储帐户保护单个受保护的VM。另请注意
  ，当在受保护的VM上执行测试故障转移时，它会在复制正在进行的同一存储帐户中运行。在这种情况下，设置磁盘大小的2倍以进行复制以进行复制并测试故障转移并行成功。

  
  
• 
  

  源IOPS超过每个磁盘支持的存储IOPS限制7500。

  
  
• 
  

  源IOPS超过每个VM支持的存储IOPS限制80,000。

  
  
• 
  

  平均数据流失超过了磁盘平均I / O大小支持的Site Recovery数据流失限制10 MB / s。

  
  
• 
  

  平均数据流失超过支持的Site Recovery数据流失限制25 MB / s表示VM的平均I / O大小（所有磁盘流失的总和）。

  
  
• 
  

  VM上所有磁盘的峰值数据流失超过了最大值移植Site Recovery峰值数据流失限制为每个VM 54 MB / s。

  
  
• 
  

  平均有效写入IOPS超出磁盘支持的Site Recovery IOPS限制840.

  
  



计算的快照存储超出了支持的10 TB的快照存储限制。



• 
  

  每天的总数据流失超过了Process Server每天支持的2 TB流失限制。

  
  

https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-deployment-planner-analyze-report

Hello,

We are in the process of migrating a mix of hyper-v guest and physical machines to Azure using ASR. We have machines and VMs that are over the the ASR supported size of 4095GB. 

What is Microsoft recommendation to migrate such machines?

---

TIA TP

解决方案

Hi - Just curious, what size of data disk and os disk per VM, you have, please share one more time. Size you have mentioned is VM size or each disk size.

There are various size you can always look for, and its not like what Azure supports, its always feeling good, on how you plan and designed you solution from rich resources and options you have got from Azure. You might need to segregate VM size into critical, medium and low category of VM and plan accordingly with some waves to move into Azure. Azure is your natural choice as most of the office tools with rich guys are mostly MS tools which are  very much supported on Azure.

For VM which sizes are more than 4095GM,  you may like to look for redesign that app or tool to suits it needs, as with this size you need lot of IOPS too, 

Please check below details from URL:

VM Compatibility: Indicates why the given VM is incompatible for use with Site Recovery. The reasons are described for each incompatible disk of the VM and, based on published storage limits, can be any of the following:

• Disk size is >4095 GB. Azure Storage currently does not support data disk sizes greater than 4095 GB.

• OS disk is >2048 GB. Azure Storage currently does not support OS disk size greater than 2048 GB.

• Total VM size (replication + TFO) exceeds the supported storage-account size limit (35 TB). This incompatibility usually occurs when a single disk in the VM has a performance characteristic that exceeds the maximum supported Azure or Site Recovery limits for standard storage. Such an instance pushes the VM into the premium storage zone. However, the maximum supported size of a premium storage account is 35 TB, and a single protected VM cannot be protected across multiple storage accounts. Also note that when a test failover is executed on a protected VM, it runs in the same storage account where replication is progressing. In this instance, set up 2x the size of the disk for replication to progress and test failover to succeed in parallel.

• Source IOPS exceeds supported storage IOPS limit of 7500 per disk.

• Source IOPS exceeds supported storage IOPS limit of 80,000 per VM.

• Average data churn exceeds supported Site Recovery data churn limit of 10 MB/s for average I/O size for the disk.

• Average data churn exceeds supported Site Recovery data churn limit of 25 MB/s for average I/O size for the VM (sum of all disks churn).

• Peak data churn across all disks on the VM exceeds the maximum supported Site Recovery peak data churn limit of 54 MB/s per VM.

• Average effective write IOPS exceeds the supported Site Recovery IOPS limit of 840 for disk.

• Calculated snapshot storage exceeds the supported snapshot storage limit of 10 TB.

• Total data churn per day exceeds supported churn per day limit of 2 TB by a Process Server.

https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-vmware-deployment-planner-analyze-report

这篇关于ASR支持超过4095GB大小的磁盘的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！