Good Day,

How is everything with you, I picked interest on you after going through your short profile and deemed it necessary to write you immediately.I have something very vital to disclose to you, but I found it difficult to express myself here, since it's a public site.Could you please get back to me on this email( mbawuah79@gmail.com ) for the full details,
Have a nice day

Thanks God bless.
Mrs Abiola.

Hi John,

Thanks for the feedback!

It's true that if you export a specific virtual machine to vmPRO, then all of it's VMDK's are exported and thus usable for backups by vmPRO (SmartMotion scheduled jobs) or through Networker or other utility that can backup CIFS/NFS shares. Right now, you can't pick just one VMDK from an exported VM.

Of course, you don't have to backup all the VM's on a given ESX host, just those that you choose to export to vmPRO.

Currently, vmPRO executes backups of up to 4 VM's at a time, per vmPRO instance. So, if you had more than one instance (allowable by the license) then you could do more than just 4. Additionally, there is a tunable parameter that can be adjusted to allow more streams, but that's considered something you do with consultation from our Service group.

Just a note on the concept of more than one vmPRO instance. vmPRO counts multiple instances configured in a vmPRO Group against the same license. That's because you can manage multiple instances from one GUI, with all capacity being rolled up to the master node for capacity enforcement. Each node in a group can have different policies from the other nodes and can be responsible for different VM's, but management is presented in a unified manner within the GUI. Just look in the Users Guide for information on "Group Mode" if you want to learn more about this.

If you had the need to have totally separate management and administrative controls, then you would use a separate license for each instance of vmPRO and treat each instance as independent from each other.

Hope that this helps!