When running a pre-command.wsf/post-command.wsf script from "C:\Program Files\VMware\VMware Consolidated Backup Framework\generic" folder the post-command fails to unmount the virtual machine image. e.g.

cscript //nologo pre-command.wsf "C:\Program Files\VMware\VMware Consolidated Backup Framework" server fullvm

cscript //nologo post-command.wsf "C:\Program Files\VMware\VMware Consolidated Backup Framework" server

Returns the following error:

[YYYY-MM-DD HH:MM:SS.SSS 'App' 6684 info] Current working directory: C:\Program Files\VMware\VMware Consolidated Backup Framework\generic
[YYYY-MM-DD HH:MM:SS.SSS 'BaseLibs' 5348 warning] [Vmdb_Unset] Unsetting unknown path: /vmomi/
[YYYY-MM-DD HH:MM:SS.SSS 'vcbMounter' 6684 error] Error: Could not read unmount information
External command failed. See error above.
Exit Code: 1

A file based backup does not have the same issue.

The issue is caused by the mount point being set to c:\mnt\<vmname> for a file based backup and c:\mnt\<vmname>-fullVM for a fullVM type backup. The post-command.wsf script does not handle this naming convention.

Workaround: Append the -fullVM extension to the server name when unmounting. e.g.

cscript //nologo post-command.wsf "C:\Program Files\VMware\VMware Consolidated Backup Framework" server-fullVM

Alternatively comment out line 616 in utils.js to create the mount point as c:\mnt\<vmname>. e.g.

// this.proxyPath += "-" + Util_FullVMPostfix;

This will then the virtual machine to be unmounted with the command:

cscript //nologo post-command.wsf "C:\Program Files\VMware\VMware Consolidated Backup Framework" server