VeeamTransport.msi update on Microsoft cluster a/p 2 nodes

[KeiichiKun]

Hi all,
as backup repository I've a CIFS resource shared from a Microsoft cluster active/passive with 2 nodes; let's call BS1 the active node, BS2 the passive node, BS3 the virtual node.
During update to 9.5U2 VeeamTransport.msi has been updated on BS3, so I think that BS1 has been update, but no BS2
In case we have to switch BS2 to active, how could Veeam reacts? I need to switch manually BS2 to active and launch console to update Veeam Transport on BS2?
Thanks

[Andreas Neufert]

I am not sure if I understand your setup completely.
A CIFS share as Repository has no software running from Veeam, as we only see the share not the computing OS behind it... Think about a CIFS share published by Linux.
Can you explain a bit more the situation and setup.

[KeiichiKun]

Hi, you're obviously right about linux cifs.

Cluster configuration:
BS1 active node
BS2 passive node
BS3 virtual node

Veeam configuration:
Under Managed Server I've BS3 as Windows Server
Under Backup Repository I've a CIFS resource named BS3_veeamrepo with path \\BS3\veeamrepo

Software installed on servers:
Under "program and features" of server BS1 (active) I've Veeam Backup Transport and Veeam Installer Service
Under "program and features" of server BS2 (passive) I've nothing about Veeam

I think that is "managed server section" that has installed transport.. so I can change the question.
It could be a best practice (manually or changing the active node) the transport on passive node?

Thanks

[foggy]

You can manually install the installer and transport components on the second node, they are located in Veeam B&R installation folder (C:\Program Files\Veeam\Backup and Replication\Backup\Packages by default).

[Andreas Neufert]

Anyway a CIFS target (even on windows) do not need any installed software.
On Repository level there are 2 systems that need installed windows sofware and this is the Gateway Server and Mount/NFS Server. Both can be a Proxy Server and do not need to be one of the CIFS Server.

If you had added the CIFS share as SMB3 share under managed Servers, this is not necessary and only needed if you run Hyper-V VMs on the SMB3 share.