PowerShell • Re: Get-VBRRestorePoint broken since last update

Hi Stephan,

I checked both 12.2 and 12.3 for Get-VBRRestorePoint, the pipeline validations haven't changed. I think part of the confusion here is that Get-VBRRestorePoints tries to do parameter binding, Powershell decides on its own how to do the binding and it's a bit unpredictable.

This is an issue because the -Backup parameter has AllowEmptyCollection for one of the bindings so powershell won't error out here. Instead there is handling that if the parameter ends up being empty, all backups are returned, and this was true in 12.2 it looks.

I can't explain why you're only hitting this on 12.3.1, but honestly I would not do this in a script

>$Backup | Get-VBRRestorePoint

I'm not sure there's much of a benefit and we end up having to battle with powershell's pipeline behavior. Instead do

$rp = Get-VBRRestorePoint -Backup $backup

Directly using the parameter will validate NotNullOrEmpty, and should properly catch and continue.

Similarly, can you explain a bit more how you ended up with backups that have no restore points? I'm a bit confused how this scenario appeared and off the top of my head cannot think how to reproduce it.

Statistics: Posted by david.domask — Apr 16, 2025 9:59 am

---