Unable to get the list of clients from NSR VBA resource

Hello Compan,

There is an ongoing escalation with engineering based on that error for a VBA 1.0.149, vCenter/ESXi 5.5.0, NW 8.2.0.1.Build.464 environment.

I would open a service request with EMC for further investigation.

As a good practice is better to have as much environment information , and logs if possible in order to help. Especially on VBA issues

Regards,

--Liliana

Hi Compan,

we had a similar issue where I think the message looked exactly the same.

We got this error message everytime we refreshed the "VMware View", so when networker tries to contact VCenter and VBAs to merge data into one view. The error was caused by the vsphere admin who was cloning VMs at that time. It seemed to us that the new created destination machine had incomplete fields as long as the cloning process took place. Maybe the incomplete fields caused the error? When cloning finished, field were complete.

Afterwards refreshing "VMware view" went without any problems.

Remarkable as well is, that during the timeperiod of the errors the save policies were successful. Adding Machines to a policy via the EBR configure Web Gui worked as well. Even when you add a machine in that way and start the policy from networker NMC.

Does this describe your situation too?

Kind regards from beautiful Schwerin, Germany

Freundliche Grüße

Jens Fuchs

B.Sc. Wirtschaftsinformatik

SIS - Schweriner IT- und Service GmbH

Abteilung Rechenzentrum

Eckdrift 93

19061 Schwerin

Tel.: +49 385 633 5454

thank you for the information,

but what do you mean by vSphere admin?

thank you

I have this same problem and have a case open with EMC.

Backups runs fine (900vms)

Use the WebSphere vCenter and connect to the EBR, go to backup tab and you'll see all your protection policy. You can edit and add vms this way.

another cool thing if you have a vm with an older backup than 72 hours, you can run a backup for those only. Check it out.

Good luck

I mean the person who administers the vCenter. Are there (VM-)cloning or (VM-)copy-jobs running?

When there are (VM-)cloning or (VM-)copy-jobs running and I run a Refresh of the VmWare View in Networker Management console I get excactly the message you got.

As soon as the jobs are finished, refreshing VmWare View works again.

Does this fit four your situation?

Kind regards from beautiful Schwerin, Germany

Freundliche Grüße

Jens Fuchs

B.Sc. Wirtschaftsinformatik

SIS - Schweriner IT- und Service GmbH

Abteilung Rechenzentrum

Eckdrift 93

19061 Schwerin

Tel.: +49 385 633 5454

Good Morning

When I try to use the WebSphere vCenter I have an error message:

An internal error has occurred - Error # 1009.

Reloading the customer is recommended, so as to clear Any problems left by this error.

Click Yes to reload the vSphere Web Client?

Have you any idea?

Thank you in advance

Can you change your VBA-user to Role "Administrator" in VCenter to see if this is a permission issue?

I would like to see what daemon.raw tells during failing Refresh of Vmware View.

Regards,

Jens

Good Morning

No home I have this error all the time:-(

Thank you in advance

If you’ve been backing up your virtual machines with VBA, you’ve probably hit that moment when you’ve run an mminfo query and seen output looking like the following:

As you can see, that’s not the most effective way to see virtual machine names – vm: doesn’t allow you to easily match it back to the virtual machine in question.

However, not all is lost. With VBA backups came a couple of new options. The first one is a “VBA backups” style report, using the command:

# mminfo -k

Using mminfo -k you’ll get a very tailored output focused entirely on your VBA backups, and it’ll resemble the following:

That’s a really good way of seeing a quick listing of all your VBA-based virtual machine backups, but if you’re wanting a way of reconciling in normal mminfo output, you can also make use of a new mminfo report field, vmname. For example:

(In the above command I could have used name and vmname in order to reconcile vm: entries to virtual machine names, but elected not to for brevity.)

There you have it – a couple of quick and easy ways of quickly seeing details of your virtual machine backups via mminfo.