hp dp软件中 ibm磁带库用过三年,质量标为差怎么办?

· 作者 ||【转载时请务必以超链接形式标明文章原始出处和作者信息】
· 永久链接:
问题提出:
日开始arch备份在inter database中提示一半对一半错:
status:Completed/Failures
Type:Backup
Specification:Oracle8 gd_rac_arch
Backup Type:full
Start Time: 22:00:05
End Time: 22:05:37
Owner:oracle.dba@gd_rac02
日还是如此,打电话给HP,要求将report发给其工程师
在cmd下,输入:omnidb -sess -6 -report>gd_misc_db_arch.txt
[Normal] From: BSM@gd-bak02 “gd_rac_arch” Time:
OB2BAR application on “gd_rac02″ successfully started.
ob2rman.exe started with arguments:
-backup -full
Recovery Manager: Release 9.2.0.6.0 – 64bit Production
Copyright (c) , Oracle Corporation. All rights reserved.
connected to target database: GDMISC (DBID=)
connected to recovery catalog database
RMAN> run {
2> allocate channel ‘dev_0′ type ‘sbt_tape’
3> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
4> allocate channel ‘dev_1′ type ‘sbt_tape’
5> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
6> allocate channel ‘dev_2′ type ‘sbt_tape’
7> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
8> allocate channel ‘dev_3′ type ‘sbt_tape’
9> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
10> allocate channel ‘dev_4′ type ‘sbt_tape’
11> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
12> allocate channel ‘dev_5′ type ‘sbt_tape’
13> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
14> allocate channel ‘dev_6′ type ‘sbt_tape’
15> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
16> allocate channel ‘dev_7′ type ‘sbt_tape’
17> parms ‘ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=gdrac2,OB2BARLIST=gd_rac_arch,OB2BARHOSTNAME=gd_rac02)’;
18> backup incremental level 0
19> filesperset 4
20> format ‘gd_rac_arch.dbf’
21> archivelog all
allocated channel: dev_0
channel dev_0: sid=178 devtype=SBT_TAPE
channel dev_0: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_1
channel dev_1: sid=839 devtype=SBT_TAPE
channel dev_1: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_2
channel dev_2: sid=679 devtype=SBT_TAPE
channel dev_2: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_3
channel dev_3: sid=250 devtype=SBT_TAPE
channel dev_3: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_4
channel dev_4: sid=467 devtype=SBT_TAPE
channel dev_4: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_5
channel dev_5: sid=369 devtype=SBT_TAPE
channel dev_5: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_6
channel dev_6: sid=279 devtype=SBT_TAPE
channel dev_6: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
allocated channel: dev_7
channel dev_7: sid=751 devtype=SBT_TAPE
channel dev_7: Data Protector A.05.50/PHSS_35224/PHSS_35225/DPSOL_00241
Starting backup at 12/26/:20]
current log archived
channel dev_0: starting archive log backupset
channel dev_0: specifying archive log(s) in backup set
input archive log thread=1 sequence=1554 recid=2171 stamp=
input archive log thread=1 sequence=1555 recid=2178 stamp=
input archive log thread=1 sequence=1556 recid=2184 stamp=
channel dev_0: starting piece 1 at 12/26/:42]
channel dev_1: starting archive log backupset
channel dev_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1557 recid=2189 stamp=
input archive log thread=1 sequence=1558 recid=2193 stamp=
input archive log thread=2 sequence=740 recid=2170 stamp=
channel dev_1: starting piece 1 at 12/26/:42]
channel dev_2: starting archive log backupset
channel dev_2: specifying archive log(s) in backup set
input archive log thread=2 sequence=741 recid=2173 stamp=
input archive log thread=2 sequence=742 recid=2174 stamp=
input archive log thread=2 sequence=743 recid=2175 stamp=
channel dev_2: starting piece 1 at 12/26/:42]
channel dev_3: starting archive log backupset
channel dev_3: specifying archive log(s) in backup set
input archive log thread=2 sequence=744 recid=2177 stamp=
input archive log thread=2 sequence=745 recid=2179 stamp=
input archive log thread=2 sequence=746 recid=2182 stamp=
channel dev_3: starting piece 1 at 12/26/:42]
channel dev_4: starting archive log backupset
channel dev_4: specifying archive log(s) in backup set
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_3_gd_rac02″ Time:
STARTING Media Agent “HP:Ultrium 3-SCSI_3_gd_rac02″
input archive log thread=2 sequence=747 recid=2188 stamp=
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_1_gd_rac02″ Time:
STARTING Media Agent “HP:Ultrium 3-SCSI_1_gd_rac02″
input archive log thread=2 sequence=748 recid=2192 stamp=
input archive log thread=3 sequence=661 recid=2172 stamp=
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_3_gd_rac02″ Time:
By: UMA@gd_rac02@/dev/rac/c8t0d0
Loading medium from slot 54 to device /dev/rmt/3mn
channel dev_4: starting piece 1 at 12/26/:42]
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_1_gd_rac02″ Time:
By: UMA@gd_rac02@/dev/rac/c8t0d0
Loading medium from slot 57 to device /dev/rmt/1mn
channel dev_5: starting archive log backupset
channel dev_5: specifying archive log(s) in backup set
input archive log thread=3 sequence=662 recid=2176 stamp=
input archive log thread=3 sequence=663 recid=2180 stamp=
input archive log thread=3 sequence=664 recid=2181 stamp=
channel dev_5: starting piece 1 at 12/26/:42]
channel dev_6: starting archive log backupset
channel dev_6: specifying archive log(s) in backup set
input archive log thread=3 sequence=665 recid=2183 stamp=
input archive log thread=3 sequence=666 recid=2185 stamp=
input archive log thread=3 sequence=667 recid=2186 stamp=
channel dev_6: starting piece 1 at 12/26/:42]
channel dev_7: starting archive log backupset
channel dev_7: specifying archive log(s) in backup set
input archive log thread=3 sequence=668 recid=2187 stamp=
input archive log thread=3 sequence=669 recid=2190 stamp=
input archive log thread=3 sequence=670 recid=2191 stamp=
channel dev_7: starting piece 1 at 12/26/:43]
[Critical] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_1_gd_rac02″ Time:
[90:63] By: UMA@gd_rac02@/dev/rac/c8t0d0
Cannot load exchanger medium (Target drive is busy.)
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_1_gd_rac02″ Time:
ABORTED Media Agent “HP:Ultrium 3-SCSI_1_gd_rac02″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
channel dev_4: finished piece 1 at 12/26/:38]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_4: backup set complete, elapsed time: 00:03:57
channel dev_4: deleting archive log(s)
archive log filename=/arch/gdrac_2_747.arc recid=2188 stamp=
archive log filename=/arch/gdrac_2_748.arc recid=2192 stamp=
archive log filename=/arch/gdrac_3_661.arc recid=2172 stamp=
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
channel dev_7: finished piece 1 at 12/26/:53]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_7: backup set complete, elapsed time: 00:04:12
channel dev_7: deleting archive log(s)
archive log filename=/arch/gdrac_3_668.arc recid=2187 stamp=
archive log filename=/arch/gdrac_3_669.arc recid=2190 stamp=
archive log filename=/arch/gdrac_3_670.arc recid=2191 stamp=
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
channel dev_5: finished piece 1 at 12/26/:01]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_5: backup set complete, elapsed time: 00:04:20
channel dev_5: deleting archive log(s)
archive log filename=/arch/gdrac_3_662.arc recid=2176 stamp=
archive log filename=/arch/gdrac_3_663.arc recid=2180 stamp=
archive log filename=/arch/gdrac_3_664.arc recid=2181 stamp=
channel dev_6: finished piece 1 at 12/26/:01]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_6: backup set complete, elapsed time: 00:04:20
channel dev_6: deleting archive log(s)
archive log filename=/arch/gdrac_3_665.arc recid=2183 stamp=
archive log filename=/arch/gdrac_3_666.arc recid=2185 stamp=
archive log filename=/arch/gdrac_3_667.arc recid=2186 stamp=
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
channel dev_3: finished piece 1 at 12/26/:46]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_3: backup set complete, elapsed time: 00:05:05
channel dev_3: deleting archive log(s)
archive log filename=/arch/gdrac_2_744.arc recid=2177 stamp=
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
archive log filename=/arch/gdrac_2_745.arc recid=2179 stamp=
archive log filename=/arch/gdrac_2_746.arc recid=2182 stamp=
channel dev_0: finished piece 1 at 12/26/:48]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_0: backup set complete, elapsed time: 00:05:07
channel dev_0: deleting archive log(s)
archive log filename=/arch/gdrac_1_1554.arc recid=2171 stamp=
archive log filename=/arch/gdrac_1_1555.arc recid=2178 stamp=
archive log filename=/arch/gdrac_1_1556.arc recid=2184 stamp=
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gd_rac_arch.dbf “Oracle8″
channel dev_1: finished piece 1 at 12/26/:03]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_1: backup set complete, elapsed time: 00:05:22
channel dev_1: deleting archive log(s)
archive log filename=/arch/gdrac_1_1557.arc recid=2189 stamp=
archive log filename=/arch/gdrac_1_1558.arc recid=2193 stamp=
archive log filename=/arch/gdrac_2_740.arc recid=2170 stamp=
channel dev_2: finished piece 1 at 12/26/:04]
piece handle=gd_rac_arch.dbf comment=API Version 2.0,MMS Version 65.5.50.0
channel dev_2: backup set complete, elapsed time: 00:05:23
channel dev_2: deleting archive log(s)
archive log filename=/arch/gdrac_2_741.arc recid=2173 stamp=
archive log filename=/arch/gdrac_2_742.arc recid=2174 stamp=
archive log filename=/arch/gdrac_2_743.arc recid=2175 stamp=
Finished backup at 12/26/:04]
released channel: dev_0
released channel: dev_1
released channel: dev_2
released channel: dev_3
released channel: dev_4
released channel: dev_5
released channel: dev_6
released channel: dev_7
RMAN> **end-of-file**
Recovery Manager complete.
[Normal] From: ob2rman.exe@gd_rac02 “gdrac2″ Time: 12/26/06 14:06:06
Oracle RMAN successfully finished.
[Normal] From: ob2rman.exe@gd_rac02 “gdrac2″ Time: 12/26/06 14:06:06
Issuing DP Managed Control File Backup …
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:gdrac2 DP Managed Control File Backup “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:gdrac2 DP Managed Control File Backup “Oracle8″
[Normal] From: ob2rman.exe@gd_rac02 “gdrac2″ Time: 12/26/06 14:06:23
Starting backup of the Oracle Recovery Catalog Database …
[Normal] From: ob2rman.exe@gd_rac02 “gdrac2″ Time: 12/26/06 14:06:23
Getting NLS_LANG and setting it into the environment ….
AMERICAN_AMERICA.ZHS16GBK
Default exp binary /oracle/app/oracle/product/9.2.0/bin/exp is used for catalog export.
[Normal] From: ob2rman.exe@gd_rac02 “gdrac2″ Time: 12/26/06 14:06:35
Export of the Recovery Catalog succeeded. Proceeding to backup.
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Starting OB2BAR Backup: gd_rac02:Oracle Recovery Backup Catalog “Oracle8″
[Normal] From: OB2BAR_Oracle8@gd_rac02 “gdrac2″ Time:
Completed OB2BAR Backup: gd_rac02:Oracle Recovery Backup Catalog “Oracle8″
[Normal] From: ob2rman.exe@gd_rac02 “gdrac2″ Time: 12/26/06 14:06:38
Backup of the Oracle Catalog Database succeeded.
[Normal] From: BSM@gd-bak02 “gd_rac_arch” Time:
OB2BAR application on “gd_rac02″ disconnected.
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_3_gd_rac02″ Time:
/dev/rmt/3mn
Medium header verification completed, 0 errors found
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_3_gd_rac02″ Time:
By: UMA@gd_rac02@/dev/rac/c8t0d0
Unloading medium to slot 54 from device /dev/rmt/3mn
[Normal] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_3_gd_rac02″ Time:
COMPLETED Media Agent “HP:Ultrium 3-SCSI_3_gd_rac02″
[Normal] From: BSM@gd-bak02 “gd_rac_arch” Time:
Backup Statistics:
Session Queuing Time (hours) 0.00
—————————————-
Completed Disk Agents …….. 10
Failed Disk Agents ……….. 0
Aborted Disk Agents ………. 0
—————————————-
Disk Agents Total ……….. 10
========================================
Completed Media Agents ……. 1
Failed Media Agents ………. 1
Aborted Media Agents ……… 0
—————————————-
Media Agents Total ………. 2
========================================
Mbytes Total …………….. 10813 MB
Used Media Total …………. 1
Disk Agent Errors Total …… 0
问题分析:
根据report中的:
[Critical] From: BMA@gd_rac02 “HP:Ultrium 3-SCSI_1_gd_rac02″ Time:
[90:63] By: UMA@gd_rac02@/dev/rac/c8t0d0
Cannot load exchanger medium (Target drive is busy.)
因此找到原因:用于备份arch的2个driver,其中一个被磁带卡住,而另一个能正常工作,于是就显示了一半成功一半失败的备份结果。
在上述情况下,arch还是能完整的正常备份(只用一个driver),但是备份有报错信息。
问题解决:
到gd-rac02上执行以下语句,检查是否真的卡带:
gd_rac02#[/]mc -p /dev/rac/c8t0d0 -r DS
DT_slot_1 FULL CS1257
DT_slot_2 EMPTY
DT_slot_3 EMPTY
DT_slot_4 EMPTY
ST_slot_1 EMPTY
ST_slot_2 FULL JT8140
ST_slot_3 FULL JT8141
ST_slot_4 FULL JT8129
ST_slot_5 FULL JT8143
ST_slot_6 FULL JT8144
ST_slot_7 FULL JT8155
ST_slot_8 FULL JT8146
ST_slot_9 EMPTY
ST_slot_10 FULL JT8148
ST_slot_11 FULL JT8149
ST_slot_12 FULL JT8170
ST_slot_13 FULL JT8171
ST_slot_14 FULL JT8172
ST_slot_15 FULL JT8154
ST_slot_16 EMPTY
ST_slot_17 EMPTY
ST_slot_18 EMPTY
ST_slot_19 EMPTY
ST_slot_20 EMPTY
ST_slot_21 EMPTY
ST_slot_22 EMPTY
ST_slot_23 FULL JT8132
ST_slot_24 FULL JT8133
ST_slot_25 FULL JT8134
ST_slot_26 EMPTY
ST_slot_27 FULL JT8136
ST_slot_28 EMPTY
ST_slot_29 EMPTY
ST_slot_30 FULL JT8120
ST_slot_31 FULL JT8121
ST_slot_32 FULL JT8122
ST_slot_33 FULL JT8123
ST_slot_34 FULL JT8124
ST_slot_35 FULL JT8125
ST_slot_36 FULL JT8126
ST_slot_37 FULL JT8127
ST_slot_38 FULL JT8128
ST_slot_39 EMPTY
ST_slot_40 FULL JT8150
ST_slot_41 FULL JT8145
ST_slot_42 EMPTY
ST_slot_43 FULL JT8153
ST_slot_44 FULL JT8173
ST_slot_45 FULL JT8174
ST_slot_46 FULL JT8175
ST_slot_47 FULL JT8176
ST_slot_48 FULL JT8177
ST_slot_49 FULL JT8178
ST_slot_50 FULL JT8179
ST_slot_51 FULL JT8160
ST_slot_52 FULL JT8151
ST_slot_53 FULL JT8152
ST_slot_54 FULL JT8163
ST_slot_55 FULL JT8164
ST_slot_56 FULL JT8165
ST_slot_57 FULL JT8166
ST_slot_58 FULL CLN000
gd_rac02#[/]
gd_rac02#[/]mc -p /dev/rac/c8t0d0 -s D1 -dS9
gd_rac02#[/]mc -p /dev/rac/c8t0d0 -r DS
DT_slot_1 EMPTY
DT_slot_2 EMPTY
DT_slot_3 EMPTY
DT_slot_4 EMPTY
ST_slot_1 EMPTY
ST_slot_2 FULL JT8140
ST_slot_3 FULL JT8141
ST_slot_4 FULL JT8129
ST_slot_5 FULL JT8143
ST_slot_6 FULL JT8144
ST_slot_7 FULL JT8155
ST_slot_8 FULL JT8146
ST_slot_9 FULL CS1257
ST_slot_10 FULL JT8148
ST_slot_11 FULL JT8149
ST_slot_12 FULL JT8170
ST_slot_13 FULL JT8171
ST_slot_14 FULL JT8172
ST_slot_15 FULL JT8154
ST_slot_16 EMPTY
ST_slot_17 EMPTY
ST_slot_18 EMPTY
ST_slot_19 EMPTY
ST_slot_20 EMPTY
ST_slot_21 EMPTY
ST_slot_22 EMPTY
ST_slot_23 FULL JT8132
ST_slot_24 FULL JT8133
ST_slot_25 FULL JT8134
ST_slot_26 EMPTY
ST_slot_27 FULL JT8136
ST_slot_28 EMPTY
ST_slot_29 EMPTY
ST_slot_30 FULL JT8120
ST_slot_31 FULL JT8121
ST_slot_32 FULL JT8122
ST_slot_33 FULL JT8123
ST_slot_34 FULL JT8124
ST_slot_35 FULL JT8125
ST_slot_36 FULL JT8126
ST_slot_37 FULL JT8127
ST_slot_38 FULL JT8128
ST_slot_39 EMPTY
ST_slot_40 FULL JT8150
ST_slot_41 FULL JT8145
ST_slot_42 EMPTY
ST_slot_43 FULL JT8153
ST_slot_44 FULL JT8173
ST_slot_45 FULL JT8174
ST_slot_46 FULL JT8175
ST_slot_47 FULL JT8176
ST_slot_48 FULL JT8177
ST_slot_49 FULL JT8178
ST_slot_50 FULL JT8179
ST_slot_51 FULL JT8160
ST_slot_52 FULL JT8151
ST_slot_53 FULL JT8152
ST_slot_54 FULL JT8163
ST_slot_55 FULL JT8164
ST_slot_56 FULL JT8165
ST_slot_57 FULL JT8166
ST_slot_58 FULL CLN000
gd_rac02#[/]
调整作业计划,在16点30分测试了一次arch备份,备份正常。
HP的文档中关于mc命令的解释:
mc(1M) mc(1M)
mc – 介质装载器操作实用程序
mc [-p device] [-a num] [-q] [-c ]
mc [-p device] [-b 0|1] [-l 0|1] [-e element_type]
mc [-p device] [-n drive_number] [-r element_type]
mc [-p device] -s
mc [-h |-?]
mc 实用程序为用户提供了一个命令行接口,用于将介质操作命令发送到自动装载机或介质更换设备。它采用
“元素类型”作为大多数选项的参数。有效的介质类型(element_types) 包括:
D 指定数据传输(DT) 元素。
I 指定导入/导出(IE) 元素。
M 指定介质传输(MT) 元素。
S 指定存储(ST) 元素。
数据传输元素的示例是自动装载机的嵌入式磁带机。导入/导出元素的示例是可用于插入介质或者从自动装载机中
取出介质的插槽。介质传输元素的示例是自动装载机的机械拾取器组件。存储元素的示例是自动装载机的介质插
有关用法,请参阅下面的示例。
mc 采用下列选项和参数:
-a num 输出num 指定的驱动器插槽的SCSI 总线地址。
-b 0|1 向设备发出保留(1) 或释放(0) SCSI 命令。
确定从源到目标的移动是否有效。使用设备功能模式页,并将返回TRUE 或FALSE。源和目标
元素类型值中不应该使用空格。例如, -c DS 指定数据传输元素作为源,指定存储元素作为目
-e element_type 输出元素类型的元素数。请参阅上面的元素类型。可以指定多个类型。例如, -e IDSM 指定所
有有效的元素类型。
-h|-? 输出用法说明。
HP-UX 11i Version 2: September 2004 -1- Hewlett-Packard Company Section 1M-527
mc(1M) mc(1M)
-l 0|1 允许(0) 或防止(1) 取出介质。
-n num 输出num 指定的插槽中的驱动器序列号(如果该信息可用)。
-p device 指定到库设备的通道设备文件。如果已设置LIBRARY 环境变量,则可以省略-p 选项。
-q 输出供应商ID、产品ID 和产品修订标准查询信息。
-r element_type 输出元素类型的元素插槽的状态(FULL/EMPTY/NONE)。请参阅上面的元素类型。如果设备支
持条码信息,该信息将追加到状态。可以指定多个类型。例如, -r IDSM 指定所有有效的元素
指定移动介质源的元素类型和插槽号() 。元素类型和插槽号之间不应使用空格。例如,
-sS1 指定插槽号1 中的存储元素。每次调用时,指定该选项的次数不能超过两次。
指定移动介质目标的元素类型和插槽号。元素类型和插槽号之间不应使用空格。例如, -dD3 指
定插槽号3 中的数据传输元素。每次调用时,指定该选项的次数不能超过两次。
mc 在成功完成时返回0,在其他情况下返回-1。
ERROR: 0×5 Illegal Request: 0x3b0d Medium Destination element full
以上错误消息可能是用于将介质移动到已满的嵌入式驱动器的命令mc -s S2 -d D1 的结果。
ERROR: /dev/scsi/3: No such file or directory
如果不存在缺省的SCSI 通道设备文件,并且未指定其他任何设备文件,则将输出上面的错误消息。
以包含六个盒式磁带的磁带盒的DDS-2 自动装载机为例:
查看自动装载机的数据传输和存储元素类型的状态:
下面显示以上命令的输出示例。输出指示插槽2 (ST_slot_2) 中存在一个介质,嵌入式驱动器(DT_slot_1) 中存在
一个介质,其他所有插槽均为空。
DT_slot_1 FULL
ST_slot_1 EMPTY
ST_slot_2 FULL
ST_slot_3 EMPTY
Section 1M-528 Hewlett-Packard Company - 2 - HP-UX 11i Version 2: September 2004
mc(1M) mc(1M)
ST_slot_4 EMPTY
ST_slot_5 EMPTY
ST_slot_6 EMPTY
将介质从嵌入式驱动器移动到插槽5,然后将介质从插槽2 移动到嵌入式驱动器:
mc -s D1 -d S5 -s S2 -d D1
检查是否可以从数据传输元素移动到存储元素:
下面显示以上命令的输出示例。该输出指示从数据传输元素类型到存储元素类型的移动是有效的。
DT->ST: TRUE
请注意,对于所有HP DDS 自动装载机:首次使用mc 命令后,自动装载机将进入随机模式。一旦处于随机模
式,将禁用除Eject Button 之外的所有前面板按钮功能。要回到堆栈模式,必须弹出并重新插入磁带盒。
请注意,对于某些自动装载机或库:使用mc 命令之前,必须使用mt offline 命令卸载介质。
mc 命令支持所有符合SCSI-2 介质更换器命令规范的HP 支持设备。
在使用该命令操作自动装载机之前,必须配置SCSI 通道驱动程序并创建设备文件。
对于连接到SCSI 接口卡(PCI) 的设备,必须配置sctl 通道驱动程序。请参阅scsi_ctl(7) 。
mc 由HP 开发。
/dev/scsi/3 缺省的通道设备文件。
· 【文章发布信息】发表于:
@ 23:35:55
· ||分类: ,
· 【分享或收藏】:
<a href="/home?status=HP DP备份arch日志报错一半成功一半失败 <}

我要回帖

更多关于 ibm磁带库 的文章

更多推荐

版权声明:文章内容来源于网络,版权归原作者所有,如有侵权请点击这里与我们联系,我们将及时删除。

点击添加站长微信