nbu6.0服务起不来

Question

先前做了重扫驱动的操作，之后发现master server 跟media server 之间通信有问题。
    现在的问题是重启备份服务器后，Netbackup enterprise media manager和Netbackup Resource Broker，两服务死也起不来了。
    不知道有没好的解决方法，谢过各位了。

Answer 1

出问题的是master server还是media server

Answer 2

3Q！
这种方式尝试过了，还是不行。。
现在的问题是，将两个media server 加进来一扫，netbackup device manager服务就会停掉。

[ 本帖最后由 tuzhu2046 于 2009-9-12 20:14 编辑 ]

Answer 3

Document ID: 281817
http://support.veritas.com/docs/281817
E-Mail this document to a colleague

GENERAL ERROR: The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker don't error, but won't remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334"
Exact Error Message
status 334: EMM interface initialization failed.
V-118-55 Unable to connect to database.

Details:
Overview:  
The services called NetBackup Enterprise Media Manager (EMM) and NetBackup Resource Broker don't error, but won't remain started and the NetBackup Device Manager service generates event log error, "EMM interface initialization failed, status = 334".  This is most likely to happen after the initial install of NetBackup 6.0 or the initial upgrade to NetBackup 6.0.

Troubleshooting:
Several symptoms listed below all point to a similar problem.

Master Log Files:
1. The open database connectivity (ODBC) Data Source Administrator, under Administrative Tools > Data Sources (ODBC), shows VERITAS NB Adaptive Server Anywhere 9.0.1 as "Not marked" in the Version and Company fields on the Drivers tab. (See Figure 1)

Figure 1
  

2. The NetBackup Device Manager service will display this error in the Application Event Log:
Event Type: Error
Event Source: NetBackup Device Manager
Event Category: None
Event ID: 0
Date: 2/10/2006
Time: 1:50:48 PM
User: N/A
Computer: xxxxxxxxx
Description:
EMM interface initialization failed, status = 334

3. The services called NetBackup Enterprise Media Manager and NetBackup Resource Broker don't error, but won't remain started.

4. The command line process <InstallPath>VERITASNetBackupbin>nbdb_ping fails with, "Database [NBDB] is not available."

5. The log <InstallPath>VERITASNetBackuplogsadmin  records this error after the failed nbdb_ping:
14:03:37.687 [3612.540] <16> nbdb_ping: ODBC connection failed.
14:03:37.687 [3612.540] <16> nbdb_ping: ErrMsg Specified driver could not be loaded due to system error  126 (VERITAS NB Adaptive Server Anywhere 9.0.1)., ErrCode -1, Sqlstate IM003

6. The VXUL Logs will show this sequence of errors: (syntax used to collect the log sample: vxlogview -t 00:10:00 -d all)
2/7/2006 18:58:55.104 [Diagnostic] NB 51216 nbemm 111 PID:3752 TID:3744 [No context] 1 V-111-1049 [ConnectionManager::OpenConnection] EMMServer generic error = Can't connect to the database (Specified driver could not be loaded due to system error  126 (VERITAS NB Adaptive Server Anywhere 9.0.1). <-1> )
2/7/2006 19:26:20.661 [Debug] NB 51216 nbrb 118 PID:3852 TID:740 [No context] 1 [RBDatabase::connectDatabase()] ODBC connection failed. ErrMsg: Specified driver could not be loaded due to system error  126 (VERITAS NB Adaptive Server Anywhere 9.0.1). ErrCode: -1 DBErrCode: 160 Sqlstate: IM003
2/7/2006 19:26:20.661 [Application] NB 51216 nbrb 118 PID:3852 TID:740 [No context] [Critical] V-118-55 Unable to connect to database.  NetBackup Resource Broker will not start.
2/7/2006 19:26:20.661 [Debug] NB 51216 nbrb 118 PID:3852 TID:740 [No context] 1 [doRun] unable to initialize the database, error: 25

Resolution:
The path to a critical DLL for allowing ODBC communication to the EMM database can not be found at the specified location. The DLL is called DBODBC9.DLL.  Check to see if the DLL exists in the correct location, <InstallPath>VERITASNetBackupDBWIN32DBODBC9.DLL

If the DLL is there, check the registry to make sure it is pointing to the correct working path for this DLL:
HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIVERITAS NB Adaptive Server Anywhere 9.0.1 and verify the keys named Driver and Setup are pointing to the correct path.  If they are incorrect, change them to reflect the correct path to DBODBC9.DLL.

Once the path statements have been adjusted, stop and start the NetBackup services:

1.  Stop NetBackup services by running the following command:
<installPath>veritasnetbackupbinbpdown

2.  Verify all processes have been stopped by running the following command:
<installPath>veritasnetbackupbinbpps
Note:  A reboot may be necessary to fully eliminate any lingering NetBackup processes that might not terminate when the services are stopped.

3.  Start the NetBackup services by running the following command:
<installPath>veritasnetbackupbinbpup

Answer 4

备份服务器时windows，我看了注册表不存在这个问题

Answer 5

你的BP.CONF文件里有没有EMM_SERVER这个啊。我记得我删除了后，会报这样的错的。

Answer 6

我已将补丁打到mp7了，我这辈子跟奖几乎无缘哈---那种100%中奖率的除外。

现在看到一个报错信息时：unalbe to connect to the Enterprise Media Manger server host_name.
unable to connect to the EMM server.

[ 本帖最后由 tuzhu2046 于 2009-9-12 14:25 编辑 ]

Answer 7

LZ不会是中奖了吧，这个问题貌似是NBU6.0GA的一个bug，不知道LZ有没有安装相应的补丁？

Answer 8

lisence都没问题。
端口也没问题。
现在的现象是点击activity monitor和别的选项nbu都会死。

[ 本帖最后由 tuzhu2046 于 2009-9-12 13:09 编辑 ]

Answer 9

Netbackup Resource Broker起不来 可以看看是不是端口被占用了？

Netbackup enterprise media manager看看是不是license过期了？