File Copy in VLAN

[frabinow]

Hi,

I have a VM in one vlan and would like to only replicate some folder to another VM in another vlan.
For that, i use the File Copy Job feature.

My problem is that the veeam backup server is not able to find the source VM or target VM even if all ports are open in my firewall.
With Replication Job, we can specify a source proxy and a target proxy. This is not possible for File Copy.

Has someone a solution for that ?

[foggy]

Francois, unlike other jobs, file copy is performed by the backup server itself, without use of proxy servers. Do you get any errors during file copy job operation? How do you specuify source and destination in the job properties and can you add those VMs to Veeam B&R console?

[kjc3303]

Which vlan is the backup server on? Does the vlan that the backup server is on have access to the other vlans? Can you ping them from the backup server?

[frabinow]

First, I add my source server and my target server to the Veeam B&R Console.
Then, I create a file copy job and go browse the servers to select specific folders.

My Backup server is on one VLAN, my source server is on another VLAN and my destination server is on another vlan.
The vlan of my backup server has full access to the 2 others vlan, but only ICMP request, HTTP and HTTPS are open in the other way.
I tried will full access in the 2 way.

I can ping all servers between them, so it seems that they are able to communicate. I can also access the Share Admin folder of the source and target servers from my backup server. But when I run the File Copy Job, i have this error :

Failed to connect to server 'SERVER', IPs 'XXX.XXX.XXX.XXX'; 'SERVER' , port '2501' Client error : No such host is known

[Gostev]

Looks like DNS issue to me.

[frabinow]

DNS resolution are ok.
I even add the backup server in the hosts file of the source server and the error is still there.

You should know that my backup server is in a domain but not my source and target server.
But i add as Prymary DNS suffix the name of my domain for the workgroup server.

[tsightler]

It's important to note that the target will connect back to the source to actually pull the data so you must make sure that the target server can resolve the name of the source server and reach it on TCP port 2501.

[frabinow]

I didn't know that the source and target servers have to communicate. I was thinking that everything was done by the backup server.
I opened the port and I had a wrong ip server in the vlan configuration in my firewall that i didn't saw.
It's working now.

Thanks for the help.

[tsightler]

You can probably make the server perform the copy by using UNC paths to the source and target, however, if you actually add the servers and managed servers and select them then it will leverage the Veeam FastSCP protocol instead which is generally much faster but requires multiple TCP connections in the 2500-5000 range (assuming a single copy operation, 2500-2510 should be enough ports).