
I tried moving a replica target from CSV iSCSI storage to the SMB3 share (all went smoothly), and performed a "reseed/remap" in the replication job (again, the Veeam console accepted this), but I then got issues during replication that looked as if Veeam was trying to perform RPC calls against the SMB3 server and not liking the responses

So I moved the replica VM back to the CSV, and the retry worked fine. So I hadn't broken the replica VM by moving it.
I should point out that the SMB3 share is working fine for live VMs in the cluster, and I can move running VMs back and forth with no issue, and between Cluster Nodes, etc.
Obviously, I can't install any Veeam components on the NAS server offering up the SMB3 share, as it is non-Microsoft.
I am also aware that CBT will fail when I get round to moving the source VM to the SMB3 share topology too (pre-Windows Server 2016 hosts, so no native CBT).
I have a suspicion I need to add the SMB3 Share in to Veeam console (so I can define some credentials to use against it and perhaps avoid the RPC errors), but it is not exactly clear this is the correct approach?
The only location I can find to add the SMB3 share is under "Inventory -> File Share", which kind of implies you want to back it up rather than send replicas to it.
Or is this a topology that won't work?
*Update*
Sorry, I should state it is using Veeam B&R Enterprise v11.0.0.837