With the release of v9 hitting the Internets on Tuesday I’ve been a very busy man upgrading various Veeam Consoles, Proxies, and Repositories. With nearly 70 different locations to look after you can imagine the amount of proxies and repositories I have, both on and off site all requiring their respective Veeam services to be upgraded. Mix that together with a few slower WAN connections and I can almost bet that the automated component update that Veeam ships with will naturally fail on a couple servers.
Packages are in c:\Program Files\Veeam\Backup and Replication\Packages – copy them to your failed server and install 🙂
Failed to upgrade host components
When this happens to me usually I get some sort of error message like the following
For the most part, re-running the automated component update will fix the issue, but there are times when it fails, again, and again, and again. Usually by the third time I resort to manual intervention.
Manually installing the transport/mount service
First up you need to get a hold of the installation files. These are located on your Veeam Backup and Replication server under the path C:\Program Files\Veeam\Backup and Replication\Packages – You will find there the individual packages for each service that Veeam provides (mount, transport, tape, etc). Depending on what services your proxy is providing you may need an number of these. Since my server was acting as a repository as well as a proxy I simply needed the transport and mount server packages (VeeamTransport.msi and VeeamMountService.msi respectively). Also, don’t forget that Veeam relies heavily on the .NET framework so you must keep that updated as well – you can find the redistributable installation package for that within the packages folder along side the others (NDP452-KB2901907-x86-x64-AllOS-ENU.exe)
Installation is just like any other install – your typical Next->Next->Done type of scenario. Once you have ran the required packages head back to Veeam Backup and Replication. If you are still on the component update screen a ‘refresh’ should update the status of the packages – if not, a rescan of your server within the Backup Infrastructure section is required.
So that’s that – as it turns out the issue on why my installation was failing during the automated process was due to lack of disk space, but nonetheless this is good information to have – If you are looking for more information in regards the the new features within Veeam Backup and Replication v9 I’ve done a post here – feel free to check it out!.