Veeam Backup & Replication • Re: [V13] Failures on synthetic full

hi,
Just to close the loop on this, the issue was not a problem with the Veeam setup, but rather a configuration issue on my side.
Just prior to the weekly synthetics, I had made a DNS change so that I could reverse publish both vCentre and Veeam console via haproxy (to make it easier for our internal users), so that the DNS entries pointed to haproxy rather than Veeam (Primarily so I could leverage cert handling on haproxy rather than having to configure certs within Veeam and vCentre).

The consequence of this was that it broke the flow during a backup cycle, so I created static entries for vCentre and Veeam (with their real internal IPs) and added them to the veeam console so the internal backup flow now prevents the traffic going through the proxy.
Thankfully the appliance model makes this easy to action from within the Veeam server appliance UI using the following approach;

# Override the DNS for the following servers (to ignore impact of reverse publishing)
* Log in as veeamadmin>
* Appliance console>Logs and Services>Host Configuration>/etc/hosts>Export
* Paste in the 2 additional entries (one for vcentre and other for Veeam) and save the file locally, then >Import
* Log off appliance, and log back in as veamso and approve the request
* Repeat for each of the 4 proxies and linux repositories in-case any communication relating to the proxies require DNS lookup directly to Veeam/Vcentre

so we are back on track and our Veeam V13 rollout is running great!

Statistics: Posted by ashleyw — Sep 30, 2025 9:08 pm

---