We are creating a new NetBackup environment from the ground up to replace our old one.
We are having an issue getting NBU to list the clients in a VMware policy.
Whenever we try to add a client and select "Browse and select Virtual Machine" option in the browse for Virtual Machines screen we get a "Failed to get VM Server Info List: uniplemented error code 255. (255)"
We have even gone so far as to comepletely rebuild the master and media server in this new environment to no avail.
The credential check out fine for the VMware Virtual Center Server and I can even see the service account that we are using (which is an admin account) log into the VC.
With our original install of the new system everything worked fine for a few days. We came in and installed the NB_7.0.1_ET2105102_5 hotfix and made a few other changes and then everything broke with the error metioned before.
Thinking that Windows Media server was not properly backing out of the patch is what led us to wipe and re-install the Media server and Master server and rebuild from the ground up. But now even, before applying the patch we are getting the exact same error.
We have tried to reboot the VC with no luck either.
I don't know where else to go as far as trying to figure this one out on my own.
Our environment is a RHEL 5.5 Master and Win2k8 R2 x64 Media.
vSphere 4.0.1 on Win2k8 Standard SP2 x-64
I have copied an edited output of the bpVMutil log below:
I can communicate with the ESX hosts directly when browsing for Virtual Machines. But if I select the Virtual Center instead of the ESX host in Virtual Machine Servers Credentials I get the previously mentioned error.
I would suggest opening a ticket with Symantec support. I had several issues with getting my vmware backups to configure properly. They are stating there are some issues using the java console (I could not get the validation to work from it). We did it from the Windows media server and that worked. They also had me do several registry changes for logging, but also for some config issues. Not sure that it is totally related, but I will look those up and post them.
First of has this issue been fixed?
"Failed to get VM Server Info List: uniplemented error code 255. (255)" - I assume you mean "unimplemented"
Did the EEB fix the issue? As of today the latest rollup patch is v14.
Next.... is a cache file being built? Take a look at c:\program files\veritas\netbackup\online_util\fi_cntl\. The best thing to do is to clean out that folder and do a new client refresh.
=> if it gets built. Take a look at the last entry in the vcbvmname_* file. The VMs are listed in blocks inside that file. Do you see any errors?
I recall something way back when IF the network card on the VM did NOT have a network assigned.
Anyway let me know if this has been fixed or not...