Return
-
Title
There is no ability to perform the export to Azure with the vhdx larger than 1023 GB -
Description
Steps to reproduce:
Perform the export to Azure with the VHDX larger than 1023Gb.
Actual result: pop-up window appear with the notification that export of the VHDX larger than 1023 GB is not allowed.
Stack Trace message:
Replay.Core.Contracts.Export.ExportException depth 0: Due to Windows Azure restrictions it is not possible to create VHD disks larger than 1023 GB. The exported machine contains disks that exceed this limitations: E:\ (3.64 TB),D:\ (1.09 TB) (0x80131500)
at Replay.Core.Implementation.Export.Validation.WindowsAzure.WindowsAzureDiskSizeValidator.Validate() +0xb3 600129b
at Replay.Core.Contracts.Validation.ValidatorBase.AggregateValidator.Validate() +0x1b 60038dc
at Replay.Core.Implementation.Export.ExportSchedulerService.ValidateMachineSettings(RecoveryPointExportInfo recoveryPointExportInfo) +0x80 6001d65
-
Cause
Starting on June 15th, 2017 Microsoft Azure has increased the maximum size limit of the virtual hard disks(VHDX) for IaaS VMs, and as a consequence they now allow to perform the export of the VHDX of up to 4TB. The Core should also support such configuration.
To provide flexibility for customers to provision an appropriate disk size which matches their workloads, we introduce two new disk sizes in P40 (2TB) and P50 (4TB) for both Managed and unmanaged Premium Disks; S40 (2TB) and S50 (4TB) for Standard Managed Disks. Customers can also provision the maximum disk size of 4,095 GB for Standard unmanaged disks.
For more details, please review Microsoft's article Announcing large disk sizes of up to 4 TB for Azure IaaS VMs.
-
Resolution
This issue have been identified as RR-105291. Our development team has created a patch to permanently fix this problem. Please open a case with technical support to retrieve this patch.
Development is working on a permanent solution to be included in a future release.
-
Defect ID
RR-105291