Open mogilomen opened 1 week ago
I have the same problem and need a solution across all organizations. Additionally, I encounter an issue when adding more than 4-5 organizations: the sensor status fluctuates between UP and Warning, displaying the following message:
"XML: The returned XML does not match the expected schema. (code: PE233) -- JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)"
Any insights or solutions would be appreciated.
Hi Stefan How can I customize the script so that it monitors all organizations in Veeam? If I want to monitor all 40 organizations individually, the requests overload the server.
Hi Monika Just to be sure. You would like to use the skript without the -orgName parameter and then have the results for all companies in one sensor. Right?
The actual skript overloads the which server? The Veeam server or the PRTG Server?
Kind regards, Steff
Hello Steff
Yes exactly, I want to use the script for all organizations in Veeam.
If I enter each organization with its own sensor, I get the same error as Florian reported yesterday from the fifth organization onwards. I think the Veeam server is then overloaded with the requests.
Kind regards Monika
Hello Monika
Would you mind to set the sensor to save the result and post it here?
Whats the sensors interval? Mine is set to 4 hours.
What info would you like to get if the skript pulls the info for every company?
Does the skript work if you set -jobsOnly $true
?
Hello Steff
The individual jobs work with the “Save result” setting. I have already created 14 and they are all green!
The parameter -jobsOnly $true does not work.
For a “general” script, the information of the current “individual” jobs would be sufficient. So the status, last execution, transferred and the information of the repositories.
But since the individual ones now work, I no longer need the script with all organizations. :-)
Thank you very much for your help!
Hello Steff
I celebrated too soon. The errors (currently still warnings) are back:
Hi Monika
Could you please post the saved result for one of the failed sensors? Make sure to delete any sensitive data ;-)
Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file names are Result of Sensor [ID].txt and Result of Sensor [ID].Data.txt. This setting is for debugging purposes. PRTG overwrites these files with each scanning interval.
Hi Steff
Enclosed are the desired logs: Result of Sensor 21818.txt Result of Sensor 21818.Data.txt
Kind regards, Monika
Hi Monika
Could you try to run the script directly within powershell?
.\PRTG-veeam-backup-MS365-tenant.ps1 -apiUrl "https://<yourserver>:4443/" -username "localhost\administrator" -password "XXXXXXXXX" -orgName "XXXXXXXXX.onmicrosoft.com" -ignoreSSL "true" -listOrgs $true
??
What Windows Version do you run the script on? Sorry, got a lot of questions to find the solution...
Kind regards, Steff
Hello Steff
The script can be executed directly in PowerShell. However, as soon as there are more than 5 sensors, the script also fails directly from PowerShell.
The organization exists in Veeam. The script works perfectly if I “only” use 5 sensors. But as soon as there are more than 5, the Veeam server blocks and apparently can no longer find the organization.
The PRTG server is Windows Server 2016 and the Veeam server is Windows Server 2022
OK Perhaps this may help https://helpcenter.veeam.com/docs/vac/rest/throttling_config.html?ver=81
or eventually this?
I don't think it's only a skript issue. I do know one company which has at least 25 Sensors active.
Throttling could be the problem. However, I have not found a way to customize this in a file in Veeam Backup Microsoft 365. The link is for the Service Provider Console.
The second link is not the problem, as the connection is basically working.
I think the only thing that helps is a script with all organizations in a sensor.
Hi Stefan How can I customize the script so that it monitors all organizations in Veeam? If I want to monitor all 40 organizations individually, the requests overload the server.
Best regards Monika