NBU 7.01 and vSphere 4.0.1 issue

[jmjudge]

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.

NBU 7.0.1

vSphere 4.0.1 on Win2k8 Standard SP2 x-64

I have copied an edited output of the bpVMutil log below:

Please help!!!

 

09:06:35.380 [3276.3888] <2> logparams: C:\Program Files\Veritas\NetBackup\bin\bpVMutil.exe 0 0 _NONE_ 

09:06:35.380 [3276.3888] virt_test_log: log function is called

09:06:35.380 [3276.3888] <2> bpVMutil main: cmd = 0 ESXMount = 0 ESXserver = _NONE_, flags = 0

09:06:35.380 [3276.3888] <2> bpVMutil main: Hyper-V GET Names requested

09:06:35.396 [3276.3888] <2> vnet_pbxConnect: pbxConnectEx Succeeded

09:06:35.396 [3276.3888] <2> logconnections: BPRD CONNECT FROM xxx.xxx.xxx.xxx.27696 TO xxx.xxx.xxx.xxx.1556 fd = 576

09:06:35.427 [3276.3888] checkBackupRegEntry: looking registry for excludeVMservers

09:06:35.427 [3276.3888]  RegOpenKey failed with 2

09:06:35.427 [3276.3888] format_virtualserver_cred: read 1 xxxxxx.xxxxxx.com xxxxxx 66da4c6401b11b1c716ec0a8b4434a224a8183c1b44cd5962d84ab155592193756d81ff4bee197c06773d9246d8b698bd0f894e47fba555bbf266dd474e8f63f 20526 0

09:06:35.427 [3276.3888] format_virtualserver_cred: read 1 xxxxxx.xxxxxx.com xxxxxx f9d9e26925cf7b4aab4c83a34e8c2ba930c48b112e064e899bc98809b73e2def6defdeadde508afab9b41d36146b39fd424bb4e5aa8d31ba0a2ee0d27e96ab58 c557817ca1ffe5c935d39382013e291d 0

09:06:35.427 [3276.3888] <2> bpVMutil main: Saving xxxxxx.xxxxxx.com guests to C:\Windows\TEMP\VMutl-03276301321195380888000000000-a03888

09:06:35.427 [3276.3888] <2> get_VM_names: get_VM_names: read for xxxxxx.xxxxxx.com

09:06:35.427 [3276.3888] get_id_lock: wait lock timeout value: 15 minutes

09:06:35.427 [3276.3888] fis_lock: entering ...

09:06:35.427 [3276.3888] rw_lock: leaving ...

09:06:35.427 [3276.3888] WRITE LOCK VMcache_lock fd = 576

09:06:35.427 [3276.3888] <2> get_VM_names: get_id_lock returned 0

09:06:35.427 [3276.3888]  read cache file = C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\vcbnames_xxxxxx.xxxxxx.com_Any

09:06:35.427 [3276.3888] cache file C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\vcbnames_xxxxxx.xxxxxx.com_Any does not exist

09:06:35.427 [3276.3888] getHostView: Getting VM's for xxxxxx.xxxxxx.com

09:06:35.427 [3276.3888] vSphereConnect: connecting to https://xxxxxx.xxxxxx.com/sdk

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for jobtimeout

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for poweroptimeout

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for snapshottimeout

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for registertimeout

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for browsetimeout

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for connecttimeout

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: JobTimeout: 900 secs

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: PowerOpTimeout: 900 secs

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: SnapshotTimeout: 900 secs

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: RegisterTimeout: 180 secs

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: BrowseTimeout: 180 secs

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: ConnectTimeout: 300 secs

09:06:35.786 [3276.3888] checkBackupRegEntry: looking registry for vmcloglevel

09:06:35.786 [3276.3888]  RegOpenKey failed with 2

09:06:35.786 [3276.3888] SetTimeoutsAndLogging: vmcloglevel=0

09:06:35.833 [3276.3888] dovSphereLogin: login for xxxxxx.xxxxxx.com completed with flags 70 and status 0

[jmjudge]

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.

[AudienceofOne]

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.

[thesanman]

Get NB_7.0.1_ET2105102_7; I had an issue with (I think) _5 and applying _7 corrected my issue.

[pikachu]

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...