v11 - Get-VBRBackupRepository Space Properties

[Markus.K1985]

Hi,
some of my reporting scripts stopped working because of the missing Space Properties of the BackupRepository Object.

v10 Example:

Code: Select all

# Get All Backup Repositories Advanced
[Array]$RepoList = Get-VBRBackupRepository | Where-Object {$_.Type -ne "SanSnapshotOnly"} 
[Array]$ScaleOuts = Get-VBRBackupRepository -ScaleOut
if ($ScaleOuts) {
    foreach ($ScaleOut in $ScaleOuts) {
        $Extents = Get-VBRRepositoryExtent -Repository $ScaleOut
        foreach ($Extent in $Extents) {
            $RepoList = $RepoList + $Extent.repository
        }
    }
}
$RepoList | Select-Object Name, Path, `
@{Name="CachedTotalSpaceGB"; Expression= {[Math]::Round([Decimal]$_.info.CachedTotalSpace/1GB,2)}}, `
@{Name="CachedFreeSpaceGB"; Expression= {[Math]::Round([Decimal]$_.info.CachedFreeSpace/1GB,2)}} | Format-Table -AutoSize

Any recommendation for an alternative way to gather these details?

Best regards
Markus

[oleg.feoktistov]

Hi Markus,

These properties were moved to another class.
Here is the way to get them:

Code: Select all

$container = $extent.Repository.GetContainer()
$container.CachedFreeSpace
$container.CachedTotalSpace

Thanks,
Oleg

[k00laid]

Hi Oleg,

I've got to ask, what is the rationale here? I'm working through using this and its if anything made the coding harder for standard usage. If I wanted to pull basic repo info in v10 I could do something like the following:

Code: Select all

Get-VBRBackupRepository | Select-Object Name, Id, @{n='PerVM';e={$PSItem.Options.OneBackupFilePerVm}},@{n='totalSpace';e={$PSItem.Info.CachedTotalSpace / 1TB}}, @{n='freeSpace';e={$PSItem.Info.CachedFreeSpace / 1TB}}

Now I need to wrap each of these items in a method statement to do the same.

Code: Select all

$Repos = get-vbrbackuprepository
$RepoDetails = foreach ($repo in $Repos) {
    [PSCustomObject]@{
        'Name'      = $Repo.Name
        'ID'        = $Repo.ID
        'Size'      = $Repo.GetContainer().CachedTotalSpace.InBytes / 1GB
        'FreeSpace' = $Repo.GetContainer().CachedFreeSpace.InBytes / 1GB
    }
} 
$RepoDetails

In the end you are just making it that much harder to consume data via powershell it seems. One liners go out the window for general day to day administration. Also I know I could have just specified .InGigabytes but standard practices die hard.

[jhoughes]

Also, specifying .InGigabytes will lead to some factor of rounding which is not as easily identifiable.

Jim, based on our conversation with your reporting against a very large number of repositories, the loss of that detail could also cause significant calculation issues, or real capacity issues over time.

I would still suggest using the most accurate form of the detail data, and only perform the rounding as you are comfortable with for easily reporting in a visible fashion; this still gives you the capability of staying entirely granular as needed.

[oleg.feoktistov]

Hi Jim,

Some older cmdlets like Get-VBRBackupRepository, Get-VBRJob, Get-VBRBackupSession etc. return objects of core classes (those with "C" prefix). When implementing new cmdlets now, we avoid this practice and stick to placing new classes with "VBR" prefix under a separate namespace, which is usually Veeam.Backup.Powershell.Infos. Those classes have fixed properties and keep references to internal classes to a minimum. Core classes are great and often very informative, but, in fact, they are more related to C# and .NET than to Powershell. Their methods and properties can be used in different parts of the code. So, if business logic changes, it may lead to properties/method relocation or else. This is what you've encountered.
Now, I'm not fully aware of why these particular properties were moved, but I do see that it is related to platform integration.
So, no rationale here. Core classes just don't have one if it comes to API contract compliance.
I do believe, though, that sooner or later we'll be able to wrap them all in VBR* classes, and I'll start sleeping at night.

Kind regards,
Oleg

[Markus.K1985]

Thank you all very much. This has helped a lot.

[verk80]

Hey guys, thank you for the clarification on this from me as well. I had created some reports that weren't working since the upgrade to v11, and I knew the info wasn't in the right place anymore, but I wasn't able to find it. I greatly appreciate it!

[MJlee]

I used to able to get the veeam repository total capacity and free space by running the following script by using the old Veeam powershell snapin. Since I upgraded to Veeam 11 and start using the new powershell module, the script doesn't work anymore.

#repo total space TB
[math]::Round( (Get-VBRBackupRepository -name $vrepo).info.CachedTotalspace/1099511627776,0)
#repo free space TB
[math]::Round( (Get-VBRBackupRepository -name $vrepo).info.CachedFreeSpace/1099511627776,1)

If you do `(Get-VBRBackupRepository -name $vrepo).info`, you can't see the CachedTotalspace and CachedFreeSpace object anymore.

Is there any other way I can retrieve the repository usage/capacity over powershell?

[Natalia Lupacheva]

Hi @MJlee,

Moved your post to the existing thread to keep the similar issues together.
Please take a look at the reply and the discussions above.

Thanks!

[tomhkr]

With the old VeeamPSSnapin I used to run

Code: Select all

Get-VBRBackupRepository

and expand the Info parameter to get CachedTotalSpace and CachedFreeSpace

This no longer works since updating to V11 and the module-based Veeam.Backup.PowerShell. I get the respositories but the CachedTotalSpace and CachedFreeSpace are no longer under the Info parameter.

How is it supposed to work to fetch avaliable space on a repository in the new module based cmdlets?

[oleg.feoktistov]

Hi,

I merged your post with the existing thread. Please check the answers above.

Thanks,
Oleg

[MartinO]

Is there any documentation for these new classes? I'm building out our documentation using the PS reference documentation but there's no mention of these classes and a quick Google doesn't bring anything up other than this thread.

I'm a bit of a newbie to this level of scripting so any reference material I can get my hands on would be brilliant!

[oleg.feoktistov]

Hi Martin,

These are internal .NET classes, which are not officially supported. It means that you won't find any documenation on them, but a mention as a workaround only, usually in scope of our forum. So, in such cases this is a place to seek and ask.

Hope it clears things up.

Thanks,
Oleg

[masonit]

Hi!

Trying to get freespace from sobr extents (Get-VBRRepositoryExtent). There is no "GetContainer()" method for extents. Any workaround for this?

\Magnus

[oleg.feoktistov]

Hi Magnus,

Yes, you need to access Repository property on extent to get to GetContainer() method. See an example in this post.

Best regards,
Oleg

[masonit]

Ok, thanks.

Worked now. I tried to use GetContainer() on wrong property before..

\Magnus