cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Exec 2010 R3 VM Backups not appearing in Resources to Restore

irishguy100
Level 2

Hi,

I have been asked to look into a backup exec platform using mostly VM backups now.  The system was ported from 2010 R2 to 2010 R3 and is fully patched.

When I choose a vm backup with unselect "Granular Restore" the backup is successfull but it is not displayed under View By Resource under Virtual Center and ESX Servers.

I have unticked both the date options and I have ran a backup to disk with the same options.  Neither are displayed in this location,  yet all backups are successfull and I can actually see the .vmdk files in the backup to disk location.

 

GRT based backups work fine and are listed by the servers NETBIOS name.

I have read about hotfixes for R2 but as this is fully patched I am running out of ideas.

Anyone know anything?

Regards,

J

3 REPLIES 3

irishguy100
Level 2

Hi,

 

Any ideas on this?  Its driving me nuts now! 

 

Anyone know how to remove a the Virtual Center from resources and have it re-added?

Ben_L_
Level 6
Employee

"I can actually see the .vmdk files in the backup to disk location." This tells me that GRT is still enabled for the job, sound like you turned off File Level GRT but not the application GRT.  If you click the Edit button on the VMware options section of the job are any of those 3 check boxes selected?

Regardless of if GRT is enabled or not you should still be able to see the restore selections of the VMDK.

Just to clarify, you're running Backup Exec 2010R3?  What version of vCenter and ESX?

irishguy100
Level 2

Hi there,

I have found the problem.  In the catresourcenamenode table in the BE Database there was a legacy Virtual Center listed with the same name as the one I was trying to use.

I noticed this by finding the following error logged in Tape Unit Event viewer each time I ran a VM Backup:

Update to catalog index (Catalog index database) failed.
Reason:  [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK_CatResourceNameNode'. Cannot insert duplicate key in object 'dbo.CatResourceNameNode'. cat_RecordSet::ExecuteBulkInsert()
e:\nicobar\5204r\becat\segodbc\seg_odbc.cpp(3113)
sp_sproc_columns CatResourceNameNodeProc

I removed reference to this and its child objects and all appeard once I restarted SQL + BE Services.