Windows File Level Restore Asking for old Proxy

[stevil]

I changed all out proxies a few months ago since the old servers were being replaced with 2008 servers. I tried to do a file restore from one today and it basically looks as though it's still trying to find the old proxy to do the restore through, which is odd.
The error I get is

"Failed to resolve host name "xxxxxx.xxx.xxx.com" No such host is know"

I tried adding the old host name to the hosts file and redirecting it to the new proxy server, this didn't work either, although it thought about it for a lot longer.
I'm currently applying the latest patch but I don't see anything in the release notes to suggest this will fix it. Anyone else experienced this?

[homerjnick]

Is the old Proxy still in the list under Backup Infrastructure? How did you remove the old proxy, did you uninstall the Veeam Transport Service from it first before retiring the machine?

[stevil]

No it's no longer there. I removed it in the proper fashion as you mention. I've logged a call with Veeam for this.

[homerjnick]

Post your case id for Veeam staff who look at the forums, you might get a faster response from the forum from a Veeam staff who has encountered this issue before...strange issue indeed.

Might be references in your Veeam DB to the old proxy...

[stevil]

"00251472"

[Dima P.]

Hello Steve,

Could you please clarify was only proxy changed during your infrastructure upgrade lately? Is there any chance that the original ESXi host configuration was changed? Also you could perform the following test – try to run an Instant Restore to New Location, specifying all settings manually, and see if it proceed successfully.

Nick, thank you for your input – highly appritiated

[Dima P.]

"00251472"

Thank you for the case number - will look into this!

[Dima P.]

Steve,

The solution provided in the case - to re install VeeamTransport.msi/update to last patch sounds perfect.

[stevil]

Yes, unfortunately it hasn't worked

[foggy]

I changed all out proxies a few months ago since the old servers were being replaced with 2008 servers. I tried to do a file restore from one today and it basically looks as though it's still trying to find the old proxy to do the restore through, which is odd.

I'm not sure proxy is involved in FLR process at all. Could you please elaborate on what changes were introduced to your environment a few months ago?

[stevil]

Sure. All I did was create a new proxy at each remote site since we were retiring the old 2003 servers. Backups have been working OK, it's just this restore that's a problem. I tried another one of our remote sites and got the same issue, so it's not site specific.

[foggy]

What is your setup at those remote sites? Do you have proxy and repository installed on the same machine?

[stevil]

The exact setup varies, but at this particular site we backup to a synology NAS, the proxy is on a VM hosted on ESX

[foggy]

And what backup repository type is used to add NAS to Veeam console?

Anyway, I can see from the case that you were requested to provide the configuration database to support. Let's wait for what they can say after reviewing it.

[veremin]

Additionally, what happens if you try to restore required files using “Other OS” option? Do you get similar error or not?

Thanks.

[stevil]

'Mount host is not specified for backup repository "xxxxxx xxxxxxxx" '

[veremin]

Hmm, can you then confirm that “Enable vPower NFS Server” box is ticked in the settings of given backup repository?

Thanks.

[foggy]

'Mount host is not specified for backup repository "xxxxxx xxxxxxxx" '

That's pretty much saying that the issue is in repository (not proxy).

[stevil]

The backup repository looks fine,it's pointing to the current, live proxy. It's not seeing vpower NFS on there though.
I may try and install a new proxy and see if that fixes the situation.

[stevil]

New proxy doesn't make any difference. I'm awaiting a conf call/screen share with Veeam on this now.

[veremin]

It's not seeing vpower NFS on there though.

May I ask you then to go to the settings of this repository (where a given backup file is stored), enable vPower NFS role there, and see whether you are able to perform “Other OS” restore or not?

In order to do it: right-click a repository -> Properties -> vPower NFS -> Enable vPower NFS.

Thanks.

[stevil]

Ah, we have action. Adding that new proxy with a working vPower NFS has made the other OS restore work. Windows restore still doesn't work, but this will at least allow me to restore the file. Thanks

[veremin]

It seems that you’re mixing up two terms – proxy and repository. Please be aware it's a repository where backup data is stored and where the vPowerNFS should and can be enabled; meanwhile, the proxy server is nothing but a “data-mover”. Though, it’s possible to have both roles deployed on one server.

For the purpose of complete understanding - I haven't proposed to create a new repository, rather just to enable vPower NFR role in the settings of existing repository (where corresponding backup data is located) and see whether it helps or not.

Thanks.

[stevil]

No problem. Our repository is a synology NAS, so we can't run vPower NFS directly on that. We pretty much always have it installed on our proxies.

[veremin]

Our repository is a synology NAS, so we can't run vPower NFS directly on that

Ok, now it’s clear. Thanks for shedding a light on it.

Anyway, I’m glad to hear that at least “Other OS” type of restore works now; as to Windows FLR, let’s wait for the support team’s answer.