最近很郁闷遇到好多错误
环境：masterA:windows2003 NBU6.0 MP4 SERVER 接了个小的阵列client B:solaris 10 .5.1 NBU CLIENTsybaseoption 安装了 sybase
容灾服务器：C：solaris 10 5.1NBU CLIENT sybaseoption sybase 容灾库
工作原理 A备份B的sybase 形成image 文件存放到A的阵列里来，在C的机器上做计划任务定时恢复image文件到容灾库上 使容灾库上的sybase和他本地的sybase数据同步
经过测试 脚本和方案都可行并且已经运行2个月
现在出错问题如下：能够正常备份 远程本地的sybase库！但是在恢复到容灾库上时候出错下面是他们详细的错误
NBUdetail:
2008-4-15 4:28:45 - Error bpbrm(pid=16220) client restore EXIT STATUS 183: tar received an invalid archive
2008-4-15 4:28:47 - end reading; read time: 00:00:06
2008-4-15 4:28:47 - restored image ntgzfy_1208174401 - (the requested operation was successfully completed(0)); restore time 00:00:07
2008-4-15 4:28:49 - Warning bprd(pid=14036) Restore must be resumed prior to first image expiration on 04/27/08 07:00:00
2008-4-15 4:28:49 - end Restore; elapsed time: 01:06:49
the requested operation was partially successful(1)
The job was successfully completed, but some files may have been
busy or unaccessible. See the problems report or the client's logs for more details.
2008-4-15 2:22:54 - begin reading
2008-4-15 3:20:49 - Error bpdm(pid=13240) wait for child pid 14256 timeout
2008-4-15 3:20:50 - Error bpdm(pid=14256) The following files/folders were not restored:
2008-4-15 3:20:50 - Error bpdm(pid=14256) UTF - /GZFY.JUDGE.D.0.24281.14-04-2008.22:14:23
2008-4-15 3:20:50 - end reading; read time: 00:57:56
2008-4-15 3:20:51 - restored image ntgzfy_1208179804 - (network connection timed out(41)); restore time 00:58:06
2008-4-15 3:20:54 - end Restore; elapsed time: 00:58:11
the restore failed to recover the requested files(5)
2008-4-15 3:20:55 - Error bpbrm(pid=12140) client restore EXIT STATUS 41: network connection timed out
在容灾库上看到sybase的日志 如下
Apr 18 03:45:16 2008: D00: SYBMULTBUF ERROR: Emulator interprocess communication failed with error state = 11, error code=0, system message=Pipe I/O
returned 0 bytes.
Apr 18 03:45:16 2008: Open Server Error: 16248.10.0: Error in srv_select() - file descriptor 179 is no longer active
.
Apr 18 03:45:16 2008: Backup Server: 4.145.2.73: Error for device 'sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38 -CLIENT ntgzfy ::00'. Pipe I/O
returned 0 bytes
Apr 18 03:45:16 2008: Backup Server Internal Error: 4.62.3.4: Multibuffering subprocesses died, archive sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38
-CLIENT ntgzfy ::00.
Apr 18 03:45:16 2008: Backup Server Internal Error: 4.62.3.3: Multibuffering subprocesses died, archive sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38
-CLIENT ntgzfy ::00.
Apr 18 03:45:16 2008: Backup Server: 4.141.2.66: The 'write' call failed for device 'sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38 -CLIENT ntgzfy
::00' with error number 32 (Broken pipe). Refer to your operating system documentation for further details.
Apr 18 03:45:16 2008: Backup Server Internal Error: 4.62.3.8: Multibuffering subprocesses died, archive sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38
-CLIENT ntgzfy ::00.
Apr 18 03:45:16 2008: Backup Server: 6.32.2.3: sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38 -CLIENT ntgzfy ::00: volume not valid or not requested
(server: , session id: 116.)
Apr 18 03:45:16 2008: Backup Server: 1.14.2.4: Unrecoverable I/O or volume error.This DUMP or LOAD session must exit.
Apr 18 03:45:16 2008: Backup Server: 4.141.2.66: The 'write' call failed for device 'sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38 -CLIENT ntgzfy
::00' with error number 32 (Broken pipe). Refer to your operating system documentation for further details.
Apr 18 03:45:16 2008: Backup Server Internal Error: 4.62.3.8: Multibuffering subprocesses died, archive sybackup::GZFY.JUDGE.D.0.27500.17-04-2008.22:14:38
-CLIENT ntgzfy ::00.
我判断的结论 1，是sybase 库进程死！重启备份库 问题依然
2，认为是备份没成功 所以手动备份了一次成功 但是恢复还是失败
求助 ：请问是什么问题引起的？ 该怎么解决 ？
请注意是恢复失败 ！！不要怀疑脚本！他是正确的 ！！
本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u1/41933/showart_571217.html
页:
[1]