HP DP 备份问题

unmark

[Normal] From: BSM@dpserver "gzyb_Archive"  Time: 2012/4/17 16:26:10
        Backup session 2012/04/17-10 started.

[Normal] From: BSM@dpserver "gzyb_Archive"  Time: 2012/4/17 16:26:10
        OB2BAR application on "gzyb" successfully started.

[Normal] From: ob2rman@gzyb-1 "gzyb"  Time: 04/17/12 16:08:29
        Starting backup of target database.

        Net service name: gzyb.
        Instance status: OPEN.
        Instance name: gzyb.
        Database DBID = 674479683.
        Database control file type: CURRENT.
        Database log mode: ARCHIVELOG.


[Normal] From: ob2rman@gzyb-1 "gzyb"  Time: 04/17/12 16:08:30
        Starting Oracle Recovery Manager.


Recovery Manager: Release 9.2.0.1.0 - 64bit Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

RMAN> CONNECT TARGET *
2> HOST 'exit';
3> run {
4> allocate channel 'dev_0' type 'sbt_tape'
5> parms 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.sl,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gzyb,OB2BARLIST=gzyb_Archive)';
6>
7> send device type 'sbt_tape' 'OB2BARHOSTNAME=gzyb';
8> backup
9>  format 'gzyb_Archive<gzyb_%s:%t:%p>.dbf'
10>  archivelog all
11>  delete input;
12> }
13> EXIT
RMAN-06005: connected to target database: GZYB (DBID=674479683)
RMAN-06009: using target database controlfile instead of recovery catalog


RMAN-08030: allocated channel: dev_0
RMAN-08500: channel dev_0: sid=54 devtype=SBT_TAPE
RMAN-08526: channel dev_0: Data Protector A.06.11/243

RMAN-06421: sent command to channel: dev_0

RMAN-03090: Starting backup at 17-APR-12
RMAN-03033: current log archived
RMAN-08009: channel dev_0: starting archive log backupset
RMAN-08014: channel dev_0: specifying archive log(s) in backup set
RMAN-08504: input archive log thread=1 sequence=2475 recid=2337 stamp=780340314
RMAN-08504: input archive log thread=1 sequence=2476 recid=2338 stamp=780399076
RMAN-08504: input archive log thread=1 sequence=2477 recid=2339 stamp=780403845
RMAN-08504: input archive log thread=1 sequence=2478 recid=2340 stamp=780410627
RMAN-08504: input archive log thread=1 sequence=2479 recid=2341 stamp=780424052
RMAN-08504: input archive log thread=1 sequence=2480 recid=2342 stamp=780487020
RMAN-08504: input archive log thread=1 sequence=2481 recid=2343 stamp=780497021
RMAN-08504: input archive log thread=1 sequence=2482 recid=2344 stamp=780567075
RMAN-08504: input archive log thread=1 sequence=2483 recid=2345 stamp=780583420
RMAN-08504: input archive log thread=1 sequence=2484 recid=2346 stamp=780669831
RMAN-08504: input archive log thread=1 sequence=2485 recid=2347 stamp=780744715
RMAN-08504: input archive log thread=1 sequence=2486 recid=2348 stamp=780756222
RMAN-08504: input archive log thread=1 sequence=2487 recid=2349 stamp=780784511
RMAN-08504: input archive log thread=1 sequence=2488 recid=2350 stamp=780834757
RMAN-08504: input archive log thread=1 sequence=2489 recid=2351 stamp=780842557
RMAN-08504: input archive log thread=1 sequence=2490 recid=2352 stamp=780854926
RMAN-08038: channel dev_0: starting piece 1 at 17-APR-12
[Normal] From: BMA@gzyb-1 "HP:Ultrium 4-SCSI_4"  Time: 2012/4/17 16:08:48
        STARTING Media Agent "HP:Ultrium 4-SCSI_4"

[Warning] From: BMA@gzyb-1 "HP:Ultrium 4-SCSI_4"  Time: 2012/4/17 16:10:43
[90:54]         
        Cannot open device (/dev/rmt/6mn)

[Normal] From: BMA@gzyb-1 "HP:Ultrium 4-SCSI_4"  Time: 2012/4/17 16:10:43
        ABORTED Media Agent "HP:Ultrium 4-SCSI_4"

[Major] From: OB2BAR_SBT_CHANNEL@gzyb-1 "gzyb"  Time: 2012/4/17 16:10:43
        Received ABORT request from RSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

RMAN-08031: released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 04/17/2012 16:11:23
ORA-19506: failed to create sequential file, name="gzyb_Archive<gzyb_5552:780854926:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   Vendor specific error: OB2_StartObjectBackup() failed ERR(-17)

Recovery Manager complete.
[Major] From: ob2rman@gzyb-1 "gzyb"  Time: 04/17/12 16:11:24
        External utility reported error.

RMAN PID=14614

[Major] From: ob2rman@gzyb-1 "gzyb"  Time: 04/17/12 16:11:24
        The database reported error while performing requested operation.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on dev_0 channel at 04/17/2012 16:11:23
ORA-19506: failed to create sequential file, name="gzyb_Archive<gzyb_5552:780854926:1>.dbf", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
    Vendor specific error: OB2_StartObjectBackup() failed ERR(-17)

Recovery Manager complete.

[Major] From: ob2rman@gzyb-1 "gzyb"  Time: 04/17/12 16:11:24
        Oracle Recovery Manager completed with errors.

[Major] From: ob2rman@gzyb-1 "gzyb"  Time: 04/17/12 16:11:24
        Backup of target database failed.

[Normal] From: BSM@dpserver "gzyb_Archive"  Time: 2012/4/17 16:29:07
        OB2BAR application on "gzyb" disconnected.

[Critical] From: BSM@dpserver "gzyb_Archive"  Time: 2012/4/17 16:29:07
        None of the Disk Agents completed successfully.
        Session has failed.

[Normal] From: BSM@dpserver "gzyb_Archive"  Time: 2012/4/17 16:29:07

        Backup Statistics:
         
                Session Queuing Time (hours)         0.00        
                -------------------------------------------      
                Completed Disk Agents ........          0         
                Failed Disk Agents ...........          1         
                Aborted Disk Agents ..........          0         
                -------------------------------------------      
                Disk Agents Total  ...........          1         
                ===========================================      
                Completed Media Agents .......          0         
                Failed Media Agents ..........          1         
                Aborted Media Agents .........          0         
                -------------------------------------------      
                Media Agents Total  ..........          1         
                ===========================================      
                Mbytes Total .................       0 MB        
                Used Media Total .............          0         
                Disk Agent Errors Total ......          0   


============================================================================
                      Session failed!
============================================================================
带库是VLS虚拟的MSL6000，提示不能open diver，但是主机端测试查看如下：
ioscan -fnC tape
Class     I  H/W Path      Driver S/W State   H/W Type     Description
=======================================================================
tape      0  0/0/1/0.2.0   stape  CLAIMED     DEVICE       HP      Ultrium 1-SCSI
                          /dev/rmt/0m            /dev/rmt/0mn           /dev/rmt/c0t2d0BEST    /dev/rmt/c0t2d0BESTn
                          /dev/rmt/0mb           /dev/rmt/0mnb          /dev/rmt/c0t2d0BESTb   /dev/rmt/c0t2d0BESTnb
tape      1  0/12/0/0.1.7.255.0.0.1  stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/1m             /dev/rmt/1mn            /dev/rmt/c11t0d1BEST    /dev/rmt/c11t0d1BESTn
                          /dev/rmt/1mb            /dev/rmt/1mnb           /dev/rmt/c11t0d1BESTb   /dev/rmt/c11t0d1BESTnb
tape      2  0/12/0/0.1.7.255.0.0.2  stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/2m             /dev/rmt/2mn            /dev/rmt/c11t0d2BEST    /dev/rmt/c11t0d2BESTn
                          /dev/rmt/2mb            /dev/rmt/2mnb           /dev/rmt/c11t0d2BESTb   /dev/rmt/c11t0d2BESTnb
tape      3  0/12/0/0.1.7.255.0.0.3  stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/3m             /dev/rmt/3mn            /dev/rmt/c11t0d3BEST    /dev/rmt/c11t0d3BESTn
                          /dev/rmt/3mb            /dev/rmt/3mnb           /dev/rmt/c11t0d3BESTb   /dev/rmt/c11t0d3BESTnb
tape      4  0/12/0/0.1.7.255.0.0.4  stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/4m             /dev/rmt/4mn            /dev/rmt/c11t0d4BEST    /dev/rmt/c11t0d4BESTn
                          /dev/rmt/4mb            /dev/rmt/4mnb           /dev/rmt/c11t0d4BESTb   /dev/rmt/c11t0d4BESTnb
tape      5  1/4/0/0.2.7.255.0.0.1   stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/5m             /dev/rmt/5mn            /dev/rmt/c20t0d1BEST    /dev/rmt/c20t0d1BESTn
                          /dev/rmt/5mb            /dev/rmt/5mnb           /dev/rmt/c20t0d1BESTb   /dev/rmt/c20t0d1BESTnb
tape      6  1/4/0/0.2.7.255.0.0.2   stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/6m             /dev/rmt/6mn            /dev/rmt/c20t0d2BEST    /dev/rmt/c20t0d2BESTn
                          /dev/rmt/6mb            /dev/rmt/6mnb           /dev/rmt/c20t0d2BESTb   /dev/rmt/c20t0d2BESTnb
tape      7  1/4/0/0.2.7.255.0.0.3   stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/7m             /dev/rmt/7mn            /dev/rmt/c20t0d3BEST    /dev/rmt/c20t0d3BESTn
                          /dev/rmt/7mb            /dev/rmt/7mnb           /dev/rmt/c20t0d3BESTb   /dev/rmt/c20t0d3BESTnb
tape      8  1/4/0/0.2.7.255.0.0.4   stape  CLAIMED     DEVICE       HP      Ultrium 4-SCSI
                          /dev/rmt/8m             /dev/rmt/8mn            /dev/rmt/c20t0d4BEST    /dev/rmt/c20t0d4BESTn
                          /dev/rmt/8mb            /dev/rmt/8mnb           /dev/rmt/c20t0d4BESTb   /dev/rmt/c20t0d4BEST
mc  -p /dev/rac/c11t0d0 -r DS
DT_slot_1 EMPTY
DT_slot_2 EMPTY
DT_slot_3 EMPTY
DT_slot_4 EMPTY
ST_slot_1 FULL HBQ201
ST_slot_2 FULL HBQ202
ST_slot_3 FULL HBQ203
ST_slot_4 FULL HBQ204
ST_slot_5 FULL HBQ205
ST_slot_6 FULL HBQ206
ST_slot_7 FULL HBQ207
ST_slot_8 FULL HBQ208
ST_slot_9 FULL HBQ209
ST_slot_10 FULL HBQ210
ST_slot_11 FULL HBQ211
ST_slot_12 FULL HBQ212
求解?

uu563112676

建议查看下
1， /var/adm/syslog/syslog.log 是否 有报错，

2，ioscan -fnC autoch
用OS 来测试下机械手 ，（从driver端到SLOT端）

3，在DP端，对该分区的driver做下SCAN 操作

感觉 是配置问题多一些。

unmark

回复 2# uu563112676


    主机端扫到两个机械手，
ioscan -fnCautoch
Class     I  H/W Path      Driver S/W State   H/W Type     Description
=======================================================================
autoch    1  0/12/0/0.1.7.255.0.0.0  schgr  CLAIMED     DEVICE       HP      MSL6000 Series
                          /dev/rac/c11t0d0
autoch    2  1/4/0/0.2.7.255.0.0.0   schgr  CLAIMED     DEVICE       HP      MSL6000 Series
                          /dev/rac/c20t0d0，
DP端也扫描过，而且都能扫到，但是有个问题，DP端的看到的robot path和上面看到的path不一样，晕了。虚拟的MSL6000总共4个driver，有一个分配给该机，但是怎么主机端会看到8个driver？（本身那一个不算）

uu563112676

看懂8个driver 是多路径问题 应该

你OS 应该不是11.31的吧
试试DP将该带库 删了 重新认下 也行

看看 /var/adm/syslog/syslog.log

unmark

回复 4# uu563112676
系统是11.11，系统日志无报错，而且在系统上测试了driver，可以tar文件到磁带。现在只剩下DP端未排除了，关于删除带库重新认，删除带库重新配置会不会冲掉以前的配置文件，因为上面还有其他的主机的备份。谢谢！   

uu563112676

首先

1）在DP中client端 upgrade该client端

2）在DP drivers选项选定该分区，删除 驱动器，之后再重新添加驱动器。

若还出现 同类现象，如果是我做，我会将ioscan -fnC tape与 ioscan -fnC autoch 所有生成的路径全部删除，insf -eC tape 重新生成一遍路径。在DP中 重新认该分区 驱动器

至于你说的配置是否会冲掉，你所做操作只是基于更改驱动器，跟配置无关，发现驱动器后，可在backup端 对该备份作业重新添加驱动器。

unmark

回复 6# uu563112676
1、关于升级client具体怎么操作？/opt/omni/bin or lbin的某条指令？
谢谢！

   

uu563112676

回复 7# unmark

在DP GUI中 点 client 选项

然后点clients 会发现 该主机，点击右键 upgrade
   

unmark

回复 8# uu563112676


    thanks