how do I fix these 2 warnings

[adelatorre]

Warning 1
13 of 13 files processed

Total VM size: 40.00 GB
Processed size: 40.00 GB
Avg. performance rate: 30 MB/s
Backup mode: agentless

Start time: 3/31/2009 8:55:21 PM
End time: 3/31/2009 9:18:19 PM

Releasing VM files
Cannot initialize information about the guest's system. Target host: [10.0.3.8].
Cannot collect metrics about the guest's operation system.
Cannot open sessions manager's registry key.
Win32 error:Access is denied.
Code: 5



Warning 2
13 of 13 files processed

Total VM size: 30.00 GB
Processed size: 30.00 GB
Avg. performance rate: 31 MB/s
Backup mode: agentless

Start time: 3/31/2009 9:45:18 PM
End time: 3/31/2009 10:01:46 PM

Releasing VM files
RPC function call failed. Function name: [Unfreeze]. Target machine: [10.11.0.31].
RPC error:The RPC server is unavailable.
Code: 1722

[Gostev]

Hello, first one looks like VSS account permission issue (unable to open remote registry key on this VM). Second one - most likely a firewall issue. It would be best if you open support case and provide us all logs from Help | Support Information for definite answers.

[JMPY]

I have solved the case in the last V3.01 with the same first warning :

Cannot initialize information about the guest's system. Target host: [10.0.3.8].
Cannot collect metrics about the guest's operation system.
Cannot open sessions manager's registry key.
Win32 error:Access is denied.
Code: 5

and perhaps the Real Time performance chart on the Virtual Center is missing and is for the same reason.

I have solved the problem with that :

One last thing you can try tomorrow on your ESX machine -
1) rm -rf /var/lib/vmware/hostd/stats
(This will clear out the stats database)
2) service mgmt-vmware restart
(This will restart the host management service)

After doing this log on to the client and check the host performance tab and you backup Veeam backup without warning !

[Luckas]

Hello,

this did not solve my problem. The first time this problems comes up after upgrading tp Backup v3.1 from 3.01

Any ideas?

Helmut

[Gostev]

Helmut, you can work with our support to resolve these warnings. In fact, Veeam Backup 3.1 did not have changes around VSS processing, so it must be some latest change in your environment.