Forum Discussion
Solved
Disk size limits for migration
Hi, does Azure Migrate have the same limit on maximum source disk size as ASR for Hyper-V VMs? 4 TB (expected to increase to 8 TB soonish). With ASR, VMware/physical servers can have 8 TB disks, and ...
- For Hyper-V, it's 4 TB data disks today. We are planning to add the support for disks upto 8 TB. You can, however, treat the Hyper-V VMs as physical servers, use agent-based physical server migration method, and migrate to Azure if the disk size is more than 4 TB.
Hello,
This 32 TB Data Disk size limit is for the total allocated disk size OR the used space on a disk?
Our scenario: We have a File Server On-Prem which uses a 40 TB disk attached to a server. It is an HP storage array 40 TB connected to server . Its a smart array controller "12 x 4 TB disk in RAID 5 disk configuration". The used space however on it is ~30 TB. Can we replicate this using Azure Migrate?
If not, what are the other options to migrate this File Server to Azure IaaS solution? (PaaS is not into consideration for my Customer)
Any response is much appreciated.
Thank you
Ravi
This 32 TB Data Disk size limit is for the total allocated disk size OR the used space on a disk?
Our scenario: We have a File Server On-Prem which uses a 40 TB disk attached to a server. It is an HP storage array 40 TB connected to server . Its a smart array controller "12 x 4 TB disk in RAID 5 disk configuration". The used space however on it is ~30 TB. Can we replicate this using Azure Migrate?
If not, what are the other options to migrate this File Server to Azure IaaS solution? (PaaS is not into consideration for my Customer)
Any response is much appreciated.
Thank you
Ravi
Hi Ravi,
32 TB is the disk size. But it's worth checking on limits because they do get increased over time.
30 TB would take a long time to transfer, wouldn't it?
py