Environment consists of:
Virtual Infrastructure Server, Version 2.0.1 build 32042
VMware ESX Server, Version 3.0.1 build 35804
Installed VCB 1.0.2 base and receiving the following error when I try to run this vcbmounter command:
vcbmounter -h wa-vcenter.rn.wilde.com -u rn\bkupservice -p password -a ipaddr:powerconvert.rn.wilde.com -r y:\mnt\powerconvert-fullVM -t fullvm -m san -L 6
Here is the error output:
Using system libcrypto, version 90703F
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 1200000
00
Connecting to host wa-vcenter.rn.wilde.com on port 902
Error: Other error encountered: Cannot connect to host wa-vce
nter.rn.wilde.com: No connection could be made because the target machine actively refused it
I can log into the VC client using my account rn\bkupservice and password just fine but can't seem to track down where or why Virtual Center is refusing my connection vcbMounter.
great thats it working.
dont know why you are communication on 905, but you do. and you are right, set it in config.js and you're fine for your jobs.
speed ist dependent from a lot of factors. without knowing more about your environment it would be like guessing. but exporting a "fullvm" is quiet something to do.
and: vcb is a vi client too. terribly stripped down maybe. but it uses exactly the same mechanisms...
An easy way to check if VCB is logging in correctly try this
vcbvmname -h wa-vcenter.rn.wilde.com -u rn\bkupservice -p password -s ANY -L6 > vmnames.log
open the vmnames.log and look for the server, make note does it have an IP next to ipaddr? Also try running it with the "moref" ID
vcbmounter -h wa-vcenter.rn.wilde.com -u rn\bkupservice -p password -a moref:moref id -r y:\mnt\powerconvert-fullVM -t fullvm -m san -L 6
If it does have the IP try using just the IP and not the DNS name.
try usin a local user instead of domain user on the login to the wa-vcenter
******************************
Svein E Jensen
IT Avdelningen
ÅRE KOMMUN
Box 201, 830 05 Järpen
0647-16331
******************************
if you get still failures, check the firewall (at the VC-Server), you need your VC-Port (default 902 vor VC 2.0.x and 443 for 2.5) wide open.
if thats ok, next check your credentials....
btw.... DNS should be correctly working as well...
you then should go further than this.....
that was one of the things I tried. I used local Administrator account from the server and received the same error.
thank you for your reply.
Bertha-
I will try your suggestion today and respond with my findings.
thank you for the reply!
How can I check the firewall at the VC server?
The Windows firewall is disabled by default and verified that it wasn't enabled accidentally.
Do you mean the configuration tabs for ESX hosts from Virtual Center console...?
the VC has no own FW, i meant the Windows one in fact.
Could you verify wether you are trying to connect the VC server thru a network firewall or such? can you ping the machine via Ip-Address and name?
From my VCB proxy server I can ping the VC server both by name and IP address.
I checked that DNS has correct forward and reverse lookups for the VC server and as a precaution created an entry in the proxy's HOST file for the VC server.
Bertha-
Both commands produced the "connection actively refused error", here is output from the command using the moref option.
C:\>vcbmounter -h wa-vcenter.rn.wilde.com -u rn\bkupservice -p password -a moref
:moref -r y:\mnt\powerconvert-fullVM -t fullvm -m san -L 6
Current working directory: C:\
Using system libcrypto, version 9
0703F
Vmacore::InitSSL: doVersionCheck = tru
e, handshakeTimeoutUs = 120000000
Connecting to host wa-vcenter.r
n.wilde.com on port 902
Error: Other error encountered
: Cannot connect to host wa-vcenter.rn.wilde.com: No connection could be made be
cause the target machine actively refused it
do a "netstat -a" at the VC server.... can you find the port 902 listening?
Good idea on the netstat.....Looks like 902 is there and listening here is the output.
C:\>netstat -a
Active Connections
Proto Local Address Foreign Address State
TCP wa-vcenter:http wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:epmap wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:https wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:microsoft-ds wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:905 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:1025 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:ms-sql-s wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:2967 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:ms-wbt-server wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:27000 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:27010 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:1074 wa-vcenter.domain.com:8083 ESTABLISHED
TCP wa-vcenter:8083 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:8083 wa-vcenter.domain.com:1074 ESTABLISHED
TCP wa-vcenter:8085 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:8087 wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:http dad.domain.com:2904 ESTABLISHED
TCP wa-vcenter:netbios-ssn wa-vcenter.domain.com:0 LISTENING
TCP wa-vcenter:905 dad.domain.com:2905 ESTABLISHED
TCP wa-vcenter:1048 wa-vcenter.domain.com:27010 ESTABLISHED
TCP wa-vcenter:1049 esx-prod3.domain.com:902 ESTABLISHED
TCP wa-vcenter:1050 esx-prod1.domain.com:902 ESTABLISHED
TCP wa-vcenter:1053 esx-prod5.domain.com:902 ESTABLISHED
TCP wa-vcenter:1073 esx-prod2.domain.com:902 ESTABLISHED
TCP wa-vcenter:1077 esx-dev1.domain.com:902 ESTABLISHED
TCP wa-vcenter:1078 esx-dev2.domain.com:902 ESTABLISHED
TCP wa-vcenter:1079 esx-prod4.domain.com:902 ESTABLISHED
TCP wa-vcenter:1086 mom.domain.com:opsmgr ESTABLISHED
TCP wa-vcenter:1087 thor.domain.com:epmap ESTABLISHED
TCP wa-vcenter:1088 thor.domain.com:1025 ESTABLISHED
TCP wa-vcenter:1091 thor.domain.com:microsoft-ds TIME_WAIT
TCP wa-vcenter:1096 thor.domain.com:1025 ESTABLISHED
TCP wa-vcenter:1101 thor.domain.com:ldap TIME_WAIT
TCP wa-vcenter:1104 RADKINS1:netbios-ssn TIME_WAIT
TCP wa-vcenter:1105 thor.domain.com:epmap ESTABLISHED
TCP wa-vcenter:1106 thor.domain.com:1025 ESTABLISHED
TCP wa-vcenter:kpop thor.domain.com:ldap TIME_WAIT
TCP wa-vcenter:ms-wbt-server JCORREIALAP:1176 ESTABLISHED
TCP wa-vcenter:27010 wa-vcenter.domain.com:1048 ESTABLISHED
TCP wa-vcenter:27010 esx-prod1.domain.com:57899 ESTABLISHED
TCP wa-vcenter:27010 esx-prod2.domain.com:58228 ESTABLISHED
TCP wa-vcenter:27010 esx-prod3.domain.com:46484 ESTABLISHED
TCP wa-vcenter:27010 esx-prod4.domain.com:35194 ESTABLISHED
TCP wa-vcenter:27010 esx-prod5.domain.com:47013 ESTABLISHED
TCP wa-vcenter:27010 esx-dev1.domain.com:46813 ESTABLISHED
TCP wa-vcenter:27010 esx-dev2.domain.com:49741 ESTABLISHED
UDP wa-vcenter:microsoft-ds :
UDP wa-vcenter:isakmp :
UDP wa-vcenter:902 :
UDP wa-vcenter:1026 :
UDP wa-vcenter:1027 :
UDP wa-vcenter:ms-sql-m :
UDP wa-vcenter:ipsec-msft :
UDP wa-vcenter:ntp :
UDP wa-vcenter:1028 :
UDP wa-vcenter:1057 :
UDP wa-vcenter:1099 :
UDP wa-vcenter:1108 :
UDP wa-vcenter:ntp :
UDP wa-vcenter:netbios-ns :
UDP wa-vcenter:netbios-dgm :
C:\>
to me it looks like VC is listening on 905 instead of 902.... for what reason ever....
try this to verify:
vcbmounter -h wa-vcenter.rn.wilde.com:905 -u rn\bkupservice -p password -a moref
:moref -r y:\mnt\powerconvert-fullVM -t fullvm -m san -L 6
better now?
Not yet...look at this?
C:\>vcbmounter -h wa-vcenter.rn.wilde.com:905 -u rn\bkupservice -p veritas -a
moref -r y:\mnt\powerconvert-fullVM -t fullvm -m san -L 6
Current working directory: C:\
Using system libcrypto, version 9
0703F
Vmacore::InitSSL: doVersionCheck = tru
e, handshakeTimeoutUs = 120000000
Connecting to host wa-vcenter.r
n.wilde.com* on port 905
Error: Other error encountered
: Host address lookup for server wa-vcenter.rn.wilde.com* failed: The requested
name is valid, but no data of the requested type was found
C:\>
sorry, my mistake, ommit the *'s, i wanted to set the :905 bold but the forum software insertet stars instead... i editied then, but somehow this didnt make it to you...
removed the * after the VC hostname and got something a little different.
C:\>vcbmounter -h wa-vcenter.rn.wilde.com:905 -u rn\bkupservice -p veritas -a moref -r y:\mnt\powerconvert-ful
lVM -t fullvm -m san -L 6
Current working directory: C:\
Using system libcrypto, version 90703F
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000
000
Connecting to host wa-vcenter.rn.wilde.com on port 905
Connected to stream: [class Vmacore::Ssl::SSLStreamImpl:01
883988]
Unsetting unknown path: /vmomi/
Authenticating user rn\bkupservice
Exception: Assert failed!
(backtraces not supported)
CoreDump: Writing minidump to C:\Documents and Settings\bkupservice\
Application Data\VMware\vcbmounter-2780-2064.dmp
C:\>
Can't read the dump file being produced.
I removed the * from the command but it still fails with the error I just posted.
The netstat does show wa-vcenter listening on 902 for .
This is very bizarre, I've done a number of VCB installs and never run into a problem like this.
hey, we are in now.
this next error is expected since you have a major syntax error tin the -a parameter. But in the first hand i focused to get you in to VC.
now we can focus on the -a syntax. use it as follows and forget the moref (you usualy only have theis id when scripting).
Use the IP-address of the to be backuped server: -a ipaddr:10.1.1.1 (or such)
Use the FQDN DNS name of the to be backuped server: -a ipaddr:someserver.my.domain
Use the VC Name: -a name:TheServerName (if it contains special chars like blanks: -a "name:My Server Name")
you should then get further.
Okay cool....I tried the command with -a ippaddr:sulu2.rn.wilde.com and it's working the snapshot is being exported to my proxy right now.
Do I just need to modify my config.js entry for the port to be 905 instead of 902?
Also noticing it is very slow. The server I'm backing up (sulu2) only has a 10GB drive....the snapshot is at about 25% complete and has been running for 17 minutes....?
Is this because we're using port 905 instead of 902? I had thought 905 was for VI Client connectivity.
great thats it working.
dont know why you are communication on 905, but you do. and you are right, set it in config.js and you're fine for your jobs.
speed ist dependent from a lot of factors. without knowing more about your environment it would be like guessing. but exporting a "fullvm" is quiet something to do.
and: vcb is a vi client too. terribly stripped down maybe. but it uses exactly the same mechanisms...