netbakcup備份時遇到 status 59: access to the client was not allowed 問題解決

一.問題描述
在一個linux 6.3 x86_64+oracle 10.2.0.5的資料庫伺服器上安裝netbackup client和netbakckup db for oracle 後,在netbackup server上配置備份策略.進行手工備份時發生錯誤程式碼為59的錯誤,
錯誤描述如下:
2012-10-24 11:40:37 - Info nbjm(pid=3436) starting backup job (jobid=269562) for client zhjkdb, policy ORA-ZHJKDB, schedule fullbackup
2012-10-24 11:40:37 - Info nbjm(pid=3436) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=269562, request id:{E2ADD91E-3307-4F69-8D2C-7B968B0182A2})
2012-10-24 11:40:37 - requesting resource Disk-Main
2012-10-24 11:40:37 - requesting resource netbackup.NBU_CLIENT.MAXJOBS.zhjkdb
2012-10-24 11:40:37 - requesting resource netbackup.NBU_POLICY.MAXJOBS.ORA-ZHJKDB
2012-10-24 11:40:37 - granted resource netbackup.NBU_CLIENT.MAXJOBS.zhjkdb
2012-10-24 11:40:37 - granted resource netbackup.NBU_POLICY.MAXJOBS.ORA-ZHJKDB
2012-10-24 11:40:37 - granted resource Disk-Main
2012-10-24 11:40:39 - estimated 0 Kbytes needed
2012-10-24 11:40:39 - Info nbjm(pid=3436) started backup job for client zhjkdb, policy ORA-ZHJKDB, schedule fullbackup on storage unit Disk-Main
2012-10-24 11:40:41 - started process bpbrm (7144)
2012-10-24 11:40:44 - Error bpbrm(pid=7144) bpcd on zhjkdb exited with status 59: access to the client was not allowed
2012-10-24 11:40:44 - Info bpbrm(pid=7144) zhjkdb is the host to backup data from
2012-10-24 11:40:44 - end writing
access to the client was not allowed(59)

[@more@]

客戶端測試伺服器的帶庫是否可以使用,結果也失敗,如下:
[oracle@zhjkdb ~]$ sbttest "SBT_TAPE"
The sbt function pointers are loaded from libobk.so library.
-- sbtinit succeeded
-- sbtinit (2nd time) succeeded
sbtinit: Media manager supports SBT API version 2.0
sbtinit: Media manager is version 5.0.0.0
sbtinit: vendor description string=Veritas NetBackup for Oracle - Release 6.5 (2007072323)
sbtinit: allocated sbt context area of 8 bytes
sbtinit: proxy copy is supported
-- sbtinit2 succeeded
-- regular_backup_restore starts ................................
MMAPI error from sbtbackup: 7501, VxBSACreateObject: Failed with error:
Server Status: access to the client was not allowed

二.問題分析
在netbackup server檢視job的工作記錄和錯誤的描述,如下:
Status 59: access to the client was not allowed

The master or the media server tries to access the client, but the client does not recognize the server as a valid server.
For the Enterprise Vault Agent: The names of all of the media servers among the Enterprise Vault servers are not specified in the client configuration.

troubleshoot:
Do the following, as appropriate:
* If the server is a valid server, verify that it is in the server list on the client. If necessary add it as follows:
* On Windows clients: Add the server on the Server to use for backups and restores drop-down in the Specify NetBackup Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client. Then click Specify NetBackup Machines and Policy Type on the File menu.
* On UNIX and Linux, and Macintosh clients: add a SERVER entry in the bp.conf file.
* On NetWare target clients: add a SERVER entry in the bp.ini file.
If you change the server list on a UNIX or Linux master server, do the following for the changes to take effect: stop and then restart the NetBackup Request daemon (bprd) and NetBackup database manager daemon (bpdbm). On Windows, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.
* On Windows clients, enable bpinetd debug logging as follows:
* Create a bpinetd debug log directory on the client.
* Increase the debug or log level.
See How to set logging levels on UNIX clients in the Troubleshooting Guide.
See How to set logging levels on PC clients in the Troubleshooting Guide.
* Retry the backup and examine the resulting logs to determine the cause of the failure.
* On all clients, enable bpcd debug logging as follows:
* Create a bpcd debug log directory on the client.
* On a UNIX or Linux client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.
* On PC clients, increase the debug or log level as explained in the debug log topics in Chapter 3.
* Retry the backup and examine the resulting logs to determine the cause of the failure.
* Check the bpcd debug log to determine the server's peer name and what comparisons are made.
The bpcd process compares NetBackup server list entries to the peer name of the server that tries the connection. It rejects the connection if the names are different. If necessary, change the server list entry on the client to match the peer name.
* On Windows clients, check the following:
* Verify that NetBackup for Windows software was installed under a Windows administrator account.
If NetBackup is under another type of account, reinstall it under an administrator account. The installation completes successfully under a non-administrator account except for the following: the NetBackup Client service is not added to Windows and the NetBackup server cannot access the client.
* Verify that the Windows TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers.
UNIX, Linux, and Windows clients are frequently not on the same subnet and use different domain servers. When this condition exists, NetBackup servers and Windows clients may be able to ping one another, but the server still cannot access the Windows client.
* The preceding items may not resolve this problem.
See Resolving network communication problems in the Troubleshooting Guide.
* If NetBackup use multiple network interfaces with media servers, make sure that the interface names appear in the client's /usr/openv/netbackup/bp.conf file.
* For the Enterprise Vault Agent: See the Troubleshooting section of the NetBackup for Enterprise Vault Agent Administrator's Guide.

原來懷疑是伺服器端出現了問題,透過命令檢查,伺服器端可以訪問到客戶端的埠,如下:
C:Documents and Settingsdujiabing>bptestbpcd -client zhjkdb
1 1 1
120.10.12.189:4616 -> 120.10.12.13:13724
120.10.12.189:4618 -> 120.10.12.13:13724
120.10.12.189:4620 -> 120.10.12.13:13724

59:access to the client was not allowed ,表明了是客戶端上的配置有問題.

檢查客戶端的bp.conf檔案,內容如下:
# more /usr/openv/netbackup/bp.conf
SERVER = netbackup
CLIENT_NAME = zhjkdb
#more /etc/hosts
120.10.12.13 zhjkdb
120.10.12.189 netbackup

配置好像都沒有問題.

三.問題解決
仔細分析,這個問題可能是因為客戶端在配置netbackup server的資訊的時候存在問題,檢視另外一些備份正常的客戶端環境,發現在bp.conf檔案中缺少media server的定義.
於是在/usr/openv/netbackup/bp.conf 檔案中增加了media server的定義.如下:
#more /usr/openv/netbackup/bp.conf
SERVER = netbackup
CLIENT_NAME = zhjkdb
MEDIA_SERVER = netbackup-ms

在客戶端,測試帶庫是否可以訪問:
$sbttest "SBT_TAPE"
[oracle@zhjkdb ~]$ sbttest "SBT_TAPE"
The sbt function pointers are loaded from libobk.so library.
-- sbtinit succeeded
-- sbtinit (2nd time) succeeded
sbtinit: Media manager supports SBT API version 2.0
sbtinit: Media manager is version 5.0.0.0
sbtinit: vendor description string=Veritas NetBackup for Oracle - Release 6.5 (2007072323)
sbtinit: allocated sbt context area of 8 bytes
sbtinit: proxy copy is supported
-- sbtinit2 succeeded
-- regular_backup_restore starts ................................
-- sbtbackup succeeded
write 100 blocks
-- sbtwrite2 succeeded
-- sbtclose2 succeeded
sbtinfo2: SBTBFINFO_NAME=SBT_TAPE
sbtinfo2: SBTBFINFO_SHARE=multiple users
sbtinfo2: SBTBFINFO_ORDER=sequential access
sbtinfo2: SBTBFINFO_LABEL=G:diskzhjkdb_1351060391_C1_F1
sbtinfo2: SBTBFINFO_CRETIME=Wed Oct 24 14:33:11 2012
sbtinfo2: SBTBFINFO_EXPTIME=Wed Oct 31 14:33:11 2012
sbtinfo2: SBTBFINFO_COMMENT=Backup ID : zhjkdb_1351060391
sbtinfo2: SBTBFINFO_METHOD=stream
-- sbtinfo2 succeeded
-- sbtrestore succeeded
file was created by this program:
seed=430316798, blk_size=16384, blk_count=100
read 100 buffers
-- sbtread2 succeeded
-- sbtclose2 succeeded
-- sbtremove2 succeeded
-- regular_backup_restore ends ................................

再在netbackup server手動啟動備份,結果成功,問題解決.