7.6.1 from what I heard. Right now 7.6 will support old fashioned VCB, but work on API support is something engineering was committed and will probably be part of 7.6.1.

On a related topic...

How do you deal with VM failover between ESX hosts? I have Networker 7.5 SP1 and am in the process of evaluating the VCB integration. The client definition appears to need to have the ESX host named in it's configuration. If my vm fails over to another host and the scheduled backup runs again it fails backup.

Eric

actually was onsite yesterday at EMC for a technical session on v7.6 and was told that the API would be available with the release. unless they themselves hadnt been updated that there was a delay on it until SP1. hmm

In theory it should not matter if it failed to another host and backup should still run. What error message do you get?

As for 7.6... 3 weeks ago I've been told VCB would be supported with this release while API support would come with 7.6.1. It's possible that EMC felt they would leave they own puppy far behind compared to some other solution thus might have changed their priorities. We'll see once that 7.6 becomes GA.

The ESX host shown on the client configuration is only for licensing. The most important thing for backups and restores is Virtual Center (unless you are in a single ESX Host environment). Virtual Center is the traffic cop for backups and restores of VM's. The ESX Host defined on the properties of the client is immaterial.

Hello,

thanks for this interesting infos.

We are using the FSC/FTS-labeled versions, and most of time the first version of an new release consists of an SP1 version of EMC . So it doesn't matter for us if vStorageAPI comes with 7.6 or 7.6SP1, the most important thing is that EMC will support this API soon.

Regards

Patrick