Avamar: /tmp/vmdk_ may be left on proxy /tmp filesystem

When running the command df -h you can see the proxy's root partition is out of space:



When viewing the /tmp on the proxy there are multiple vmdk* files:

When a backup is performed with the index or exclude feature enabled the proxy connects to the vm using vixMntAPI and copies the windows registry file to /tmp/vmdk_####,

[VcbImageBackupAssistThread]  HLPR_IsfileExist::sLine = 83623936 Apr  4 00:26 2017 SYSTEM2022/11/23-19:03:27.52207 [VcbImageBackupAssistThread]  HLPR_SaveFileInVMDKToTmp::command line :  /usr/local/bin/ntfscat /dev/loop1 Windows/System32/config/SYSTEM > /tmp/vmdk_jQHnvy

If there is problem opening or reading /tmp/vmdk_jQHnvy, the proxy prints a warning message like this. It will not delete the temp file.

avvcbimage Warning <44016>: ReadRegistryEntriesFromRegFile::failed to read system child nodes values of MountedDevices 2022-11-23 19:03:31 avvcbimage Warning <43586>: GetExcludeFileSectors::Get partition driver letter failed.

Workaround: 
Disable the index and exclude feature in the dataset. 
Open Avamar's web interface and navigate to Settings --> Dataset --> Select the appropriate dataset --> Edit.
Clear the boxIndex VMware Image Backups features as shown below:






A permanent solution is addressed by the following proxy hotfixes.

• Avamar 19.4: This was resolved in proxy HF 338728. Install the latest cumulative proxy hotfix. 
• Avamar 19.7: This was resolved in proxy HF 337617. Install the latest cumulative proxy hotfix. 
• Avamar 19.8: This was resolved in proxy HF 338258. Install the latest cumulative proxy hotfix.