Hi guys, we have an ongoing case with Veeam Support now.
The issue was that the hardened repository suddenly disconnected last Sunday/Saturday. This happened to two deployment on a different client and it happen at the same time.
1 of the hardened repository was deployed recently only (1 month++) and we performed a reboot, and re-configure the hardened repository and it managed to remove both veeamdeployment and veeamtransport services and reinstall it back. This was solved.
The other client was deployed more than 3 months ago. We did the same thing and it just stuck at testing veeam transport. This is what we observed.
1. During re-installation, the veeamdeployment service is running and listening to port 6160. Meanwhile the veeamtransport service is running (based on systemctl status veeamtransport) but it is not listening to port 6162.
2. There's no network/firewall blockage. Port 6160 are 'telnet-able' from VBR to the Hardened Repository.
We have a lots other hardened repository running, but not from this recent ISO. It was prebuilt back then with installaton of bare Ubuntu and running the script to hardened back then which is downloaded from github community and it's still running like a beast.
For now we are still waiting for Veeam Support to reach back to us.
The issue was that the hardened repository suddenly disconnected last Sunday/Saturday. This happened to two deployment on a different client and it happen at the same time.
1 of the hardened repository was deployed recently only (1 month++) and we performed a reboot, and re-configure the hardened repository and it managed to remove both veeamdeployment and veeamtransport services and reinstall it back. This was solved.
The other client was deployed more than 3 months ago. We did the same thing and it just stuck at testing veeam transport. This is what we observed.
1. During re-installation, the veeamdeployment service is running and listening to port 6160. Meanwhile the veeamtransport service is running (based on systemctl status veeamtransport) but it is not listening to port 6162.
2. There's no network/firewall blockage. Port 6160 are 'telnet-able' from VBR to the Hardened Repository.
We have a lots other hardened repository running, but not from this recent ISO. It was prebuilt back then with installaton of bare Ubuntu and running the script to hardened back then which is downloaded from github community and it's still running like a beast.
For now we are still waiting for Veeam Support to reach back to us.
Statistics: Posted by johnnytan — Jul 09, 2025 4:18 am





