I had similar symptoms and ended up contacting support. In my setup, the networker server was also configured as the VADP proxy. This meant that it was listed twice in the client list. The EMC engineer told me that Networker selects the client and app info at random. So a VADP backup may not get the vadp application information just as the error indicates. The fix was to make sure that the vadp application information on the Apps & Modules tab was present in both clients. My backups have been 100% successful since adding the infomation.
Initializing VADP Configuration. Using xxxx as the VADP proxy server host for client yyyy. 81094:nsrvadp_save: Failed to get application information attribute of configured proxy server xxxx for client yyyy 80416:nsrvadp_save: Failed to get application information attributes of proxy server for VM client yyyy. 80990:nsrvadp_save: Failed to initialise the VADP Configuration values.
And xxxx/yyyy are hostnames of FQDN? Or more importantly, do those match exactly NSR client name? If not, can you double check those are included in alias field?
Did you enter the correct parameters in the Proxy Host properties in Networker? You need to add stuff to the APP properties like what the VCenter is, what type of backup you want (SAN, NBD,...).
Yes, my EMC networker VMware backup is also failing, so the only silly work around is by uninstalling the VMware tools and then installing it back again without the VMware VSS provider ?
can anyone please confirm this before I remove it from hundreds of my VM ?
1) add your vCenter to Vitalization. It will need to fully populate
2) remove (delete) the client that you have for VADP.
3) in the (Configuration tab) Vitalization (vCenter) find your VMware clients "client backup configuration" option. it will populate the info for you i.e client name server, you will need to fill out the rest. I also let it make me a new group. Do not for get to add the new group to the media pool.
If your VADP Virtual storage Node is setup right. Like the /mnt is on a local hard drive and your backup media (could be Advance file system like mine or tape) it should work. Do not for get to add the new storage node to you User Group Administrator for your index's.
It's strange that a couple of client failing when all was ok...all the above parameter seems correct..anyone had it working? Probably delete and recreate the client with all config does the trick? Please advise..
The solution pfochi offered worked for my setup. We also have the NetWorker server as the VADP proxy and it started failing for no apparent reason. Good explanation, thank you for sharing.
pfochi
1 Message
3
August 12th, 2011 07:00
I had similar symptoms and ended up contacting support. In my setup, the networker server was also configured as the VADP proxy. This meant that it was listed twice in the client list. The EMC engineer told me that Networker selects the client and app info at random. So a VADP backup may not get the vadp application information just as the error indicates. The fix was to make sure that the vadp application information on the Apps & Modules tab was present in both clients. My backups have been 100% successful since adding the infomation.
unexpected1
34 Posts
0
July 6th, 2011 06:00
Provide more info please. Logs, VADP proxy server information, ESX version, VCenter version,...
Omega Periphera
9 Posts
0
July 6th, 2011 09:00
VMware vCenter Server Version 4.1.0 Build 258902
VMware ESXi 4.1.0 Build 260247
VADP Transport Mode: SAN|NBD
Logs:
Initializing VADP Configuration.
Using xxxx as the VADP proxy server host for client yyyy.
81094:nsrvadp_save: Failed to get application information attribute of configured proxy server xxxx for client yyyy
80416:nsrvadp_save: Failed to get application information attributes of proxy server for VM client yyyy.
80990:nsrvadp_save: Failed to initialise the VADP Configuration values.
ble1
4 Operator
•
14.4K Posts
0
July 7th, 2011 06:00
And xxxx/yyyy are hostnames of FQDN? Or more importantly, do those match exactly NSR client name? If not, can you double check those are included in alias field?
unexpected1
34 Posts
0
July 8th, 2011 00:00
Did you enter the correct parameters in the Proxy Host properties in Networker? You need to add stuff to the APP properties like what the VCenter is, what type of backup you want (SAN, NBD,...).
Albertwt
2 Intern
•
164 Posts
0
July 20th, 2011 19:00
Yes, my EMC networker VMware backup is also failing, so the only silly work around is by uninstalling the VMware tools and then installing it back again without the VMware VSS provider ?
can anyone please confirm this before I remove it from hundreds of my VM ?
Thanks.
lee6
68 Posts
0
July 21st, 2011 08:00
I have the same setup it sounds like and the same problem with the same error.
lee6
68 Posts
0
July 22nd, 2011 15:00
I got this to work.
1) add your vCenter to Vitalization. It will need to fully populate
2) remove (delete) the client that you have for VADP.
3) in the (Configuration tab) Vitalization (vCenter) find your VMware clients "client backup configuration" option. it will populate the info for you i.e client name server, you will need to fill out the rest. I also let it make me a new group. Do not for get to add the new group to the media pool.
If your VADP Virtual storage Node is setup right. Like the /mnt is on a local hard drive and your backup media (could be Advance file system like mine or tape) it should work. Do not for get to add the new storage node to you User Group Administrator for your index's.
Thierry101
2 Intern
•
326 Posts
0
November 23rd, 2011 11:00
Hi All
It's strange that a couple of client failing when all was ok...all the above parameter seems correct..anyone had it working? Probably delete and recreate the client with all config does the trick? Please advise..
ccouse
1 Message
0
July 12th, 2012 13:00
The solution pfochi offered worked for my setup. We also have the NetWorker server as the VADP proxy and it started failing for no apparent reason. Good explanation, thank you for sharing.