Get-VBREPJob - Next Run Issue in v9

[Backerupper]

In v8 we could use the following code to see when the next run time was for an Endpoint job

Code: Select all

$epjobs = Get-VBREPJob
$job = $epjobs | select -First 1
$nextrun = $job.NextRun

In v9 the property is there but is not returning the correct date/time. I am getting the same date/time for all jobs (9/26/2015 10:00:00 PM).

Is this to be expected? Can we not rely on this property?

[veremin]

Checked on my installation and confirmed the said behaviour. It looks like a bug and we're currently investigating it more closely. Thanks.

[Backerupper]

FYI - this erroneous date (9/26/2015 10:00:00 PM) is also returned for configuration backup jobs

Code: Select all

$config = Get-VBRConfigurationBackupJob
$config.NextRun

[veremin]

Appears to be a bug as well. Both should be fixed in one of the next product versions. Thanks.

[Yukinobu]

Do you know the fixed oldest version of Veeam B&R and EP for this problem?

[veremin]

In my lab (VB&R 9.5 U1, VAW 2.0 beta) I don't face the said issues any longer.

[nsimao]

Hi team,

I have a customer trying to use the cmdlet Get-VBREPJob to return details his agent jobs managed by VBR 9.5 U3, which I understand is not yet supported.

Just wanting to find out if this is included in update 3a or 4?

[veremin]

Update 4. Thanks.