Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+VMware\s+VCB\s+policy\s*$/: 3 ]

Total 3 documents matching your query.

1. [Veritas-bu] VMware VCB policy (score: 1)
Author: Renee Carlisle <rcarlisle AT serverwarecorp DOT com>
Date: Thu, 16 Oct 2008 12:31:24 -0400
When trying to search for Virtual Machines in a VCB policy, the search keeps failing with cannot connect on socket error.  I have double checked credentials, tried both the ESX server and the Virtual
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2008-10/msg00236.html (13,057 bytes)

2. Re: [Veritas-bu] VMware VCB policy (score: 1)
Author: "George Winter" <george_winter AT symantec DOT com>
Date: Tue, 21 Oct 2008 20:02:33 -0700
Hi Renee. There are a couple of reasons why this might happen.  Most common issue is DNS.  For example, the Virtual Center server might not be resolving correctly from the VMware Backup Proxy.  You c
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2008-10/msg00298.html (19,106 bytes)

3. Re: [Veritas-bu] VMware VCB policy (score: 1)
Author: Renee Carlisle <rcarlisle AT serverwarecorp DOT com>
Date: Wed, 22 Oct 2008 08:37:22 -0400
We have some updated information.  The backup proxy server is a 64bit system.  Apparently when the VMware converter utilities are installed, they are installed as 32 bit binaries but are supposed to
/usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2008-10/msg00305.html (21,424 bytes)


This search system is powered by Namazu