I was referring to the API being the same not the closing snap shot issue youre talking about. When and why the Snap shot API's are sent are 100% on the 3rd party apps i.e. VCB or vRanger, I just want to be clear that vRanger does use the same API as VCB.
BTW, I just installed a build from...
The case youre talking about was a Snap shot API issue, that VMware API went into a Loop and cause a large chain to occur.
If you perform a backup and after the snap shot is added, kill the backup, come back and perform a backup vRanger will close the open snap shot and start a new one...
Keep in mind any app that uses VMware Snap shots i.e. VCB by its self, vRanger and vRanger using VCB. They all just use the VMware snap shots API provided.
In the cases of vRanger, I will say the cleanup process could be better. Since ESX 3.x VMware took over the commit process for snap...