Associated repositories will be preserved." To work around, in the management console remove this proxy from the infrastructure configuration, then configure this proxy anew, targeting at the machine with its new name.
#Windows alias for systemname Offline
If a Windows machine hosting backup proxy was renamed, this proxy will have the Offline status displayed in the management console. Obviously, proceed at your own risk, but I feel comfortable enough doing these sorts of things - which is why I thought I'd try.Įdit: I just noticed this " 11. From some more poking, there's also a Repositories XML file in C:\ProgramData\Veeam\Backup365 and a Repositories table in the ProxyDB too - So you'd probably want all those lining up and pointing at the same things, otherwise things are likely to go bang! I'd expect Path in the Repositories table to be reasonably safe too as the jobs all reference Id (Which is a GUID). What I've gathered is that if you leave the Id columns alone, it seems relatively safe to edit things like the Proxies table and change the Host, MachineName and Identity columns. Need to re-enter all the credentials for each organisation due to probably encryption keys.
Need to re-install/re-generate the API certificate.The downside of moving computers is there's 2 things that break (easy fix): They're in the same domain so authentication isn't an issue, though odds are I'd probably be able to figure that one out too if it came to it.
0 kommentar(er)
