Netbackup 6.5.4日志位置及查看

一.统一日志：

统一日志记录（此 6.0 版本中的新增功能）以所有 VERITAS 产品通用的标准格式创建日志
文件名和消息。统一日志记录供某些 NetBackup 进程使用，这些进程多数为服务器进程。

默认为/usr/openv/logs
查看它的位置和配置：
[root@nbu-server logs]# vxlogcfg -l -o nbrb -p NB
Configuration settings for originator 118, of product 51,216...
LogDirectory = /usr/openv/logs/
DebugLevel = 1
DiagnosticLevel = 1
LogToStdout = False
LogToStderr = False
LogToOslog = False
RolloverMode = FileSize
LogRecycle = False
MaxLogFileSizeKB = 5120
RolloverPeriodInSeconds = 43200
RolloverAtLocalTime = 0:00
NumberOfLogFiles = 3
IDNames = nbrb
L10nLib = /usr/openv/lib/libvxexticu.so
L10nResource = nbrb
L10nResourceDir = /usr/openv/resources
SyslogIdent = VRTS-NB
SyslogOpt = 0
SyslogFacility = LOG_LOCAL5
LogFilePermissions = 664

[root@nbu-server logs]# ls
51216-111-8323328-081208-0000000000.log 51216-118-8323328-081208-0000000000.log
51216-116-8323328-081208-0000000000.log 51216-127-8323328-081208-0000000000.log
51216-117-8323328-081208-0000000000.log 51216-132-8323328-081208-0000000000.log

日志文件内容：
[root@nbu-server logs]# more 51216-163-8323328-081208-0000000000.log
$Header 65543,51216,163,1228729263,-28800,nbu-server
0,51216,137,163,1,1228729263803,7233,4395328,0:,117:logging configuration set to Svc Debug = 1 Svc Diag = 1 Lib Debug = 1 Lib Diag
= 1 Orb Level = 0(OrbService.cpp:819),30:OrbService::configureLogging_u,1
0,51216,137,163,2,1228729263805,7233,4395328,0:,73:=====================================================(OrbService.cpp:727),24:OrbS
ervice::setupLogging,1
0,51216,137,163,3,1228729263805,7233,4395328,0:,52: nbsvcmon Starting (OrbService.cpp:728),24:OrbService::setupLogging,
1
0,51216,137,163,4,1228729263805,7233,4395328,0:,73:=====================================================(OrbService.cpp:729),24:OrbS
ervice::setupLogging,1
0,51216,163,163,1,1228729263806,7233,4395328,0:,

日志格式比较难懂，可以用下面的方式查看：

显示最近 20 分钟内发布的发起方 116 (nbpem) 的日志消息：
vxlogview -o 116 -t 00:20:00

显示特定时间段内发布的 nbpem 的日志消息：
vxlogview -o nbpem -b "05/03/05 06:51:48 AM" -e "05/03/05 06:52:48 AM"

举例，查看一分钟内的日志：
[root@nbu-server logs]# vxlogview -t 00:01:00
12/21/2008 17:43:54.542 [SchedEventHandler::handle_timeout] House keeping timer(SchedEventHandler.cpp:161)
12/21/2008 17:43:54.553 [JobScheduler::scheduleNextJob] next due job at 1229875200 (Mon Dec 22 00:00:00 2008 )(JobScheduler.cpp:2601)
12/21/2008 17:43:54.558 [JobScheduler::scheduleNextJob] setting timer for 1229875200 (Mon Dec 22 00:00:00 2008 ,0x060617b0), jobs currently active 0(JobScheduler.cpp:2629)
12/21/2008 17:43:54.559 [JobScheduler::scheduleNextJob] policy = bk_etc(JobScheduler.cpp:2631)
12/21/2008 17:43:54.560 [JobScheduler::scheduleNextJob] schedule = Differential-Inc(JobScheduler.cpp:2632)
12/21/2008 17:43:59.944 [DeviceConfigImpl::getRBCacheDriveList] Cli <Host=&lt;nbu-server> APP=<nbrb> PID=<2548>&gt;
12/21/2008 17:43:59.945 [DeviceConfigImpl::getRBCacheDriveList] MasterServer <nbu-server>
12/21/2008 17:44:00.025 [DeviceConfigImpl::getRBCacheDriveList] retval = < 0 >

二.传统 NetBackup 日志记录
这个不多说，以前版本就有
统一日志记录由某些 NetBackup 进程使用。所有其他的 NetBackup 进程都使用传统日志记录。

默认目录为/usr/openv/netbackup/logs。
在传统调试日志记录中，每个进程都在自己的日志记录目录中创建日志。要在 NetBackup服务器上启用传统调试日志记录就要在该目录中创建相应进程的目录。

在/usr/openv/netbackup/logs中提供了一个小脚本mklogdir，可以用来创建所有进程对应的目录：
并且Netbackup官方文档也有一个说明列表：调试日志目录 相关进程
admin 管理命令。
bpbrm NetBackup 备份和恢复管理器。
bpcd NetBackup 客户机后台驻留程序/ 管理器。此进程由 NetBackup 客户机服务启动。
bpcoord 由 bpsynth 启动的 NetBackup 进程，用于监视介质服务器上的
bptm/bpdm 进程以读取要合成的组件映像。bpcoord 在主服务器上运行。
bpdbjobs NetBackup 作业数据库管理器程序。
bpdm NetBackup 磁盘管理器。
bpdbm NetBackup 数据库管理器。此进程仅在主服务器上运行。在 Windows系统上，它是 NetBackup 数据库管理器服务。
bpjava-msvc 在 NetBackup Java 界面应用程序启动期间，由 UNIX 服务器上的 inetd或 Windows 服务器上的“客户机服务”服务启动的 NetBackup-Java 应用程序服务器身份验证服务。此程序验证启动应用程序的用户的身份。
bpjava-susvc 通过在 NetBackup-Java 界面启动时出现的“登录(Login)”对话框成功登录之后，由 bpjava-msvc 启动的 NetBackup 程序。此程序为所有来自正在运行 bpjava-msvc 的 NetBackup 主服务器或介质服务器主机上的 Java 用户界面中的所有请求提供服务（在所有 Windows 平台上）。
bprd NetBackup 请求后台驻留程序/ 管理器。在 Windows 系统上，此进程称为 NetBackup 请求管理器服务。
bpsynth 由 nbgenjob 启动的 NetBackup 进程，用于合成备份。bpsynth 在主服务器上运行。
bptm NetBackup 磁带或光盘介质管理进程。
symlogs 系统日志。
user_ops 在所有服务器和客户机上安装 NetBackup 的过程中，会创建 user_ops目录。NetBackup Java 界面程序用此目录存储临时文件以及由用户备份、归档和恢复程序 (jbpSA) 生成的作业和进度日志文件。为保证所有 Java程序的成功运行，此目录必须存在，而且必须拥有公共读取、写入和执行的权限。user_ops 将包含每个正在使用 Java 程序的用户的目录。此外，在支持 NetBackup-Java 的平台上， NetBackup Java 界面日志文件将写入称为 nbjlogs 的子目录中。user_ops 目录分层结构中的所有
文件都将根据 KEEP_LOGS_DAYS 配置选项的设置而被删除。
vnetd VERITAS 网络后台驻留程序，用于创建“防火墙友好的”套接字连接。由 inetd(1M) 进程启动。
注意对于此 6.0 版以前的版本，在 UNIX 上， vnetd 日志目录位于/usr/openv/logs 中，而不是
/usr/openv/netbackup/logs 中。对于 6.0 版，将在这两个位置中包含 vnetd 目录的那一位置执行日志记录。如果两个位置中都存在 vnetd 目录，则日志记录仅在/usr/openv/netbackup/logs/vnetd 中执行。

一旦创建了这些目录，配合合适的日志级别(一般默认)，只要去对应的目录查找需要的日志就好了。

三.job执行过程的详细日志
/usr/openv/netbackup/db/jobs/trylogs在这个目录中会有每个job的详细执行过程，例如，刚执行了一个测试备份:
jobid为221，备份/etc,并且是增量备份，server为nbu-server,client为nbu-server,策略为bk_etc,存储单元为bkdisk.

则文件名为：221.t
其中就会有记录：
[root@nbu-server trylogs]# more 221.t
PROCESS 1229853538 2357 bpdm
Try 1
REQUESTING_RESOURCE 1229853534 bkdisk
REQUESTING_RESOURCE 1229853534 nbu-server.NBU_CLIENT.MAXJOBS.nbu-server
REQUESTING_RESOURCE 1229853534 nbu-server.NBU_POLICY.MAXJOBS.bk_etc
RESOURCE_GRANTED 1229853535 nbu-server.NBU_CLIENT.MAXJOBS.nbu-server
RESOURCE_GRANTED 1229853535 nbu-server.NBU_POLICY.MAXJOBS.bk_etc
RESOURCE_GRANTED 1229853535 bkdisk
PROCESS 1229853537 2351 bpbrm
CONNECT 1229853537
CONNECTED 1229853537
BEGIN_WRITING 1229853539
FW 1229853541 1
PATH_WRITTEN 1229853541 /etc/
KBW 1229853543 32 8.384
FW 1229853543 3
PATH_WRITTEN 1229853543 /etc/cups/certs/0
END_WRITING 1229853544
Started 1229853535
KbPerSec 8
Kilobytes 32
Files 4
ActivePid 2351
Status 0
DestStorageUnit bkdisk
DestMediaServer nbu-server
Ended 1229853551上面的内容就不多说了，看看就能明白

四.Media server调试日志
需要创建下面的目录：
/usr/openv/volmgr/debug/daemon （有关该服务的调试信息）
/usr/openv/volmgr/debug/ltid （有关 ltid 的调试信息）
/usr/openv/volmgr/debug/reqlib （有关请求该服务的进程的调试信息）
/usr/openv/volmgr/debug/tpcommand （有关 tpconfig 和 tpautoconf 命令的调试信息）

例如创建完这几个这些目录后执行tpconfig添加drive /dev/xxxx,则在tpcommand下面会有日志：
[root@nbu-server tpcommand]# more log.122208
17:57:54.488 [3933] <4> tpconfig: emmserver_name = nbu-server
17:57:54.488 [3933] <4> tpconfig:main(): tpconfig
17:57:54.489 [3933] <2> mm_getnodename: cached_hostname nbu-server, cached_method 3
17:57:54.506 [3933] <2> mm_getnodename: (3) hostname nbu-server (from mm_master_config.mm_server_name)
17:57:54.507 [3933] <4> InitThisHostName: ThisHost is nbu-server
17:57:54.507 [3933] <4> tpconfig: emmserver_port = 1556
17:57:54.574 [3933] <2> VssGetFQDNHostName: vss_auth.cpp.3997: Function: VssGetFQDNHostName. Search name
17:57:54.574 [3933] <2> VssInit: vss_auth.cpp.716: Function: VssInit. Using Cached entries FALSE
17:57:54.585 [3933] <2> vnet_get_user_credential_path: vnet_vxss.c.931: status: 35 0x00000023
17:58:02.608 [3933] <16> emmlib_GetDeviceList: (0) MasterServer = null, MachineName = nbu-server
17:58:14.595 [3933] <4> get_ndmp_host_from_path: user path = /dev/xxxx
17:58:14.596 [3933] <4> get_ndmp_host_from_path: path is not ndmp

官方文档：

Details:
On Windows clients, the following steps are used:

1. Create the \\<install_path>\NetBackup\logs\bpbkar directory. Generated log information will be placed in this directory in a file named mmddyy.log (where mm = month, dd = date, yy = year).
2. Create an empty file called \\<install_path>\NetBackup\bpbkar_path_tr (ensure that the file has no extension and is named as defined)
3. Enable logging for the desired system by setting the 'Global logging level' to 5(maximum). This can be found in the Logging tab of the Host Properties | Clients | Properties section of the NetBackup Administration Console.
4. Restart the 'NetBackup Client Service' in the Control Panel Services applet (usually contained within Administrative Tools)
5. Run a backup to generate the log information

On UNIX clients, the following steps are used:

1. Create the bpbkar debug log directory by running mkdir /<install_path>/netbackup/logs/bpbkar. Generated log information will be placed in this directory in a file named log.mmddyy (where mm = month, dd = date, yy = year).
2. Create a file named touch /<install_path>/netbackup/bpbkar_path_tr to enable extended bpbkar debug logging
3. Enable logging for the desired system by setting the Global logging level to 5(maximum). This can be found in the 'Logging' tab of the Host Properties | Clients                  | Properties section of the NetBackup Administration Console.
4. Run a backup to generate the log information

Note that the use of this "touch" file will cause radically larger bpbkar logs than the usual (even at a logging level of 5). Refer to the UNIX / Windows Troubleshooting Guide for more specifics on debug logs.

Problem
Backups of large Notes? databases terminate with the error message:
Lotus ERROR [14352]: Backup terminated due to timeout.

How can this be remedied?
Solution
By default the Notes API functions used in third party backup software allow 15 minutes for each backup unit to complete before timing out. This is to cater to any potential server hangs that could prevent the backup from completing. A backup unit may be a single database or it may be a group of databases. This depends on the backup software.

To increase the timeout interval use the notes.ini parameter
BACKUP_TIMEOUT=xx
where xx is the number of minutes to allow for the backup before timing out.

Alternatively, it is possible to set a different notes.ini parameter
BACKUP_NO_TIMEOUT=1
which results in no timeout. However, there is potential danger of this leading to a backup run which lasts forever, because it is waiting for a condition that will never be fullfilled.

NOTE: Only one of these parameters should be set.

Supporting information:

The time taken while the backup server waits for another tape, when operator intervention is required, is included in the timeout calculation