Skip to main content

Powershell - VBO Health Check

  • November 10, 2021
  • 15 comments
  • 1606 views

SteveHeart
Forum|alt.badge.img+11

Update Jan 13th - Latest version available on 

https://github.com/yetanothermightytool/powershell/tree/master/vbo/vbo-health-checker

***

It's always recommended to open a support case as soon you're facing an issue with Veeam Backup for Microsoft Office 365. But as systems engineers, we somehow always want to know what happens under the hood :wink:

That's why I started writing a VBO Health Check script which quickly gives some useful information about the health of a Veeam Backup for Microsoft 365 setup. The script checks and reports possible issues/misconfigurations:

    - Backup Job Status per Job / Number of failed job
    - License expiration date
    - Check logs if throtthling occured on MS side
    - Possible slow backup due to slow backup repository
    - Proxy stuff (min. recommended CPU and Memory)
    - Check Windows event log for low memory conditions    
    - Logfile with the findings

Logfile gets stored in “C:\Scripts\Veeam\vbo\vbo_healthcheck_<computername>.log”


Note: The script is still "work in progress". Feedback welcome.

15 comments

StefanZi
Forum|alt.badge.img+3
  • Comes here often
  • November 10, 2021

Great work @SteveHeart - I ran that successfully for both my demo environments  :clap:


Mildur
Forum|alt.badge.img+12
  • Influencer
  • November 10, 2021

Thanks @SteveHeart 

I will try the script on my servers.


falkob
Forum|alt.badge.img+13
  • Veeam Vanguard
  • November 10, 2021

Hi @SteveHeart, the script runs perfectly fine !

One recommendation would be a “read-host” variable to decide where to store log files to as it is hardcoded at the moment. If you have the script on github, link it here I’m doing a PR then :D


SteveHeart
Forum|alt.badge.img+11
  • Author
  • Influencer
  • November 10, 2021

Hi @SteveHeart, the script runs perfectly fine !

One recommendation would be a “read-host” variable to decide where to store log files to as it is hardcoded at the moment. If you have the script on github, link it here I’m doing a PR then :D

 

Hi @falkob - No github yet. But now you can pass the logfile name using the “-Logfile” Parameter.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • November 10, 2021

Great script will have to run this on my test environment and see if we can use it.  Great work.


Ian Sanderson
Forum|alt.badge.img+7
  • Veeam Vanguard
  • November 15, 2021

Love it, thanks for sharing @SteveHeart :slight_smile:


k00laidIT
Forum|alt.badge.img+7
  • Veeam Vanguard
  • November 16, 2021

Looks great @SteveHeart ! Please do get this into github, would like to build this into some automated testing.


SteveHeart
Forum|alt.badge.img+11
  • Author
  • Influencer
  • November 17, 2021

Looks great @SteveHeart ! Please do get this into github, would like to build this into some automated testing.

@k00laidIT , @falkob - github is on its way. Stay tuned.


falkob
Forum|alt.badge.img+13
  • Veeam Vanguard
  • November 17, 2021

Nice !


damien commenge
Forum|alt.badge.img+5

Thanks for sharing


SteveHeart
Forum|alt.badge.img+11
  • Author
  • Influencer
  • November 18, 2021

@falkob, @k00laidIT - Now on github
https://github.com/yetanothermightytool/powershell/tree/master/vbo/vbo-health-checker

V1.1 with bugfixes and new functions


falkob
Forum|alt.badge.img+13
  • Veeam Vanguard
  • November 19, 2021

Forked :hearts:


  • New Here
  • March 17, 2022

Hi @SteveHeart ,

The script is working great. I just have a little problem. the Bottleneck give an error of cannot find path because it does not exist. Need help. Thank You

 

 


SteveHeart
Forum|alt.badge.img+11
  • Author
  • Influencer
  • March 18, 2022

Hi @azja09 ,

 

possibly some special characters or something else within your job or org name that makes the variable “unusable”. Could you PM me your backup job name as well as the organization name?

https://helpcenter.veeam.com/docs/vbo365/guide/vbo_rename_org.html?ver=60

 

Thanks.


SteveHeart
Forum|alt.badge.img+11
  • Author
  • Influencer
  • March 21, 2022

@azja09 : Found the “bug” and I am working on a solution.

 

Update: Newest version 1.3 now available.