nsrvadp_save: The following internal error occurred: Unable to download config file

Hi Broeste- Moving this over to the support forum to get additional views for you.

Allan

Please review these EMC KB articles:

Verify versions:

http://solutions.emc.com/EMCSolutionView.asp?id=esg112035&usertype=C

Similar issue with VMware KB article link:

http://solutions.emc.com/emcsolutionview.asp?id=esg121746

You will need access to powerlink.emc.com in order to read these articles.

Let us know if either of these are usful.  If not, I will research this error more.

Thanks!

Mark

Let me dig into this and see what I can find for you.

Please let me know the version of the NetWorker server and the version of VMware.  It will help me in my research.

Thank you!

Mark

Hi Mark,

I have tried changing the vcenter config in NW so everthing is configured with FQDN but no luck. I think you are right about it might be a Vcener version issue. The customer has 2 vcenter. 1 for their ESX located in the US and 1 for the ESX in DK. The version in US is Vcenter 4.1 and the one in DK is 4.0. I have asked to customer to upgrade Vcenter in DK to 4.1. I'm waiting for his response. I also looked at the articles you posted but I don't think it relates for these issue. There is no problem in creating the snapshots. Thank you for your help so far, I will keep you posted

I had the same problem.

I found the problem and solution in my case: the VCB user was still configured in VCenter with "VCB" permissions. These are not sufficient, because when I set it to "Administrator" to make sure the issue is not permission related, it worked like a charm.

Next step will be to create a new permission role in VCenter with all the rights that are in the Integration Guide for 7.6.2. but I will continue testing with "Administrator".

Hope this helps.

Hi,

I checked if it would be a permission issue but my user is Administrator in Vcenter. The strange thing is that my customer has 8 ESX servers runing under the same Vcenter. It works with all the machines on only one of the ESX servers. The others fail with the above error message.

Hi fellas,

I'm really getting grey hair because of this error. I had a look in Vcenter we I ran a successfull backup. See attached file

Everything looks fine and the backup is successfull. When I try to run a backup of another VM on another ESX server in the same Vcenter I get this

I really don't understand why it will work on one ESX server and not another one i the same Vcenter. Its the same Networker hypervisor resource being used for both backups. Anybody have any ideas on this???

Perhaps a stupid question, but where did you give your "administrator" the necessary permissions in VCenter? Make sure you set it up in the "Datacenter" level. Perhaps you did it on the ESX host level and only on the host where it works...

Let us know.

Well the user I'm using is a domain admin created in AD. I have used this account for VCB backups prior to 7.6.2. I can see in vcenter that the user is administrator. Maybe I should try to create an account manually in vcenter for the VADP user role

Sent from my iPhone

It can be an AD user, that's no issue as far as I know.

Did you check what I am saying? Are the permissions for your AD user in VCenter defined in the "datacenter" level in VCenter?

Yep, its set on the datacenter level

No, every permission is propogated correctly. I did some testing today and will post the result later. Don't want to write that much over the phone

Sent from my iPhone

If you take the properties of the non-working ESX hosts, are you seeing the specified user underneath "Permissions" as well? Just to make sure the permissions are being replicated across the hosts.

Hi Bojan and others,

ok, this is how far I got today on the issue. I am now pretty sure  that it is something going wrong when I upgraded the clients from VCB to  VADP accordingly to the Networker for VMWare integration Guide.

The difference between the one working and the ones not working is that under the Info & Licensing tab on the client configuration in Networker I can see that the client still thinks it's using 7.6.1. I now that this is updated everytime a successfull backup is run. This made me try and delete the client not working and create it again. Same error as before.

I then tried to create a new VM and autodiscover it on one of the ESX servers not working. This is a client never configured before and the backup was successfull. So I can say with some degree of certain that this is not a permission issue between Networker and Vcenter but more an issue with the upgrade process from VCB to VADP for the client part. Why it is working on one ESX server when I upgraded, I don't know but now it seems like I'm not the only one seeing this.

So my conclusion is that if you create new clients from the ESX servers not working, it should work fine.

Bojan, can you give this a try on one of ESX that doesn't work. Just to verify that we are seeing the same???

I don't know where to go from here. I would imagine that this is a matter for EMC engineering but does EMC want me to create a SR for this? I know that many EMC's is live on the forum so please let me know how I should proceed on this matter????

best regards

Thomas

Hi,

I have the same problem as you.

everything is working on the first node of the cluster, but not working on other nodes.

User is administrator on VC and is propagated correctly.

BR

Bojan