vSphere 5.0 patch - issue

[chimera]

Hi,
We had upgraded from vSphere 4.1 to vSphere 5.0 a couple weeks ago however at the time had failed to check compatibility with Veeam. As a workaround at the time, I changed the backup jobs to backup the VM's direct from the hosts rather than via VC. Today I've downloaded/applied the vSphere 5.0 patch for Veeam but when I edit the jobs to backup off the Virtual Center server, I get an "Invalid SoapPath fullName:" error (eg: when clicking the + next to the VC server when adding virtual machines to a job)
Whats this error mean?
Cheers

[chimera]

Apologies, not a patch issue... I've just worked this one out myself, the error referred to a virtual template that sits on a datastore that resides on a SAN that has since been decommissioned (or rather, the SAN/LUN still exist, the datastore has just been disabled in vCenter for now). Removing the template from Virtual Center inventory has fixed this error. Hope this at least helps someone else out who may get the same thing!

[chimera]

First backup job test (which contains a few Citrix VM's) has come up with this error... which concerns me as its making reference to a "TEST-Win7Client" virtual machine that is not even in this particular Veeam backup job!

Publishing catalog session
Failed to delete oib '[vmname=TEST-Win7Client:creation_time=20/10/2011 7:18:35 p.m.:alg=Syntethic:id=9b347bc6-cb08-405a-84cc-ad326becd583:point_id=32803a69-ef6d-4dc3-aa09-abaf25ab452f:storage_id=9b2f9cf1-3d0a-4384-93c6-0c428e334c44]' from 'E:\Veeam\CitrixServers\Citrix Servers (all disks)2011-10-20T180044.vbk', redo 'E:\Veeam\CitrixServers\Citrix Servers (all disks)2011-10-19T180042.vrb'
Failed to execute stored procedure. Name: [[Backup.Model.UpdateOib]], Params: [@id = 5cfd7369-9d71-4836-b3fa-3143e6cebe41, @object_id = 057ac27b-65d6-41d0-8c9c-8c85c35e1052, @point_id = 67cc8d22-aa18-4471-b144-62049bc1e618, @storage_id = 9b2f9cf1-3d0a-4384-93c6-0c428e334c44, @link_id = , @is_corrupted = False, @is_consistent = True, @state = Nothing, @type = Full, @alg = Full, @inside_dir = c785a048-a357-4414-a23f-3859bed292ff (16), @creation_time = 19/10/2011 6:10:41 p.m., @vmname = TEST-Win7Client, @guest_os_info = <GuestInfo><Property Name="GuestOsName"><Value /></Property><Property Name="Ip"><Value /></Property><Property Name="DnsName"><Value /></Property><Property Name="ToolsStatus"><Value>NotRunning</Value></Property><Property Name="ToolsVersionStatus"><Value>NeedUpgrade</Value></Property></GuestInfo>, @memory = 1024, @approx_size = 25769803776, @process_id = -1, @has_index = False, @aux_data = <COibAuxDataVmware xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><Host ... DataVmware>].
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Second backup job (of a handful DMZ servers) direct from SAN, seems to be running along well so far though so the previous issue maybe isolated to that particular job or VM in that job.

[foggy]

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Most likely this error means that some operation with Veeam SQL database (backup file deletion according to retention policy) has timed out. Maybe SQL server was temporary unavailable at that moment. Please provide the full logs to our support team so they could locate and further investigate the issue. Thanks.