VMware
 

Knowledge Base

Search the Knowledge Base:

Products:
Search In:
 

File-Level Backup with VCB Fails When Attempted with Six or More Virtual Disks on the Backup Proxy

Details

Why does my file-level backup with VMware Consolidated Backup (VCB) fail when I attempt to mount six virtual disks concurrently on the backup proxy when connecting directly to a host?

Solution

File-level backup with VCB fails if an attempt is made to mount many (typically six or more) virtual disks concurrently on the backup proxy when connecting directly to a host.

Currently, VCB opens one connection per disk to the SDK instance it is using (ESX Server or VirtualCenter Server). For ESX Server, the default number of concurrent connections is limited to eight. This limit prevents the possibility of jeopardizing the performance or stability of the ESX Server service console by overloading it with too many instances. Also, some of these eight connections can be used for virtual machine remote consoles, reducing the number of connections available to VCB.

Because VCB has to share this connection pool with other applications (VirtualCenter Server, virtual machine remote consoles, or some management agents), no fixed limit can be given. When you encounter this problem, hostd logs the following message:

 [... 'VmdbSvc' 115477424 error] Max connections reached (8), closing connection 

To work around this issue, VMware recommends that VCB connect to a VirtualCenter Server instead of directly to the ESX Server machine. If you do not use a VirtualCenter Server (standalone ESX Server host), you can increase the total number of concurrent connections that hostd allows by editing /etc/vmware/hostd/config.xml.

Add the following lines to the <vmacore> section of this configuration file to increase the total number of concurrent connections allowed:

<vmdb><maxconnectioncount>100</maxconnectioncount></vmdb> 
Warning: Do not use these extra connections for connecting more than eight instances of the VI Client directly to an ESX Server machine. Doing so can affect the performance of your ESX Server machine and compromise its stability. These extra connections should be used only for VCB.
 
Note: This issue is resolved with the releases of ESX Server 3.0.1, VirtualCenter 2.0.1, and VCB 1.0.1.

Keywords

2185

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (1 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (1 Ratings)   
Actions