Well,
After checking out this other thread: post353936.html#p353936, I disabled a second Network card from the File Server that was been in use to connect an iSCSI server and the Backup Job back to work again without issues.
So, I am assuming that the issue that I faced is related with a second network card in the client.
Does someone had/know some issue when working with two network interfaces in the Client? Some advise?
Thank you,
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Jul 18, 2020 12:47 pm
- Full Name: Alexandre Mendes Guedes
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Windows File Server Backup job suddenly stopped working.
Alexandre,
I would suggest contacting our suppot team to reconfirm that adding a second NIC is an issue. They should also help you with the solution.
Thanks!
I would suggest contacting our suppot team to reconfirm that adding a second NIC is an issue. They should also help you with the solution.
Thanks!
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Jul 18, 2020 12:47 pm
- Full Name: Alexandre Mendes Guedes
- Contact:
Re: Windows File Server Backup job suddenly stopped working.
I found the Issue.
In both servers (client and Veeam Backup) I had a second Network Card configured with the Same IP Address ranges (192.168.10.x/24). These NICs are used as point to point connection with iSCSI servers.
After changing the IP Addressing range of the second NIC in one the servers, the Backup run successfully.
Thank you,
In both servers (client and Veeam Backup) I had a second Network Card configured with the Same IP Address ranges (192.168.10.x/24). These NICs are used as point to point connection with iSCSI servers.
After changing the IP Addressing range of the second NIC in one the servers, the Backup run successfully.
Thank you,
Who is online
Users browsing this forum: No registered users and 4 guests