For anyone stumbling across this. Shout out to Allan from Veeam support who was able to help me out.
The issue was that the repository had previously been used for Veeam12 and I attempted to use this for Veeam13 and this can cause an issue with the systemd startup process for Veeam.
So the solution was simply to remove the /etc/systemd/system/veeamtransport.service file and then to reconfirm the server under the managed server list and then things work perfectly after a reboot.
For any naysayers on Veeam Support, I have never had a single negative support experience with Veeam in the last 15 years we've been using their products - so keep up the great work team!
cheers
Ashley
The issue was that the repository had previously been used for Veeam12 and I attempted to use this for Veeam13 and this can cause an issue with the systemd startup process for Veeam.
So the solution was simply to remove the /etc/systemd/system/veeamtransport.service file and then to reconfirm the server under the managed server list and then things work perfectly after a reboot.
For any naysayers on Veeam Support, I have never had a single negative support experience with Veeam in the last 15 years we've been using their products - so keep up the great work team!
Code:
# systemctl stop veeamtransport # cd /etc/systemd/system/ # mv veeamtransport.service veeamtransport.service.old# reboot* Veeamconsole>Backup Infrastructure>Managed servers>Linux, edit existing server, and reconfirm. Ashley
Statistics: Posted by ashleyw — Sep 30, 2025 8:47 pm
/english-betterindia/media/post_attachments/uploads/2022/05/Sustainable-home-10-1651667432.jpg)
