Skip to main content

There are a lot of new PowerShell cmdlets for VBR alone - without agents and explorers. in v11 we have 1178, in v12 1334 cmdlets. So the list is too long to show here. Categories I could see:

  • GFS scheduling options
  • Hyper-V Surebackup/Instant Recovery
  • CDP
  • Tape … I have to check separately :)
  • Application Groups
  • Oracle

Another nice feature is that we now can see PowerShell commands at the end of wizards.

In older versions we saw parameters for Veeam.Backup.Manager.exe.

 

I love this!  It allows you to see how they structure the PS commands and also to copy them for use as well as learning. 😎


I love this!  It allows you to see how they structure the PS commands and also to copy them for use as well as learning. 😎

Same here, and will make things easier to automate.


I love this!  It allows you to see how they structure the PS commands and also to copy them for use as well as learning. 😎

Same here, and will make things easier to automate.

Absolutely.  We get bonuses if we help automate things so I will be going nuts. 🤣


Structuring is great and the example commands are very good, too. The standalone Linux agent has this,  too.

I am waiting for better cmdlet supprt for the application plugins. As far a I have seen there are some included with V12. 😎👍🏼


Structuring is great and the example commands are very good, too. The standalone Linux agent has this,  too.

I am waiting for better cmdlet supprt for the application plugins. As far a I have seen there are some included with V12. 😎👍🏼

Yes, they are!


I love this!  It allows you to see how they structure the PS commands and also to copy them for use as well as learning. 😎

Same here, and will make things easier to automate.

Absolutely.  We get bonuses if we help automate things so I will be going nuts. 🤣

Great idea to get admins to script 😂


Great to see Powershell improvents 👍

Regarding the summary, I've always used it to get the job GUID in case a job got stuck; then you can kill the corresponding process. While it's much more useful to show a powershell command, where will I now find the GUID? I know the answer, via Powershell 🤣


I love this!  It allows you to see how they structure the PS commands and also to copy them for use as well as learning. 😎

like MS when install roles\feature DCpromo etc. nice!


I love this!  It allows you to see how they structure the PS commands and also to copy them for use as well as learning. 😎

like MS when install roles\feature DCpromo etc. nice!

Yes exactly like that as it brought back those installs. 😂


Great to see Powershell improvents 👍

Regarding the summary, I've always used it to get the job GUID in case a job got stuck; then you can kill the corresponding process. While it's much more useful to show a powershell command, where will I now find the GUID? I know the answer, via Powershell 🤣

Good point! For sure this was the fastest way to get GUID 😀


Comment