sf和nbu双应用上升级pbx的问题请教

Question

aix5.3.10
sf5.0.3rp2
nbu 6.5

由于6.5备份问题，case说升级到6.5.5
升级过程中提示pbx版本低
#lslpp -l | grep pbx
  VRTSpbx                  1.3.17.10  APPLIED    Symantec Private Branch

问题是
我现在系统中有vcs正在跑着，nbu要求升级pbx。怎么个升级法？要停掉vcs吗？之后要reboot吗？

Answer 1

不懂nbu的路过。。

Answer 2

本帖最后由 vovi 于 2010-04-29 13:44 编辑

楼上说的很对呀。多谢
问题如下。其中一个无牙大哥也回复过了。也是建议升级。

第一个问题：
所有备份都包括如下红色警报。请帮忙分析。系统为aix 5.3.10
Warning bpbrm (pid=827742) from client nwdb2: WRN - Unable to backup VxFS Named Data Streams, vxfs_nattr_check failed.  Errno = 25: A specified file does not support the ioctl system call.
第二个问题如下面红色标记，也就是需要我测试的问题。
Error bptm (pid=791026) block read is not a NetBackup or Backup Exec media header, len = 65536, media id SL0400, drive index 2, data is ANSI-format
04/27/2010 17:16:11 - restored from image nwdb2_1272359587; restore time: 0:00:46
04/27/2010 17:16:13 - Warning bprd (pid=774426) Restore must be resumed prior to first image expiration on Tue May 11 17:13:07 BEIST 2010
04/27/2010 17:16:14 - end Restore; elapsed time 0:01:08
04/27/2010 17:53:09 - begin Restore
04/27/2010 17:53:14 - number of images required: 1
04/27/2010 17:53:14 - media needed: SL0401
04/27/2010 17:53:19 - restoring from image hlwdb1_1272361874
04/27/2010 17:53:28 - connecting
04/27/2010 17:53:30 - connected; connect time: 0:00:00
04/27/2010 17:53:31 - started process bptm (pid=62285
04/27/2010 17:53:31 - mounting SL0401
04/27/2010 17:53:29 - requesting resource SL0401
04/27/2010 17:53:29 - granted resource  SL0401
04/27/2010 17:53:29 - granted resource  IBM.ULTRIUM-TD1.006
04/27/2010 17:54:10 - Error bptm (pid=62285 block read is not a NetBackup or Backup Exec media header, len = 65536, media id SL0401, drive index 2, data is ANSI-format
04/27/2010 17:54:11 - Error bptm (pid=83593 The following files/folders were not restored:
04/27/2010 17:54:12 - Error bptm (pid=83593 UTF - /tmp/test/
04/27/2010 17:54:12 - Error bptm (pid=83593 UTF - /tmp/test/1
04/27/2010 17:54:13 - restored from image hlwdb1_1272361874; restore time: 0:00:54
04/27/2010 17:54:14 - Warning bprd (pid=712712) Restore must be resumed prior to first image expiration on Tue May 11 17:51:14 BEIST 2010
04/27/2010 17:54:16 - end Restore; elapsed time 0:01:07
the restore failed to recover the requested files (5)

04/27/2010 17:54:04 - requesting resource nwdb2-hcart-robot-tld-1
04/27/2010 17:54:04 - requesting resource nwdb2.NBU_CLIENT.MAXJOBS.hlwdb1
04/27/2010 17:54:04 - requesting resource nwdb2.NBU_POLICY.MAXJOBS.test_hlwdb1
04/27/2010 17:54:05 - granted resource  nwdb2.NBU_CLIENT.MAXJOBS.hlwdb1
04/27/2010 17:54:05 - granted resource  nwdb2.NBU_POLICY.MAXJOBS.test_hlwdb1
04/27/2010 17:54:05 - granted resource  SL0400
04/27/2010 17:54:05 - granted resource  IBM.ULTRIUM-TD1.004
04/27/2010 17:54:05 - granted resource  nwdb2-hcart-robot-tld-1
04/27/2010 17:54:05 - estimated 38 kbytes needed
04/27/2010 17:54:06 - started process bpbrm (pid=745544)
04/27/2010 17:54:07 - connecting
04/27/2010 17:54:22 - Warning bpbrm (pid=745544) from client hlwdb1: WRN - Unable to backup VxFS Named Data Streams, vxfs_nattr_check failed.  Errno = 25: A specified file does not support the ioctl system call.
04/27/2010 17:54:19 - connected; connect time: 0:00:00
04/27/2010 17:54:25 - mounting SL0400
04/27/2010 17:55:02 - Error bptm (pid=856372) block read is not a NetBackup or Backup Exec media header, len = 65536, media id SL0400, drive index 0, data is ANSI-format
04/27/2010 17:55:02 - Error bptm (pid=856372) non NetBackup media found in drive index 0, FREEZING SL0400
04/27/2010 17:55:02 - mounted SL0400; mount time: 0:00:37
04/27/2010 17:55:02 - current media SL0400 complete, requesting next media Any
04/27/2010 17:55:09 - granted resource  SL0401
04/27/2010 17:55:09 - granted resource  IBM.ULTRIUM-TD1.006
04/27/2010 17:55:09 - granted resource  nwdb2-hcart-robot-tld-1
04/27/2010 17:55:11 - mounted SL0401
04/27/2010 17:55:11 - positioning SL0401 to file 3
04/27/2010 17:55:11 - positioned SL0401; position time: 0:00:00
04/27/2010 17:55:11 - begin writing

虚拟带库是emc sedl2060
master server上有个vtl。每次备份会报第二个问题的错误。
而另外一台vtl的media server就没问题。vtl微码相同。升级到6.5.5主要是为了解决上面第一个问题。

Answer 3

本帖最后由 paul.cz 于 2010-04-29 11:42 编辑

什么问题，为什么要你升级到6.5.5？
你问清楚，让他们的800给一个需要升级到6.5.5版本的充足的理由？别听他们的，遇到问题就让升级，真是瞎指挥。

BTW，把你遇到的问题详细描述一下贴上来，让坛子里的兄弟们帮你分析一下。