Veeam Backup Validator run against Imported VBKs only

[resruss]

Hi,

So I wrote a script a while ago, before upgrading to Veeam 9.

Basically, once a quarter, we restore a tape from another site into our test Veeam environment.
We're only restoring the VBK and VBM file for each job from tape to disk, from Reversed Incrementals.

Back in v 8.0, it worked a treat and would email me the HTML reports.

Now in version 9, I get the following for each VM.
I know that the VMs are in fact available, as I've manually booted them and interacted with them using Instant VM Recovery, so I'm sure it's just a syntax change.

Anyone got any ideas where I'm going wrong?

Code: Select all

Veeam Backup Validator Version 9.0.0.0
Copyright (C) Veeam Software AG. All rights reserved.

Parameters:
    Backup ID:          {GUID}
    Backup name:       backup-name
    Format:             Html
    Restore point date: Friday, 12 February 2016
    Restore point ID:   {GUID}
    Restore point time: 7:00:00 PM
    Report:             c:\Powershell\VeeamValidation
    Silence:            no
    Skip:               no

Validating...

Validating VM...
    VM name:      vm-name
    Creation time: 12/02/2016 7:04:08 PM
    Backup type:   full
    Platform:      VMware
    OS name:       Red Hat Enterprise Linux 6 (64-bit)

Skipping VM vm-name': VM is unavailable.

Statistic:
    VM count:            1
    Incomplete VM count: 0
    Failed VM count:     1
    Files count:         0
    Total size:          0.0 KB

Validation failed.

The following VMs are corrupted:
 1. 'vm-name': VM is unavailable.

[Vitaliy S.]

Are you using a Linux repository by any chance?

[resruss]

Nope, the VMs are on a Windows Proxy repository, with transport role installed.

It's weird that it says unavailable, considering I was able to boot the VMs and interact with the guests, opened files, etc.

[alanbolte]

Would you mind posting your script? I'm curious.

[resruss]

Sure thing, I'm not convinced it is the issue, but I don't quite know where to start troubleshooting.

Edit: I should add, that when invoking the validator via command line without all the scripty goodness, it still doesn't work.

Code: Select all

#Set the sending email address and destination address
$SenderAddr = "user@domain.com"
$DestinationAddr = "user@domain.com"

#Set the email server
$SMTPServer = "smtp.domain.com"

######################################
#Do not edit anything below this line#
######################################

Add-PSSnapIn VeeamPSSNapin
$date = (Get-Date).AddDays(-1).ToString('dd-MM-yyyy')
set-location "C:\Program Files\Veeam\Backup and Replication\Backup"
$jobs = get-vbrbackup -Name *SearchString*
foreach ($job in $jobs)
{
$jobname = $job.name
$friendlyname = $job.metafilename

#This is to display the Job Names in the console for troubleshooting
write-output $jobname

#Set the Output file location
$VeeamOutputFile = "c:\Powershell\VeeamValidation-$date-$friendlyname.html"

#Runs the exe file with the necessary parameters 
.\veeam.backup.validator.exe /backup:"$jobname" /format:html /report:"$VeeamOutputFile"

#Set the location of the output file
$JobFile = $VeeamOutputFile

#Sends the output files to a recipient
send-mailmessage -from "<$SenderAddr>" -to "<$DestinationAddr>" -subject "Veeam Validation Report for $jobname" -body "Report Attached." -Attachments "$JobFile" -priority High -dno onSuccess, onFailure -smtpServer $SMTPServer
}

[Vitaliy S.]

The validator code didn't change between v8 and v9 versions, let our support team take a look at this situation live. Once you open a case, please let me know your case ID.

[resruss]

Thanks. Case number is 01752464.

[rmehta]

This is a known issue with version 9.0: case: 01725472, Vyacheslav from the 3rd level support gave me a new validator,exe and dll file and it worked afterwards.