cancel
Showing results for 
Search instead for 
Did you mean: 

Vmware credential validation failed. connect failed (-1)

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Environment

NBU = 7.5.0.5

OS of NBU = Windows 2008 R2 (64bit)

ESXi Server version = 4.1.0

Error

ESXi.png

1 ACCEPTED SOLUTION

Accepted Solutions

CRZ
Level 6
Employee Accredited Certified

Would this TechNote have helped you?

How to add Virtual Machine Server credentials using tpconfig command
 http://symantec.com/docs/TECH68837

Your error is not mentioned (and the command is written for UNIX instead of Windows), but it does say:

This is useful when gathering information, or when GUI access is not available.

...and the command referenced appears to be the same one you used (although without a -requiredport switch, so I'm assuming you used the default).

 

View solution in original post

13 REPLIES 13

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listhosts
NBEMMCMD, Version: 7.5.0.5
The following hosts were found:
server           NetBackupTest
master           NetBackupTest
ndmp             NetBackupTest
replication_host NetBackupTest1
virtual_machine  192.168.1.88
virtual_machine  drvmware0
Command completed successfully.

I ran the below command

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -deletehost -machinenam
e drvmware0 -machinetype virtual_machine
NBEMMCMD, Version: 7.5.0.5
The function returned the following failure status:
generic EMM SQL error (193)
Command did not complete successfully.

 

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbemmcmd -listhosts
NBEMMCMD, Version: 7.5.0.5
The following hosts were found:
server           NetBackupTest
master           NetBackupTest
ndmp             NetBackupTest
replication_host NetBackupTest1
virtual_machine  192.168.1.88
Command completed successfully.

 

Now see the below error

ESXi1.png

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

are you able to telnet the 443 port from Master server to Vmwaer ESX server??

telnet <ESXi> 443

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

C:\Program Files\Veritas\NetBackup\bin\admincmd>telnet drvmware0 443
Connecting To drvmware0...Could not open connection to the host, on port 443: Co
nnect failed

 

But I can ping/ssh both to my ESXi
 

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

you require this port to communicate to discover the VMs and validations.

and also you require the port 902 if you use NBD transport..

check with your firewall team..if they are blocking the ports.. 

more details about the VMware ports details.

https://www-secure.symantec.com/connect/blogs/nuts-and-bolts-netbackup-vmware-transport-methods-and-...

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Nothing(firewall) included between both. The Netbackup Server is a VM and it exist on the ESXi Server which Netbackup not able to communicate

 

 

root@zahidhaseeb:~# nmap 192.168.1.230

Starting Nmap 5.21 ( http://nmap.org ) at 2013-07-01 21:28 PKT
Nmap scan report for 192.168.1.230
Host is up (0.00060s latency).
Not shown: 992 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
80/tcp   open  http
427/tcp  open  svrloc
443/tcp  open  https
902/tcp  open  iss-realsecure
5989/tcp open  unknown
8000/tcp open  http-alt
8100/tcp open  unknown
MAC Address: 00:1C:C0:B0:07:89 (Intel Corporate)

Nmap done: 1 IP address (1 host up) scanned in 1.35 seconds
 

inn_kam
Level 6
Partner Accredited
 
Verify the server(s) listed in the NetBackup Administration Console on the master server under "Host Properties > Master Servers > master server properties > VMware Backup Hosts"
The only servers listed here should be NetBackup servers performing as VMware Backup Hosts.  If any Virtual Center Servers or ESX Hosts are listed here they should be removed.
The Virtual Center Server, or the ESX Hosts if there is not a Virtual Center Server in this environment, should be added in the NetBackup Administration Console under "Media and Device Management > Credentials > Virtual Machine Servers"
The reason for the Status 25 is that the validation request is sent to the VMware Backup Host's NetBackup Client Service.  This port and service are not present on a Virtual Center Server/ESX Host and will result in a "cannot connect on socket" failure.
 
2. also check  Add the proxy server host name to the NetBackup master server Servers list using the host name resolved by  above post.
 
3.In the NetBackup Administration Console, go to:


NetBackup Management -> Host Properties -> Master Servers -> (double-click the master server to open)

In the master server properties, go to:

Properties -> Servers

In this list add the proxy server using either the fully qualified domain name (FQDN) or short name (as identified by 1 above).  If unsure, add both.


Save this change, then stop and restart services on the NetBackup master server to make the changes take effect.

 

inn_kam
Level 6
Partner Accredited

Virtual machine server credential validation fails with MM Status -1.

Article:TECH180217  |  Created: 2012-01-30  |  Updated: 2012-01-30  | 

Article URL http://www.symantec.com/docs/TECH180217


 

 

Credential validation fails with Host connection failed (MM Status -1).

Article:TECH194983  |  Created: 2012-08-15  |  Updated: 2012-08-15  |  Article URL http://www.symantec.com/docs/TECH194983

 

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

"Host Properties > Master Servers > master server properties > VMware Backup Hosts"

 

Not able to see VMware Backup Hosts under Host Properties > Master Servers > master server properties

inn_kam
Level 6
Partner Accredited
VMware Access Hosts properties
Use the VMware backup hosts properties in the NetBackup Adminstration
Console to add or remove VMware backup hosts. These properties appear when
the NetBackup Enterprise Client license is installed. These properties apply to
currently selected master servers.
You can add servers to and remove servers from the backup hosts list.
A VMware backup host is a server on the same SAN as a VMware ESX server. The
VMware ESX server must be able to access the snapshot of the VMware virtual
machine. A backup host can provide access to the files for third-party backup
vendors.
For more information, see the NetBackup for VMware Administrator’s Guide.
taken from NB 7.5 Admin win guide
 

 

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

From GUI I keep facing the same error which is:

VMware crediantials validation failed. connect failed (-1)

===============================================

I cross check below:

- host enteries on Esxi Server and Netbackup Server as well and both can ping each other via host name and IP Adress as well.

- Netbackup Server entry mentioned under below path.

Untitled_0.png

 

- Now when trying to add the crediantials I keep facing the error under the below path.

 

ESXi1_1.png

 

- I used the below TechNote as well but no success.

http://www.symantec.com/docs/TECH170018

===============================================

- Via command line the above VMware crediantial validation successfully added. See the below for reference.

Resolution:

C:\Program Files\Veritas\Volmgr\bin>tpconfig.exe -add -virtual_machine VServer -
vm_user_id root -vm_type 2 -password **********

 

(VServer is the ESXi Server name, root is the ESXi Server user ID)

 

- After doing the below I successfully browse the VMware machines from the Clients tab under Netbackup policy. See the below for reference:

VMBrowse.png

 

===============================================

As per my assumption It seems that its a bug.

 

huanglao2002
Level 6

hi Zahid.Haseeb

thanks for you share,you can mark as solution.

inn_kam
Level 6
Partner Accredited

its resolved now

 

CRZ
Level 6
Employee Accredited Certified

Would this TechNote have helped you?

How to add Virtual Machine Server credentials using tpconfig command
 http://symantec.com/docs/TECH68837

Your error is not mentioned (and the command is written for UNIX instead of Windows), but it does say:

This is useful when gathering information, or when GUI access is not available.

...and the command referenced appears to be the same one you used (although without a -requiredport switch, so I'm assuming you used the default).