Backup fails with "The partition size is incorrect, please shrink the volume." when adding a Linux VM to agentless protection (VMware) (4375438)

The backups of Linux VMWare VMs protected via Agentless fail with the error: 

The partition size is incorrect. Please shrink the volume.

As noted in Knowledge Article 4033908, increasing the virtual disk size by 1 or 2 GB does not fix the issue in this case; the error still happens. 
 

The issue has been identified as defect RR-111487. The defect will be evaluated by our Product Team for inclusion in a future release of Rapid Recovery.
 
A list of "Resolved Issues" is published in the product Release Notes accompanying new releases that can be referenced to identify if a fix for this defect has been implemented. Product Release Notes are available in the "Release Notes and Guides” area of our Support Portal at quest.com/support.
 
For more information on our Product Enhancements and Defects policy, see details published in our Global Support Guide available on the Support Portal.

Please go ahead and apply the patch that corresponds to your Rapid Recovery version.

Available Patches

Installation Instructions

For Versions 6.6.0.268, 6.9.x, and 6.10.0.316

These patches are .msi installers and can be applied as follows:

1. Stop the Rapid Recovery Core service.
2. Run the downloaded .msi file.
3. Wait for the installation to complete.
4. Start the Rapid Recovery Core service.
5. Reattempt the agentless protection process for the Linux VM.

For Version 6.8.0.402

This version does not use a .msi installer. You must manually replace a DLL file.

1. Stop the Rapid Recovery Core service.
2. Download the patched Core.Implementation.dll.
3. Navigate to:
   C:\Program Files\AppRecovery\Core\CoreService\
4. Back up the original Core.Implementation.dll.
5. Replace it with the downloaded file.
6. Start the Rapid Recovery Core service.
7. Retry the agentless protection process.

Additional Information

• This issue is limited to agentless protection of Linux VMs in VMware environments.
• There is no patch available for version 6.7.x. Customers using version 6.7 must upgrade to a supported version to resolve the issue.