Comprehensive data protection for all workloads
Post Reply
BillyT
Service Provider
Posts: 14
Liked: never
Joined: May 29, 2009 12:12 pm
Full Name: Bill Thompson
Contact:

VSS Failure

Post by BillyT » Jun 19, 2009 1:23 am

I am trying to backup some VMs using VCB SAN mode with VSS. The error is a "known" issue:

Cannot initialize information about the guest's system. Target host: [xxx.xxx.xxx.xxx].
Cannot collect metrics about the guest's operation system.
Cannot connect to the remote registry.
Win32 error:The network path was not found.
Code: 53

What makes my problem different than others I have seen posted is that these VMs are not members of a domain and I am trying to use the local admin account. I have confirmed that the job will run without error if I enable and start the Remote Registry service on the target VM, but I would like to avoid that if possible. Is remote registry absolutely necessary for VSS success in my scenario?

Gostev
SVP, Product Management
Posts: 25280
Liked: 3754 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: VSS Failure

Post by Gostev » Jun 19, 2009 8:41 am

Bill, yes Remote Registry is required - otherwise, it will not be possible for Veeam Backup to control its VSS agent remotely.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 22 guests