Multiple Servers doing Config file copy to server in Azure

[marius402]

Hi Guys,

FYI

Something I picked up that can mess around a bit. If I add multiple servers to an Azure Windows server and I "File Copy" there, everything works fine, but if you de-install any configured server copying to that location, it will uninstall the VeeamTransport.msi on the target system, even though 10 other machines still use that target as well

Regards

Marius

[HannesK]

Hello,
just to clarify, there is only one VBR server involved, right?

but if you de-install any configured server

does that mean "remove from managed servers" from the backup infrastructure?

As you mention Azure... I would assume the same happens to any Windows machine. Before testing it, I would just like to be sure on the setup.

Best regards,
Hannes

[Mildur]

I think, he has multiple vbr servers with a single azure file server as a target for the file copy Jobs of the configuration backups.
This azure file server was added to each vbr server as a managed server. Because File Copy Jobs need a windows server and they cannot work with smb targets.

If you remove the azure file server from one of the vbr servers, veeam will uninstall the components of course.

[marius402]

Let's try again with the answer...

Mildur is correct

I have about sites that copies its own Veeam config files to a central server, hosted in Azure on a Windows machine. This central server also acts as the Veeam EM server for all these servers.

Regards

[HannesK]

Hello,
yep, multiple backup servers was also my first guess. I read it again and again and could not find a definite answer on that question

If Fabian is correct, then it's expected and correct behavior (independent from Azure again). Different VBR servers don't know about each other. So if you say "remove", then it removes all Veeam components.

Best regards,
Hannes

PS: file copy jobs work with every managed server (also Linux and ESXi servers)