Object reference not set to an instance of an object

[leeg123]

Just completed our first setup of veeam 7
Backups of VMware esx 5.0, all vms backup cleanly
When testing a SharePoint recovery I get this error "Object reference not set to an instance of an object"
No issues with file or full vm recovery testing
This error pops up as after right clicking on the SharePoint vm, and clicking on "Restore Microsoft Share Point Items"
The VM is Windows 2008 r2 and SharePoint is 2010
Any direction to follow to troubleshoot this?
MY Veeam backup PC is running within a 2008 R2 Server
The backup server is a VM but we aren't backing up the VM within veeam itself.

Thank you

Lee

[foggy]

Lee, R&D would like to take a look at your log files, please open a case with technical support and provide its ID here.

So am I understanding right that you can successfully perform all other types of restore over this very VM, however get the mentioned error message while trying to restore SharePoint items?

Thanks.

[leeg123]

Exactly

What’s interesting, if I select a file recovery, and then open the veeam explorer for SharePoint, I was able to manually browse for the SQL files for SharePoint and then I was able to get further into the restore process
Since I know very little about SharePoint, I cut my losses
My feeling is that maybe I need to setup veeam in advance to know where the SharePoint databases are
Basically the quick right click of SharePoint restore generates the error, but if I open the veeam explorer after doing file recovery, I can get it to work
I’m ok with that, but am curious if anyone has seen this
I can send screen shots if interested

[foggy]

Backing up the VM using application-aware image processing is sufficient for Veeam B&R to detect that SharePoint is installed inside the VM, no additional steps required. It would be great if you could provide the logs to support so we could take a look at the issue a bit closer. Thanks!

[TorEgil]

I've got the same issue, did you get a solution?

regards,
Tor Egil

[foggy]

Since OP did not provide the case ID, we cannot track this issue. Please contact support directly for your own investigation. Thanks.