What's the location of the Proxy.xml file for the Linux backup proxies?

[t7MevELx0]

I've opened a case with Veeam support on this and I haven't received a response.

I have 12 Linux proxy VMs running the latest build and none of them have a Proxy.xml file in the /etc/veeam/backup365 dir.

This yields nothing:
sudo find / -type f -name "Proxy.xml" 2>/dev/null

Are these Linux proxy VMs grabbing their settings from somewhere else?

I have certain settings in there that let us use our storage. I'm hesitant to decommission the Windows proxies until I know where these Linux proxies are grabbing their configs from....

[Polina]

Which product build are you running?
Try searching for Proxy.ini

[t7MevELx0]

I do see Proxy.ini and I asked support about that but they insisted I should have a Proxy.xml file on an Ubuntu Linux VM running Veeam Backup for Microsoft 365 8.1.0.3503.

I have a storage validation setting I need to make sure is being honored.

Case #07620373

[t7MevELx0]

I just verified that these Linux backup proxies aren't honoring the <ObjectStorage SkipObjectStorageVersioningValidation="True" /> flag. There's no Proxy.xml file on the Ubuntu Linux proxy backup servers. I've placed all of them into maintenance mode and now I can create new backup repositories. It wasn't even giving me an error about objectstorage versioning. It would just spin validating for 30 mins when adding a backup repo and time out. Before proxy pools it would tell you what the error was - objectstorage versioning.

[edh]

Hi ,
I think you can use something like this. Im not 100% sure about the $xpath variable in your case.. becasue there's not a public list of variables to use or to do a fine tunning.

This for windows, but in case of linux , you can use check the help of Set-VBOConfigurationParameter. It works for apply pools settings at once.
This scripts take care of Proxy.xml in case of Windows Proxy or Linux Proxy (Proxy.ini)

Code: Select all

$xpath = "/Veeam/Archiver/ObjectStorage"
$key = "SkipObjectStorageVersioningValidation"      
$value = "True"

$proxys = Get-VBOProxy -Hostname XXXXXX
$pwd = ConvertTo-SecureString -String "" -AsPlainText -Force
$wincredential = $winserverCredentials = Get-Credential
Set-VBOConfigurationParameter -XPath $xpath -Key $key -Value $value -Proxy $proxy -WindowsCredential $wincredential -Restart

[t7MevELx0]

If that PS cmdlet sets the config in the Proxy.xml file then it won't work. I would also need to know what key/value to use and only Veeam support would know that. I'll have to wait for them to chime in. These Ubuntu Linux proxy servers don't have a Logs dir either. So no Proxy.xml file, and no Logs dir. I only have a Proxy.ini with very little in it. It just looks like the archiver service running and moving data without any settings to me.

There are a lot of other configuration settings in these xml files. So this is just an example. If I build a new Windows proxy, I just edit the Proxy.xml file so that these settings match. I'd do that here too.. if I had one to edit. I could use touch to create one, but I have no idea if the contents should be the same. I also don't understand why there's no file to begin with.

Edit: I found that the Linux proxies store the logs here: /var/log/veeam/backup365

I'm still waiting to hear back from support on how to set the config on a linux proxy.

[edh]

Example script for linux proxys.

Code: Select all

$xpath = "/Veeam/Archiver/ObjectStorage"
$key = "HTTPRequestTimeout"      
$value = "00.00:10:00"
$vboproxy = Get-VBOProxyPool -name "Name of proxy pool" 
$pwd = ConvertTo-SecureString -String "Pa$$word123" -AsPlainText -Force
$linuxcredential = New-VBOLinuxCredential -Account "Administrator" -ElevateAccountToRoot -IgnoreFingerprintCheck -Password $pwd
Set-VBOConfigurationParameter -XPath $xpath -Key $key -Value $value -Proxy $vboproxy -LinuxCredential $linuxcredential -Restart

Now you just need the Path of the value. And it will edit properly the Proxy.ini in your linux...

[t7MevELx0]

I'll wait to see what Veeam support says. They've sent a screenshot in Linux that clearly shows I should have a Proxy.xml file, not just a Proxy.ini file. The logs dir is also in the dir with that Proxy.xml file in their screenshot; mine looks nothing like that.

The contents of the Proxy.ini files looks nothing like the contents of the Proxy.xml file from a Windows system.

[t7MevELx0]

I've had a support case open with Veeam for this since Feb 28th. I'm still waiting to hear back on how these Proxy.ini files work.

The support engineer assigned to our platinum account gave me different values than the engineer assigned to the case. I'm trying to reconcile those differences right now.

I'm going to have to install a copy of 8.05, set the .xml file, upgrade and look at the Proxy.ini file myself for the converted values. It's become clear that this is so new that no one at Veeam has an answer for me.

Case #07620373

I think 8.1 should be pulled until all of the critical bugs are ironed out and support knows how the new version works.

[Polina]

Hi t7MevELx0,

The INI file contains the same information as XML. Its structure is organized into sections enclosed in square brackets, such as [Veeam.Archiver.Patching.Proxy], [Veeam.Archiver.Proxy] and so on. Under each section, you will find a list of corresponding parameters.

Is it what you are looking for?

[t7MevELx0]

I ended up fixing this myself after months of nothing going anywhere with support. I installed 8.05, set my config in the xml files, upgraded to 8.1, and then I pulled the config from the upgraded Proxy.ini files. Support ended up giving me wrong information and so I decided it's faster to find out myself vs waiting months longer for help that will never come.

[Polina]

May I ask what information exactly was misleading?

[t7MevELx0]

The information provided by support did not match what our assigned account engineer gave me. I installed version 8.05, configured the settings in Proxy.xml, upgraded to 8.1, and then retrieved the settings from the converted Proxy.ini. However, these settings did not align with the guidance I received from support, which I find misleading.

[Polina]

That's confusing indeed. We'll ensure it doesn't happen again, thanks for the heads-up.