vRanger v3.2.0.28142 problems

[crazex]

I have just upgraded my vRanger Pro to the newest 3.2 build. This was the full release. Everything seems to be working fine, with the exception of one thing. When I try to use a .info file to do a either a file level, or full-VM restore, the application throws up a stop error. I can continue past this error, but then when I try to mount the .vmdk files, I am only able to see one of them. Each of my VMs have 3 disks. If I do a restore via the list of previous backups then everything works fine; however, I need to be able to restore via the .info files, for DR purposes. Has anyone else run into this error, and if so, where you able to fix it? If anyone from Vizioncore wants to chime in, that would be great. Will there be a new build that fixes this issue?

-Jon-

[doubleH]

i have the same issue. vizioncore is aware of this. they told me to use

a work around of restoring the entire vm as a separate instance until

the issue is resolved.

[crazex]

Thanks. Did Vizioncore give any ETA on the fix?

-Jon-

[doubleH]

no. let me ask them and i'll post back.