Loading...
Loading...
Consistency Group entered an error state after increased a shared VMDK size, the following error is displayed in RecoverPoint Plugin System Alerts: "There is a mismatch between the actual size and the protected size of the user volume." Note: The Warning states which volumes are affected if you hover the hover over the Description .
Kdriver logs ( /scratch/log/kdriver.log.0000x ): 2023/02/01 05:07:06.425 - #2 - 2099698/2099645 - SplitterController: getHostWarnings: splitter has warnings on site 2340d60313191c68 m_GenericWarningMap = Map([2340d60313191c68 => Vector((genericWarningID=WarnID_SPLITTER,problemSeverity= ProblemSeverity_WARNING ,genericWarningCategory=WarnCategory_SPLITTER,siteUID=NoOption,boxRole=[],hostID=Option(ESX 0x10c71e58f25fe269),globalLinks=[],groupCopies=Vector(),groups=Vector(),links=Vector(), devices=Vector( 0xf0226ebf4afdb37b,0xf1d2c75138b26fcc ),hostVolumes=Vector(),vms=Vector(),arrays=Vector(),contents= There is a mismatch between the actual size and the protected size of the user volume .),(genericWarningID=WarnID_SPLITTER,problemSeverity=ProblemSeverity_WARNING,genericWarningCategory=WarnCategory_SPLITTER,siteUID=NoOption,boxRole=[],hostID=Option(ESX 0x10c71e58f25fe269),globalLinks=[],groupCopies=Vector(),groups=Vector(),links=Vector(), RecoverPoint logs: Control log ( /home/kos/control/result.log.x ): Log collector entry(5744-1): Finished computing HM_hostVolumeStates. ShortTermGoals HM_hostVolumeStates diff from TargetState=[(hostID=ESX 0x10c71e58f25fe269,gUDeviceID=0x21875399cce283fb)=>(state=TRACK-META-DATA(trackingInfo= (trackingReason=TR_UNDEFINED)), reason= CAR_ESX_VOLUME_RESIZED )] Control log ( /home/kos/control/settings_state.log.x ): 0xb5c9592bf3bac380: (siteDeviceName=(gUDeviceID=0xb5c9592bf3bac380,sharedDeviceId=NoOption,sharedDeviceVmGuids=[ 0x21875399cce283fb,0xf0226ebf4afdb37b,0xf1d2c75138b26fcc ], boxRole=KBox1,scsiCommonInfo=id=0xb5c9592bf3bac380,vendor=Virtual,product=VDisk,size=26843545600,vendoreUnique=0xb5c9592bf3bac380, rawGuid=Vector(96,0,194,159,219,114,129,230,167,209,222,80,229,84,111,249),creationID=(creationID=NoOption),name=scsi2:8, arrayID=Option(ARRAY_VC_NAME),maskingGroupUID=NoOption,dataStoreUuid=Option((uuid=datastore-111111)),vMUuid=Option((vcUuid=(uuid=c9de17fe-1111-1111-111-f7f09554e352),uuid=ee866978-4018-a62e-de12-cdd16ff70dc6)), rpvsLunID=NoOption), size= 26843545600 , deviceRoleInfo=volumeType=USER_VOLUME(groupCopyID= GroupCopy(1321230354 SiteUID(0x2340d60313191c68) 0),replicationSetUID= 4409400419568205188))0x21875399cce283fb: (siteDeviceName=(gUDeviceID= 0x21875399cce283fb ,sharedDeviceId=Option( 0xb5c9592bf3bac380 ),sharedDeviceVmGuids=[],boxRole=KBox1,scsiCommonInfo=id=0x21875399cce283fb, vendor=Virtual,product=VDisk,size= 26843545600 ,vendoreUnique=ee866978-4018-a62e-de12-cdd16ff70dc6:scsi2:8, rawGuid=Vector(101,101,56,54,54,57,55,56,45,52,48,49,56,45,97,54,50,101,45,100,101,49,50,45,99,100,100,49,54,102,102,55,48,100,99,54,58,115,99,115,105,50,58,56), NAAGuid=Vector(101,101,56,54,54,57,55,56,45,52,48,49,56,45,97,54,50,101,45,100,101,49,50,45,99,100,100,49,54,102,102,55,48,100,99,54,58,115,99,115,105,50,58,56), creationID=(creationID=NoOption),name=scsi2:8,arrayID=Option(ARRAY_VC_NAME),maskingGroupUID=NoOption,dataStoreUuid=Option((uuid=datastore-111111)), vMUuid=Option((vcUuid=(uuid=c9de17fe-1111-1111-111-f7f09554e352),uuid=ee866978-4018-a62e-de12-cdd16ff70dc6)),rpvsLunID=NoOption), size= 26843545600 , deviceRoleInfo=volumeType=USER_VOLUME(groupCopyID= GroupCopy(1321230354 SiteUID(0x2340d60313191c68) 0),replicationSetUID= 4409400419568205188)) The shared VMDK volume size was increased to 50 GB, but RecoverPoint still sees the old size, which was 25 GB. The process, to increase shared disks protected with RecoverPoint, is different from nonshared disks. In nonshared disks, RecoverPoint detects the size change and replicate those changes to the Replica VM. In shared disks, RecoverPoint cannot replicate those changes to the replica VM, as the shared disks have a special configuration in order to be protected.
Workaround: In order to avoid the issue stated above, use the below procedure to increase shared disks/s size. Access RecoverPoint for Virtual Machines (RecoverPoint for Virtual Machines) Plugin . Select Protected VMs. Find which VM/s have the shared disk/s and press Protection Policy. Clear the shared disk/s to stop the replication and Update Policy . (Has to be done for all the protected VMs sharing the disk being resized.) 5. Disable the Consistency Group (CG) protecting the VMs. 6. Increase shared disk/s size. 7. Return to RecoverPoint for Virtual Machines Plugin under Protected VMs. 8. Find which VM/s have the shared disk/s and press Protection Policy. 9. Enable replication for the shared disk/s you increased the size. 10 Update Policy 11 Enable the CG and wait for INIT process to complete. Resolution: RecoverPoint for Virtual Machines is working by design.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.