The initial placeholder disk size doesn't account for excluded disks for on-premises to cloud replications in VMware Cloud Director Availability 4.x
search cancel

The initial placeholder disk size doesn't account for excluded disks for on-premises to cloud replications in VMware Cloud Director Availability 4.x

book

Article ID: 315164

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:

  • When configuring an on-premises to cloud replication using the exclude disks option, Cloud Director Availability creates an independent placeholder disk in vCloud Director with a provisioned size equal to the sum of all the disks on the source VM.
  • If the size of the full source VM is greater than the free space on the Organization VDC Storage Policy, then configuring the replication fails and you see a similar error:
The requested operation will exceed the VDC's storage quota: storage policy "High_Performance" has 173,886 MB remaining, requested 559,104 MB
  • In /opt/vmware/h4/cloud/log/cloud.log on the Cloud Replication Management Appliance, you see entries similar to:
2020-07-27 17:17:14.939 DEBUG - [UI-b557d921-####-####-####-########dd9-cD] [job-66] c.vmware.h4.cloud.job.VmReplicationJob   : Starting replication for CloudReplicationSettings{source=VcSourceVm{site='On-prem', vcUuid='cb8bf038-####-####-####-########8e3', vmId='vm-202', excludedDisks=[2001]}, destination=VcloudDestination{site='Cloud', vdc=a751b7b9-####-####-####-########1d9, storageProfile='c2e650d9-####-####-####-########fd3'}, description='Protected via VCAV UI', rpo=120, dataConnectionType=ENCRYPTED_COMPRESSED, quiesced=false, retentionPolicy=RetentionPolicy{rules=[RetentionRule [numberOfInstances=7, distance=1440]]}, targetDiskType=THIN, initialSyncTime=0, isMigration=false, slaProfileId='silver'}
...
2020-07-27 17:17:15.948 DEBUG - [UI-b557d921-####-####-####-########dd9-cD] [job-66] c.vmware.h4.cloud.job.VmReplicationJob   : sourceVmDetails SourceVmDetails{sourceInfo=VmSourceInfo{vappName='Test_Quota', site='On-prem', org='null', vdcId=null, vdcName='null', vappId='Test_Quota'} SourceInfo{site='On-prem', org='null', vdcId='null', vdcName='null', vappId='Test_Quota'}, vappDescriptor=VappDescriptor{name='Test_Quota', description='null', metadata={}, networks=[]}, sourceVmInfo=SourceVmInfo{computerName='null', vappId='null', vappName='null', vcId='cb8bf038-####-####-####-########8e3', vmId='vm-202', vmName='Test_Quota', vmDescription='null', hwVersion=13}, vmStartupInfo=VmStartupInfo{order=0, startAction='powerOn', startDelay=0, stopAction='powerOff', stopDelay=0}, vmMetadata={}, diskIds=[6000c29c-####-####-####-########7e3, 6000c299-####-####-####-########b9a], diskSize=586263035904, hwVersion=13, primaryNicIndex=null, nics=null, disks=[DiskInfo [diskKey=2000, capacity=42949672960, diskType=preallocated, diskName=Test_Quota.vmdk, uuid=6000c299-####-####-####-########b9a], DiskInfo [diskKey=2001, capacity=543313362944, diskType=preallocated, diskName=Test_Quota_1.vmdk, uuid=6000c29c-####-####-####-########7e3]]}
...
2020-07-27 17:17:16.030 DEBUG - [UI-b557d921-####-####-####-########dd9-cD] [job-66] c.v.h.c.s.DatastoreManagementService     : Creating independent disk with name C4-eb22349f-####-####-####-########1c1, description 1b99ef06-####-####-####-########39f and size 586263035904
...
2020-07-27 17:17:16.198 ERROR - [UI-b557d921-####-####-####-########dd9-cD] [job-66] com.vmware.h4.jobengine.JobExecution : Task d334dbb0-####-####-####-########b09 (WorkflowInfo{type='start', resourceType='vmReplication', resourceId='C4-eb22349f-####-####-####-########1c1', isPrivate=false, resourceName='null'}) has failed
com.vmware.vcloud.client.exception.VcloudException: (Major code = 400, minor code = STORAGE_QUOTA_EXCEEDED) - [ UI-b557d921-####-####-####-########dd9-cD-0abbcb0f-####-####-####-########a5d ] *The requested operation will exceed the VDC's storage quota: storage policy "High_Performance" has 173,886 MB remaining, requested 559,104 MB*


Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCloud Availability 3.0.x
VMware Cloud Director Availability 4.x
VMware vCloud Availability 3.5.x

Cause

This issue occurs because the reservation calculation uses all of the source disks to determine the initial provisioned size of the independent placeholder disk for on-premises to cloud replications when details about the source VM are being generated.

Resolution

This is a known issue affecting vCloud Availability 3.x and VMware Cloud Director Availability 4.x.

Currently, there is no resolution.