Skip to main content

I have a new small environment using the community edition.  There is no domain or DHCP server (except the router).  Single server doing VBM and VBR.  VBM working perfectly.  VBR failing for recan within the backup job.  However, rescan will run if initiated from Backup Infrastructure.  ADMIN$ share is accessible over a network call.  I get the same results regardless of using a direct IPv4 address or the server’s name.  Server name has been imbedded into the HOSTS file.

I’m concerned that IPv6 may be interfering with this install.  The server was initially setup in another office without v6 being present.  Server has v6 turned off, however ping of the server name is still returning a v6 address unless it’s forced to v4.  My suspicion is that VBR is issuing a v4 network request that is being returned as a v6 reply.  

Any ideas?

Is the VBR server also acting as the backup proxy, or has that been broken out to a dedicated proxy server. If so, can the proxy server resolve the IP address and connect to the target system?


i don’t think ipv6 is providing an issue, you need to test connection, if is working, then is ok

sorry, what is VBM?


You can try disabling IPv6 and see what happens but that should not play a role here.  As asked by Tommy is the Veeam install an “all-in-one” where everything is on the same server?  What specific version of Veeam are you using 12.3.x?  What version of Windows is this installed on?

You can check the logs here - C:\ProgramData\Veeam\Backup\Jobname to see if that points you somewhere.


Thank you all for your replies.  A few questions were asked.

Tommy O’Shea - this is a one server wonder install.  Everything is on-board the box.

Marcel.K - VBM refers to Veeam Backup for MS 365

Chris.Childerhose - I will check those logs!

 


What is being failed to rescan during the job? Is this a VM backup job, Windows agent?


Let us know what you find in the logs.  That should point you in the right direction or at least where to start looking.


Comment