Veeam 6 Vmattribute powershell question

[jkcouch]

How can I set my job notification options in Veeam 6 with powershell? I used to this this:

Code: Select all

vbrjob = Get-VBRJob | where {$_.name -eq $job.JobName}
$options = $vbrjob.GetOptions() 
$options.VmAttributeName = "Veeam"
$options.SetResultsToVmNotes = $true
$vbrjob.SetOptions($options)

Now since its broken out differently I cannot find the place to set the attribute since when you run this:

Code: Select all

vbrjob = Get-VBRJob | where {$_.name -eq $job.JobName}
$options = $vbrjob.GetOptions()
$options.NotificationOptions | gm

You get:
Name MemberType Definition
---- ---------- ----------
Equals Method bool Equals(System.Object obj)
GetHashCode Method int GetHashCode()
GetType Method type GetType()
ToString Method string ToString()
EmailNotification Property System.Boolean EmailNotification {get;set;}
EmailNotificationAddresses Property System.String EmailNotificationAddresses {get;set;}
SnmpNotification Property System.Boolean SnmpNotification {get;set;}


There are no options for setting the vmattributename. Is it hidden somewhere else or left out of 6.0? I see it in $options.Options.RootNode, but am unable to set it there.

Thanks in advance.

[Sethbartlett]

Here you go:

Code: Select all

$job = Get-VBRJob | ?{$_.name -eq "MyJob"}
$opt = $job.GetOptions()
$opt.ViSourceOptions.VmAttributeName = "whatever you want"
$opt.SetResultsToVmNotes = $true
$job.SetOptions($opt)

[Gostev]

Seth,

Code: Select all

{$_.name -eq "MyJob"}

is really old style with v6 though

I heard there is now -Name parameter in every cmdlet now, can you confirm it works?

[jkcouch]

HA! Thanks Seth. I found it this morning and was coming back to post it.

Gostev, yes it does work. Aswesome!

Code: Select all

get-vbrjob -name "MyJob" 

[Gostev]

Haha, this is officially the first time that I am teaching Seth something on our PowerShell capabilities (and not the other way around!)

[Sethbartlett]

Haha! Very true, very awesome! I never did a Get-VBRJob -? or any help on the cmdlets once I learned them the first time. Now I'll have to check them all Thanks.

[jteager]

I do wish I didn't have to put "-name" at all though. Not like get-vbrjob really takes any other parameters

[Gostev]

Is it even acceptable by PowerShell syntax best practices to omit parameter name?

[ThomasMc]

You can omit the name if the cmdlet parameter is positional but the ones in Veeam are named

Good cmdlet design recommends that the most-used parameters be declared as positional parameters so that the user does not have to enter the parameter name when the cmdlet is run.

MSDN Source

[jteager]

Ooh, cool doc. Thanks Thomas! As someone who actually does some C# on the side, I didn't even know that suite of info existed. Quite handy

[Sethbartlett]

Agreed Thomas, positional should be done. So we can do Get-VBRServer "serverName", Get-VBRJob "JobName", etc, etc.

[jteager]

It'd also be cool if -Name accepted wildcards...

[Gostev]

It does!

[Sethbartlett]

Such a troll...Haha, but you're right it does . FYI, the help documentation(Get-help Get-VbrJob -full) states that it doesn't accept wildcards