[已解决]求NBU6.0 Catalog备份问题解决方法

柯雅

NBU.60Catalog 完全备份时，两个子进程显示备份成功，但父进程却显示部份备份成功（显示状态ID为1，正常应该为0才对），如下图：





查看备份日志如下：
# ./bperror -d 09/18/2008
1221667200 1 4 4 erp1 518 0 0 erp1 nbpem client erp1 handling path CATALOG_DRIVEN_BACKUP
1221667200 1 2 4 erp1 0 0 0 *NULL* nbjm started backup job (jobid=51 for client erp1, policy NBU_Catalog_Backup, schedule Full
1221667200 1 4 4 erp1 518 518 0 erp1 nbjm starting backup job (jobid=51
1221667201 1 2 4 erp1 0 0 0 *NULL* bpdbm **************** GOOD MORNING ****************
1221667256 1 4 4 erp1 519 -1 0 erp1 nbpem client erp1 handling path /usr/openv/db/staging/EMM_DATA.db
1221667256 1 2 4 erp1 0 0 0 *NULL* nbjm started backup job (jobid=519) for client erp1, policy NBU_Catalog_Backup, schedule Full
1221667257 1 4 4 erp1 519 518 0 erp1 nbjm starting backup job (jobid=519)
1221667342 1 4 4 erp1 519 518 0 erp1 bptm begin writing backup id erp1_1221667257, copy 1, fragment 1, to media id 000010 on drive index 1
1221667358 1 4 4 erp1 519 518 0 erp1 bptm successfully wrote backup id erp1_1221667257, copy 1, fragment 1, 61312 Kbytes at 9144.221 Kbytes/sec
1221667359 1 68 4 erp1 519 518 0 erp1 nbpem CLIENT erp1  POLICY NBU_Catalog_Backup  SCHED Full  EXIT STATUS 0 (the requested operation was successfully completed)
1221667360 1 4 4 erp1 520 518 0 erp1 nbpem client erp1 handling path CATALOG_DRIVEN_BACKUP
1221667360 1 2 4 erp1 0 0 0 *NULL* nbjm started backup job (jobid=520) for client erp1, policy NBU_Catalog_Backup, schedule Full
1221667361 1 4 4 erp1 520 518 0 erp1 nbjm starting backup job (jobid=520)
1221667366 1 4 4 erp1 520 518 0 erp1 bptm begin writing backup id erp1_1221667361, copy 1, fragment 1, to media id 000010 on drive index 1
1221667383 1 4 4 erp1 520 518 0 erp1 bptm successfully wrote backup id erp1_1221667361, copy 1, fragment 1, 205280 Kbytes at 12997.341 Kbytes/sec
1221667395 1 68 4 erp1 520 518 0 erp1 nbpem CLIENT erp1  POLICY NBU_Catalog_Backup  SCHED Full  EXIT STATUS 0 (the requested operation was successfully completed)
1221667396 1 68 4 unknown 518 0 0 erp1 nbpem CLIENT erp1  POLICY NBU_Catalog_Backup  SCHED Full  EXIT STATUS 1 (the requested operation was partially successful)
1221667396 1 4 16 erp1 518 0 0 erp1 nbpem backup of client erp1 exited with status 1 (the requested operation was partially successful)
1221683635 1 2 4 erp1 0 0 0 *NULL* nbpem cleaning image DB
1221683635 1 2 4 erp1 0 0 0 *NULL* bpdbm Cleanup running in background, pid=5100
1221683635 1 2 4 erp1 0 0 0 *NULL* bpdbm Deleting Expired Images
1221683636 1 2 4 erp1 0 0 0 *NULL* bpdbm deleted 3 expired records, compressed 0, tir removed 0, indexed 0, deleted 0 expired copies
1221683636 1 2 4 erp1 0 0 0 bpexpdate bpexpdate Deassigned 0 out of 4 media-ids found.
1221726070 1 4 4 erp1 521 -1 0 erp1 nbpem client erp1 handling path CATALOG_DRIVEN_BACKUP
1221726070 1 2 4 erp1 0 0 0 *NULL* nbjm started backup job (jobid=521) for client erp1, policy NBU_Catalog_Backup, schedule Full
1221726070 1 4 4 erp1 521 521 0 erp1 nbjm starting backup job (jobid=521)
1221726120 1 4 4 erp1 522 -1 0 erp1 nbpem client erp1 handling path /usr/openv/db/staging/EMM_DATA.db
1221726120 1 2 4 erp1 0 0 0 *NULL* nbjm started backup job (jobid=522) for client erp1, policy NBU_Catalog_Backup, schedule Full
1221726120 1 4 16 erp1 522 521 0 erp1 nbjm NBU status: 96, EMM status: No media is available
1221726120 1 68 4 unknown 522 521 0 erp1 nbpem CLIENT erp1  POLICY NBU_Catalog_Backup  SCHED Full  EXIT STATUS 96 (unable to allocate new media for backup, storage unit has none available)
1221726120 1 4 16 erp1 522 -1 0 erp1 nbpem backup of client erp1 exited with status 96 (unable to allocate new media for backup, storage unit has none available)
1221726130 1 68 4 unknown 521 -1 0 erp1 nbpem CLIENT erp1  POLICY NBU_Catalog_Backup  SCHED Full  EXIT STATUS 2 (none of the requested files were backed up)
1221726130 1 4 16 erp1 521 -1 0 erp1 nbpem backup of client erp1 exited with status 2 (none of the requested files were backed up)
1221726130 1 4 16 erp1 521 -1 0 erp1 nbpem [1] suspending further backup attempts for client erp1, policy NBU_Catalog_Backup, schedule Full: exceeded configured number of tries
1221726130 1 2 4 erp1 0 0 0 *NULL* nbpem [3] backup of client erp1, policy NBU_Catalog_Backup, is suspended: exceeded configured number of tries for a schedule





恳求解决方法？CataLog备份策略应该没问题吧！如下：






[ 本帖最后由 柯雅 于 2008-11-3 10:06 编辑 ]

阿拉丁神灯

你这个问题真的是太搞笑了，我从没见过catalog backup是黄色小人的
很遗憾的是我也不知道怎么解决,不过我觉得如果条件允许的话你可以做一下catalog的恢复测试,试试能不能成功,如果不能就根据结果反推一下backup的问题.
另外,catalog的policy配置没有问题.
再另外,你标记的哪个红色日志也不是问题.
我以前有个备份文件的policy也是黄色小人,结果我发现是因为NBU统计的文件大小和操作系统统计的大小不一样.我将黄色小人备份恢复了一下是没有问题的.

柯雅

现在主要是备份状态为1，在面板Report---Problem中，全显示相关Job ID状态为ERROR，让客户看得很不爽。

还是肯求各位解决之法！

david5337

打打最新的补丁嘛！！！
最好还是使用offline catalog备份方式吧，不会有啥子问题的；online catalog备份，MS不可靠，我都不用这种方式的！！

alex_linux

我最恨的error code 就是 1

柯雅

真晕，找不到解决方法，郁闷呀！

求Error Code=1，解决方法？

alex_linux

1221726120 1 4 16 erp1 522 521 0 erp1 nbjm NBU status: 96, EMM status: No media is available
1221726120 1 68 4 unknown 522 521 0 erp1 nbpem CLIENT erp1  POLICY NBU_Catalog_Backup  SCHED Full  EXIT STATUS 96 (unable to allocate new media for backup, storage unit has none available)

你空间不够了吧...

柯雅

我查了磁盘和NBU卷所在磁带的空间，还剩余有很多呢？根本还没用完！

Catalog备份的东西本来就很少，我用的是LTO2的磁带，不会那么快用完的。那又是什么原因呢？alex_linux

alex_linux

server 重启试试
这个文档可能对你有用
http://support.veritas.com/docs/280181

柯雅

还是没解决呀？
跪求解决方法？