Veeam v8 – My Veeam Report turns 2.0!

MVR2.0Find the latest version here.

It’s hard to believe that it has been two years since I posted my first version of My Veeam Report.  It’s amazing how times flies and interesting to see the progress that has been made. I am extremely grateful for all the feedback provided by folks who see the benefit of running such a report. The feedback has certainly pushed me to improve the report over time – please, keep it coming!

This update includes three major enhancements as well as a few smaller tweaks and polish. The two improvements I think will most benefit folks are the ability to query the Veeam database for repository info as well as the addition of Endpoint backup sessions. The last new addition is reporting for Restore sessions (not sure why this one slipped by for so long).

Lets start with the repository info.  If you have been following along, this has historically been a challenge as Veeam does not expose this info via their PowerShell snapin. So we have had to be creative when querying storage for things like total space, free space, etc. With some help from tsightler on the Veeam forums we can now query the Veeam database directly – so we can see what Veeam see’s. That’s the good news.  The not so good news is that this will come with some potential issues. One issue is that this method is absolutely not supported by Veeam (no vendor likes you digging into their db directly). This means that they could easily break this function with a patch or update. The other issue is that we need to ensure a connection to the database which could be configured in many different ways (local, remote, etc). The script is setup to use Windows authentication of the user running the script which should cover the majority of use cases. Unfortunately I am not going to be able to troubleshoot individual configurations, so this is going to be a bit of an advanced setup.  You can still choose to use the old way if you can’t seem to get the SQL connection to work (by default the old way is used unless specified in the User Variables section).

Next we have Endpoint backups – I surely hope by now you have looked into this awesome addition to the Veeam family. Using a Veeam repository for your Endpoint backups has many advantages and allows us to grab session information with PowerShell as well. Though the information provided is much more basic than what we can retrieve for VM backups, it is still a nice way to keep tabs on these new jobs.  I’m hoping Veeam will expand on the information provided in the future (maybe v9?).

Lastly – Restore sessions. It is always a good idea to keep tabs on when Restore sessions are run, especially if you work in an environment where multiple people have access to the VBR server. I’ve added a section for completed as well as running Restore sessions.

I’d like to note as well that through some clean-up I can assure you that Backup Copy jobs and Replica jobs are not included in this version.  Some Backup Copy jobs ended up in previous versions, mostly due to my oversight, not purposely.  The reason is simple – I don’t happen to use either of these types of jobs.  This makes it very hard to ensure the code is correct – the last thing I want to do is report incorrect/unverified data. As mentioned, the code has been cleaned up a bit and this info could be included.  I will have to see if I have the time in the future to setup some test jobs and add them to the report. Let me know if this is something that you would really like to see. I’ll also add that this report is for VMware only – no Hyper-V support.  Though the same details should be able to be retrieved for a Hyper-V setup…I don’t run Hyper-V…making it too difficult of a task to ensure the report is correct. Though I’m unable to provide a report that is going to work for every possible scenario, I’m happy to share what I have put together for my own use.

As before, be sure to give the user variables section a good once over as there have been a few changes and many additions. By default most things are turned on so on first run you can get a look at everything – feel free to trim back and customize for your needs. There are a few items that you must specify prior to running like the vCenter name (as seen in VBR), the paths to the two Veeam files and the email section (if you want to send a copy of the report via email).

Here’s a list of the included changes:

  • Misc minor tweaks/cleanup
  • Proxy host IP info now always returns IPv4 address
  • Added ability to query Veeam database for Repository size info
  • Added report section – Backup Job Status
  • Added option to show detailed Backup Job/Session information (Avg Speed, Total(GB), Processed(GB), Read(GB), Transferred(GB))
  • Added report section – Running VM Restore Sessions
  • Added report section – Completed VM Restore Sessions
  • Added report section – Endpoint Backup Results Summary
  • Added report section – Endpoint Backup Job Status
  • Added report section – Running Endpoint Backup Jobs
  • Added report section – Endpoint Backup Jobs/Sessions with Warnings or Failures
  • Added report section – Successful Endpoint Backup Jobs/Sessions

Here’s a list of the requirements:

  • Veeam v8 (with latest update)
  • PowerShell v2
  • VMware Infrastructure hosting VMs

Script can be downloaded from here.

Advertisements

37 thoughts on “Veeam v8 – My Veeam Report turns 2.0!

  1. Andreas

    First – great job – Thanks! I just found your script a few weeks ago and it is exactly what I need 🙂 One additional idea: can you add a section with excluded VM’s. I think it would be interesting to see which VMs are not in the backup because they where put on the exclude list of the Job …

    Reply
  2. Michael

    Hi,

    Nice, nice, nice

    Thanks a lot for the new version.
    Now I have everything I need.

    Thank you again…

    Best regards from South Tyrol
    Michael

    Reply
  3. virgilwashere

    Shawn,
    I’ve forked your gist and made some not-so-minor modifications. But the gist diff is easy enough to follow.

    Feedback appreciated.

    Reply
  4. smasterson.com@jezza1.com

    Hi Shawn, great work and a big fan of using your report 2.0 in Veeam8. Any word or work for it to run with Veeam 9?

    Reply
    1. smasterson Post author

      v9 support will depend on a few things
      1) I’ll need to install and start testing/working with it (could be a month or two to ensure bugs are squashed – though Veeam typically does a decent job)
      2) I’ll need to assess what has changed and how much is broken – this will likely be the biggest factor

      Stay tuned!

      Reply
      1. Daniel

        Hi Shawn,
        I did some quick testing with your V2 script and Veeam V9. The most crucial part (protected/unprotected VMs) still works, but unfortunately the sections Repository Details, Proxy Details and License seem to be broken (no result in the html file, but lots of red PowerShell error messages). Do you want me to send you details? In this case, just drop me a message.

    2. Dean

      Any update on this working with version 9? It looks like it has everything that we would need but we get the “Warning: This cmdlet is obsolete, use Find-VBRViEntity instead” followed by a ton of red text with “you cannot call a method on a null-valued expression”. We The report comes in and is “mostly” accurate but we see that it’s reporting VM’s that don’t have any successful backups. We can see in the Veeam console that this isn’t true.

      Please, PLEASE release the new script! Did I say PLEASE already?!

      Thanks,
      Dean

      Reply
      1. smasterson Post author

        Hi Dean
        I’m happy to say that work is in progress for v9!
        Re: Warning about obsolete command – this is as expected and can be ignored
        Re: tons of red text – cleaning this up now.
        Re: “mostly” accurate – can you elaborate on what you mean here? I’m not seeing any inconsistencies myself.

        Thanks!

      2. Dean

        Hi John,
        That’s all great news. The “mostly” statement is that I did VMs listed as having no successful backups even though we did have successful backups. Although, you can disregard this as I think it was a mistake made on my end because I’ve ran the report several times since posting and it appears to be all correct. The fact that we were doing some experimentation and troubleshooting with Veeam support and Tegile could have caused the false positive.

        So at this point, we can just ignore the red and warning and everything seems accurate… This is perfectly fine with us. Thank you very much for all of your hard work on this!

        Dean

  5. John

    Hello Shawn,

    is it possible to exclude backup jobs from appearing in the report ?
    (for example, if they’re not scheduled and we don’t want to see them. I tried to exclude VMs but the backup jobs still appear).

    Thanks for your amazing work!

    Reply
    1. smasterson Post author

      Hi John
      The only place an inactive job should show up is in the Backup Job Status section which is simply a status of ALL jobs (similar to what is seen in the console).
      The Successful Sessions/Jobs and Sessions/Jobs with Warnings or Failures sections should only show sessions/jobs run within your given time-frame.
      HTH

      Reply
  6. Alan

    Hi Shawn, awesome report! Love the Job Status and Backup Sessions. I just updated to v9 and it looks like the Repository Details, Proxy Details, and License/Support Renewal info are broken with Veeam’s database changes. Still checking it out on our end! Again Great Job!

    Reply
    1. smasterson Post author

      Thanks for the heads up!
      The license section should break, so no surprise there. Repo and Proxy details should be easy enough to fix (fingers-crossed).
      Seems as though the bulk of it is still working (wahoo!) so we should be in good shape.
      I should have time in the next few weeks to take a stab at the upgrade myself. Will let you know when I do.
      Thanks!

      Reply
  7. John

    Hello Shawn,

    i have a new question about your script, is it possible to add/show “Backup to Tape” in the report ?

    Thanks a lot 🙂

    Reply
  8. Marco

    Can you extract just the part of the script that would give back the Support Days remaining as an integer value, so I could add this script part to our monitoring? Then I could monitor all our Veeam consoles through Zabbix in one place and have an overview about the remaining days?

    Reply
  9. Yann

    Hi,

    Thanks for this amazing script, it’s very help full.
    I have question, i can exclude vcenter folder and vm but if i want exclude certain job backup.

    I try to explain i will generate the same report but for a specific Backup Job and Vms.

    I’m sorry, i just begin in powershell.

    Thanks for your help

    BR

    Reply
    1. smasterson Post author

      Hi Yann
      There are certain parts of the report that do not work well with a single job in mind. Therefore I have stayed clear (not that it is not possible).

      Reply
  10. Prabhat

    Hii, I am new to powershell and scripts 😦
    Getting below error when I am running this script
    ************************************************************************************************************
    Get-VBRLocalHost : The term ‘Get-VBRLocalHost’ is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At C:\S12HKGMUTBAKPR1.ps1:252 char:14
    + $vbrServer = Get-VBRLocalHost
    + ~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRLocalHost:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRViProxy : The term ‘Get-VBRViProxy’ is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At C:\S12HKGMUTBAKPR1.ps1:254 char:16
    + $viProxyList = Get-VBRViProxy
    + ~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRViProxy:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRBackupRepository : The term ‘Get-VBRBackupRepository’ is not recognized as the name of a cmdlet, function,
    script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
    correct and try again.
    At C:\S12HKGMUTBAKPR1.ps1:256 char:13
    + $repoList = Get-VBRBackupRepository
    + ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRBackupRepository:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRBackupSession : The term ‘Get-VBRBackupSession’ is not recognized as the name of a cmdlet, function, script
    file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
    and try again.
    At C:\S12HKGMUTBAKPR1.ps1:258 char:12
    + $allSesh = Get-VBRBackupSession
    + ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRBackupSession:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRRestoreSession : The term ‘Get-VBRRestoreSession’ is not recognized as the name of a cmdlet, function, script
    file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
    and try again.
    At C:\S12HKGMUTBAKPR1.ps1:260 char:13
    + $allResto = Get-VBRRestoreSession
    + ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRRestoreSession:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRJob : The term ‘Get-VBRJob’ is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At C:\S12HKGMUTBAKPR1.ps1:272 char:14
    + $allJobsBk = Get-VBRJob | ? {$_.JobType -eq “Backup”}
    + ~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRJob:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBREPJob : The term ‘Get-VBREPJob’ is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At C:\S12HKGMUTBAKPR1.ps1:303 char:14
    + $allJobsEp = Get-VBREPJob
    + ~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBREPJob:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBREPSession : The term ‘Get-VBREPSession’ is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At C:\S12HKGMUTBAKPR1.ps1:306 char:14
    + $allSeshEp = Get-VBREPSession
    + ~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBREPSession:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRJob : The term ‘Get-VBRJob’ is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At C:\S12HKGMUTBAKPR1.ps1:321 char:12
    + $repList = Get-VBRJob | ?{$_.IsReplica}
    + ~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRJob:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Get-VBRServer : The term ‘Get-VBRServer’ is not recognized as the name of a cmdlet, function, script file, or operable
    program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At C:\S12HKGMUTBAKPR1.ps1:610 char:16
    + $vcenterobj = Get-VBRServer -Name $vcenter
    + ~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRServer:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Find-VBRObject : The term ‘Find-VBRObject’ is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At C:\S12HKGMUTBAKPR1.ps1:611 char:12
    + $vmobjs = Find-VBRObject -Server $vcenterobj |
    + ~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Find-VBRObject:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Unable to find type [Veeam.Backup.Core.CHierarchyObj]. Make sure that the assembly that contains this type is loaded.
    At C:\S12HKGMUTBAKPR1.ps1:617 char:2
    + $jobobjids = [Veeam.Backup.Core.CHierarchyObj]::GetObjectsOnHost($vcenterobj.id …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (Veeam.Backup.Core.CHierarchyObj:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

    Get-VBRBackupSession : The term ‘Get-VBRBackupSession’ is not recognized as the name of a cmdlet, function, script
    file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
    and try again.
    At C:\S12HKGMUTBAKPR1.ps1:638 char:17
    + $vbrsessions = Get-VBRBackupSession | Where-Object {$_.JobType -eq “Backup” -an …
    + ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-VBRBackupSession:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Exception calling “Add” with “2” argument(s): “Key cannot be null.
    Parameter name: key”
    At C:\S12HKGMUTBAKPR1.ps1:569 char:18
    + $vservers.add($($script:vbrserver.realname),”VBRServer”)
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentNullException
    *****************************************************************************************************************

    Reply
  11. Prabhat

    Hii,

    I am using VEEAM version 8 and previously script was not working as there was some issue with the Veeam Powershell toolkit. This was fixed with the help from the Veeam Support. Now when I was trying to run the script it was giving error with the ‘Get-VBREPJob’ & ‘Get-VBREPSession’ as these command is not available in the Get-VBRCommand.
    I have changed it to ‘Get-VBRJob’ & ‘Get-VBRSession’ as these commanda were available in the Get-VBRCommand. Now while running the script I am getting below error.
    I am very much new to these scripts but trying to get it done.

    Any help will really be appreciated..

    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    cmdlet Get-VBRSession at command pipeline position 1
    Supply values for the following parameters:
    Job:
    @ I press enter as it was asking for the Job details
    Get-VBRSession : Cannot bind parameter ‘Job’. Cannot convert the “” value of type “System.String” to type
    “Veeam.Backup.PowerShell.Infos.VBRJob”.
    At D:\new 6.ps1:307 char:14
    + $allSeshEp = Get-VBRSession
    + ~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (:) [Get-VBRSession], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Veeam.Backup.PowerShell.Cmdlets.GetVBRSession

    Find-VBRObject : Cannot validate argument on parameter ‘Server’. The argument is null. Provide a valid value for th
    argument, and then try running the command again.
    At D:\new 6.ps1:612 char:35
    + $vmobjs = Find-VBRObject -Server $vcenterobj |
    + ~~~~~~~~~~~
    + CategoryInfo : InvalidData: (:) [Find-VBRObject], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Veeam.Backup.PowerShell.Command.FindVBRObject

    Cannot convert argument “hostId”, with value: “”, for “GetObjectsOnHost” to type “System.Guid”: “Cannot convert nul
    to type “System.Guid”.”
    At D:\new 6.ps1:618 char:2
    + $jobobjids = [Veeam.Backup.Core.CHierarchyObj]::GetObjectsOnHost($vcenterobj.id …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [], MethodException
    + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument

    Exception calling “GetFolder” with “1” argument(s): “Exception from HRESULT: 0x800A004C (CTL_E_PATHNOTFOUND)”
    At D:\new 6.ps1:414 char:33
    + $folder = $fso.GetFolder($r.Path)
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ComMethodTargetInvocation

    Get-Service : Cannot open Service Control Manager on computer ‘10.2.102.90’. This operation might require other
    privileges.
    At D:\new 6.ps1:594 char:13
    + $output = Get-Service -computername $obj -Name “*Veeam*” -exclude “SQLAgent*” …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Get-Service], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.GetServiceCommand

    Exception calling “Send” with “1” argument(s): “Failure sending mail.”
    At D:\new 6.ps1:1156 char:9
    + $smtp.send($msg)
    + ~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : SmtpException
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

    Reply
    1. smasterson Post author

      Please be sure you are running version 2 of the script. Your first error is on Get-VBRSession which was not introduced until VBR v9 (and script version 9.0.1).
      Also Get-VBREPJob & Get-VBREPSession should be available in VBR v8 – be sure you are running the last/latest patch for VBR v8.

      Reply
      1. Prabhat

        Hello,

        Thanks for you prompt reply. Appreciate it..
        Latest available patch for Veeam Backup & Replication 8 on Veeam Official site is 8.0.0.2084 and My Veeam Server is already on this version.

        Now, when I am executing Get-VBRCommand to list the available commands below Get-commands are available in which I cannot see Get-VBREPJob & Get-VBREPSession 😦
        @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
        Cmdlet Get-VBRBackup VeeamPSSnapIn
        Cmdlet Get-VBRBackupRepository VeeamPSSnapIn
        Cmdlet Get-VBRBackupSession VeeamPSSnapIn
        Cmdlet Get-VBRCloudGateway VeeamPSSnapIn
        Cmdlet Get-VBRCloudProvider VeeamPSSnapIn
        Cmdlet Get-VBRCloudTenant VeeamPSSnapIn
        Cmdlet Get-VBRCredentials VeeamPSSnapIn
        Cmdlet Get-VBREncryptionKey VeeamPSSnapIn
        Cmdlet Get-VBRFailoverPlan VeeamPSSnapIn
        Cmdlet Get-VBRFilesInRestorePoint VeeamPSSnapIn
        Cmdlet Get-VBRHvProxy VeeamPSSnapIn
        Cmdlet Get-VBRHvServerNetworkInfo VeeamPSSnapIn
        Cmdlet Get-VBRInstantRecovery VeeamPSSnapIn
        Cmdlet Get-VBRJob VeeamPSSnapIn
        Cmdlet Get-VBRJobObject VeeamPSSnapIn
        Cmdlet Get-VBRJobObjectVssOptions VeeamPSSnapIn
        Cmdlet Get-VBRJobOptions VeeamPSSnapIn
        Cmdlet Get-VBRJobProxy VeeamPSSnapIn
        Cmdlet Get-VBRJobScheduleOptions VeeamPSSnapIn
        Cmdlet Get-VBRJobVSSOptions VeeamPSSnapIn
        Cmdlet Get-VBRLocalhost VeeamPSSnapIn
        Cmdlet Get-VBRReplica VeeamPSSnapIn
        Cmdlet Get-VBRRestorePoint VeeamPSSnapIn
        Cmdlet Get-VBRRestoreSession VeeamPSSnapIn
        Cmdlet Get-VBRServer VeeamPSSnapIn
        Cmdlet Get-VBRSession VeeamPSSnapIn
        Cmdlet Get-VBRTapeBackup VeeamPSSnapIn
        Cmdlet Get-VBRTapeDrive VeeamPSSnapIn
        Cmdlet Get-VBRTapeJob VeeamPSSnapIn
        Cmdlet Get-VBRTapeLibrary VeeamPSSnapIn
        Cmdlet Get-VBRTapeMediaPool VeeamPSSnapIn
        Cmdlet Get-VBRTapeMediaPoolOptions VeeamPSSnapIn
        Cmdlet Get-VBRTapeMedium VeeamPSSnapIn
        Cmdlet Get-VBRTapeServer VeeamPSSnapIn
        Cmdlet Get-VBRTapeVault VeeamPSSnapIn
        Cmdlet Get-VBRTaskSession VeeamPSSnapIn
        Cmdlet Get-VBRViProxy VeeamPSSnapIn
        Cmdlet Get-VBRViReplicaReIpRule VeeamPSSnapIn
        Cmdlet Get-VBRViServerNetworkInfo VeeamPSSnapIn
        Cmdlet Get-VBRWANAccelerator VeeamPSSnapIn
        Cmdlet Get-VSBApplicationGroup VeeamPSSnapIn
        Cmdlet Get-VSBHvVirtualLab VeeamPSSnapIn
        Cmdlet Get-VSBJob VeeamPSSnapIn
        Cmdlet Get-VSBJobOptions VeeamPSSnapIn
        Cmdlet Get-VSBJobScheduleOptions VeeamPSSnapIn
        Cmdlet Get-VSBSession VeeamPSSnapIn
        Cmdlet Get-VSBTaskSession VeeamPSSnapIn
        Cmdlet Get-VSBVirtualLab VeeamPSSnapIn
        @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

        And I am using your script with subject line (Veeam v8 – My Veeam Report turns 2.0!)

        Please update..
        Thanks a lot

  12. voodoo

    Trying to run the report, but are getting an error here…

    Find-VBRViDatastore : Cannot validate argument on parameter ‘Name’. The argument is null or empty. Provide an argument
    that is not null or empty, and then try the command again.

    Any idea ? – this is current only Hyper-V setup, does the script only support VMware or ?

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s