01-10-2016 08:41 AM
Hi
I tried the solution given however unable to get a solution
I am using windows 2008 server and have MHVTL however I am unable to connect to masterserver (testmasterserver) MHVTL & Master server are able to ping each other.
Unable to poing nbdb_ping
unable to stop all the services
below are the services which are not stopped what to do pls assist
NetBackup software will be shutdown. This may cause backups to fail.
Do you wish to proceed? (y/n) y
Shutting down services
Calling nbproxyreq to cleanup nbproxy processes.
Shutdown of one or more services failed.
C:\Program Files\Veritas\NetBackup\bin>bpps
* WIN-QB9MA8Q042O 1/10/16 08:59:57.689
COMMAND PID LOAD TIME MEM START
nbstserv 2116 0.000% 0.686 22M 1/10/16 08:31:17.692
nbproxy 2844 0.000% 0.436 19M 1/10/16 08:31:29.782
NBConsole 544 0.000% 1.856 39M 1/10/16 08:33:17.984
vnetd 3064 0.000% 0.015 6.7M 1/10/16 08:47:08.077
bpinetd 3532 0.000% 0.031 8.8M 1/10/16 08:47:08.108
bpcd 2028 0.000% 0.062 7.5M 1/10/16 08:47:08.233
nbevtmgr 2376 0.000% 0.499 21M 1/10/16 08:47:09.777
bpdbm 2864 0.000% 0.031 14M 1/10/16 08:47:19.262
bpjobd 3308 0.000% 0.046 14M 1/10/16 08:47:19.293
nbpem 2312 0.000% 0.748 26M 1/10/16 08:47:20.791
nbproxy 2572 0.000% 0.436 17M 1/10/16 08:57:10.971
bpps 1236 0.000% 0.062 6.2M 1/10/16 08:59:56.612
Solved! Go to Solution.
01-13-2016 10:34 AM
Your actual computer hostname is not "masterserver", it is "WIN-SCLLFJMHDC1". NetBackup doesn't like this.
You haven't confirmed that you've changed your hosts file name to "hosts".
Can you also show the contents of your "hosts" file?
01-10-2016 10:01 AM
01-10-2016 10:05 AM
Try stopping all the NetBackup processes, use task manager and kill those processes.
Then check to ensure that the drive NetBackup and it's databases are on is not full or nearly full (within 10% full) if it is clear space
Then restart netbackup: bpup -f -v (bpup is located in program files\veritas\netbackup\bin
Does NetBackup come up now?
If not, check the server.log under \program files\veritas\netbackupdb\log\ to see if there are any assertion errors
If so, follow this technote to recreate the transaction log
https://www.veritas.com/support/en_US/article.TECH72780
01-10-2016 10:07 AM
mehul, check the server.log as per my post above and the disk space available.
IF that all looks fine and if it's just nbemm not coming, increase the log for nbemm and look at the log
vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6
Restart NetBackup
If nbemm does not stay up run:
vxlogview -i 111 -d all -t 00:05:00 > c:\nbemm.txt
Then post up the nbemm.txt file here.
01-11-2016 07:33 AM
Hi
I am running it on VMWare and I have MHVTL. It's a dummy environment I am not sure about the server.log file could you please explain
01-11-2016 07:40 AM
Hi,
I copied and pasted in a text file the data which was there in that text file pls check and let me know the issue and how you were able to find issues i that file
01-11-2016 09:52 AM
01-11-2016 12:50 PM
01-11-2016 03:52 PM
Typically, when we create small virtual test environments, then we would:
1) decide upon and set the hostname of the server first before doing anything else, e.g.: master1
2) configure at least one virtual NIC - it does not need to be able to reach the internet
...and you don't need DNS for a small test environment
3) assign a fixed non APIPA address to your vNIC
4) choose a dummy long name for your test master server, e.g.
shortname and hostname: master1
dummy FQHN long name: master1.test.com
5) add a host file entry that has the long and the short names
x.x.x.x master1.test.com master1
6) then install NetBackup Server
...and all should be ok, because you have a fixed IP, and the shortname matches the hostname, and the shortname matches the start of the lomg name, and both the short name and the long name are resolvable... and NetBackup Server will be happy.
01-13-2016 08:18 AM
Hi
I have reinstalled the OS and then reinstalled the netbackup 7.1 master
my masterservername - masterserver (192.168.211.131)
hostname - NBclient - (192.168.211.129)
Tape lib - vtl (192.168.211.130)
using vmworkstation on which i have used dhcp using virtual editor of vm everybody is able to ping each other
Again i tried to run the NB master server it gives me the same error unable to connect to EMM server I checked the services it not getting started
01-13-2016 08:59 AM
01-13-2016 09:13 AM
I got the below results
C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self
gethostname() returned: masterserver
host masterserver: masterserver at 192.168.0.9
aliases: masterserver 192.168.0.9
host entry done already
01-13-2016 09:18 AM
NBEMM services in windows is still not started says error: windows could not start netbackup services on local computer
error 1068: the dependency service group failed to start
01-13-2016 09:32 AM
01-13-2016 09:34 AM
I. 01/13 07:20:21. SQL Anywhere Network Server Version 11.0.1.2472
I. 01/13 07:20:21. OEM Authenticated Edition, licensed only for use with authenticated OEM applications.
I. 01/13 07:20:21.
I. 01/13 07:20:21. Copyright © 2001-2009, iAnywhere Solutions, Inc.
I. 01/13 07:20:21. Portions copyright © 1988-2009, Sybase, Inc. All rights reserved.
I. 01/13 07:20:21. Use of this software is governed by the Sybase License Agreement. Refer to http://www.sybase.com/softwarelicenses
I. 01/13 07:20:21.
I. 01/13 07:20:21. 1 physical processor(s) detected.
I. 01/13 07:20:21. Processor limit (licensed processors): 128
I. 01/13 07:20:21. Maximum number of physical processors the server will use: 1
I. 01/13 07:20:21. This server is licensed to:
I. 01/13 07:20:21. NetBackup
I. 01/13 07:20:21. Symantec Corporation
I. 01/13 07:20:21. Running Windows 2008R2 Build 7601 Service Pack 1 on X86_64
I. 01/13 07:20:21. Server built for X86_64 processor architecture
I. 01/13 07:20:22. 25600K of memory used for caching
I. 01/13 07:20:22. Minimum cache size: 25600K, maximum cache size: 512000K
I. 01/13 07:20:22. Using a maximum page size of 4096 bytes
I. 01/13 07:20:22. Database server started at Wed Jan 13 2016 07:20
I. 01/13 07:20:22. Trying to start SharedMemory link ...
I. 01/13 07:20:22. SharedMemory link started successfully
I. 01/13 07:20:22. Trying to start TCPIP link ...
I. 01/13 07:20:22. Starting on port 13785
I. 01/13 07:20:22. TCPIP link started successfully
I. 01/13 07:20:22. Now accepting requests
I. 01/13 07:44:32. Database server shutdown requested via server console
I. 01/13 07:44:32. Database server stopped at Wed Jan 13 2016 07:44
01-13-2016 10:05 AM
You said your master's IP is 192.168.211.131 but when you run bpclntcmd its finding the master on 192.168.0.9
Where is the other IP coming from?
01-13-2016 10:05 AM
The "bpclntcmd -self" command asks NetBackup software to perform a kind of "who do I think I am?" query, and it says it think it's 192.168.0.9. But you say the master should be 192.168.211.131. I think you might need to revisit your planning/implementation of networking for these VMs.
01-13-2016 10:07 AM
i understand however but as suggested above i have set the ip in the network adapter that is the reason why it is 192.168.0.9
01-13-2016 10:08 AM
Is your hosts file named "hosts" or "hosts.txt" ?
> dir C:\Windows\System32\drivers\etc\hosts*
...and if "hosts.txt", this is incorrect - it needs to be "hosts" without a file name type extension.
01-13-2016 10:11 AM
dear sdo,
it is hosts.txt i have checked it