client backup was not attempted because backup window closed 錯誤解決一例
今天有個備份策略出問題,報錯內容是這樣的:
04/24/2008 00:03:00 - requesting resource bfepdb-hcart2
04/24/2008 00:03:00 - requesting resource bfbkup.NBU_CLIENT.MAXJOBS.bfepdb
04/24/2008 00:03:00 - requesting resource bfbkup.NBU_POLICY.MAXJOBS.bfep_db
04/24/2008 00:03:00 - awaiting resource bfepdb-hcart2. Waiting for resources.
Reason: Tape media server is not active, Media server: erpdb,
Robot Type(Number): TLD(0), Media ID: N/A, Drive Name: N/A,
Volume Pool: DB_ep_full, Storage Unit: bfepdb-hcart2, Drive Scan Host: N/A
client backup was not attempted because backup window closed (196)
在master server開啟控制檯,deivce--host,發現的status是“active for disk”。由於這個media server上面連線的是磁帶庫。正常應該是“active for type and disk”於是在這臺機器上執行tpconfig –d,一直沒有反饋資訊。
1.透過bpps檢視程式:
NB Processes
------------
root 11379 1 0 15:24:23 ? 0:00 /usr/openv/netbackup/bin/bpcompatd
root 11384 1 0 15:24:28 ? 0:00 /usr/openv/netbackup/bin/nbsl
root 11356 1 0 15:24:17 ? 0:00 /usr/openv/netbackup/bin/nbnos
root 11391 1 0 15:24:29 ? 0:00 /usr/openv/netbackup/bin/nbsvcmon
MM Processes
------------
root 11494 11364 0 15:30:37 ? 0:00 tldd
root 11364 1 0 15:24:20 ? 0:00 /usr/openv/volmgr/bin/ltid
root 11497 11364 0 15:30:39 ? 0:00 avrd
root 11480 1 0 15:30:34 ? 0:00 vmd
沒有發現異常情況。
2.在master server上執行:
vmdareq -a
發現沒有bfepdb這個media server的資訊,決定重啟nbu程式。netbackup stop後bpps -a
NB Processes
------------
MM Processes
------------
3.ioscan -fnC tape
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
tape 0 0/0/1/0.4.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/0m /dev/rmt/0mnb /dev/rmt/c0t4d0BESTn /dev/rmt/c0t4d0DDSb
/dev/rmt/0mb /dev/rmt/c0t4d0BEST /dev/rmt/c0t4d0BESTnb /dev/rmt/c0t4d0DDSn
/dev/rmt/0mn /dev/rmt/c0t4d0BESTb /dev/rmt/c0t4d0DDS /dev/rmt/c0t4d0DDSnb
tape 7 0/10/0/0.97.26.255.1.3.0 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/7m /dev/rmt/7mn /dev/rmt/c16t3d0BEST /dev/rmt/c16t3d0BESTn
/dev/rmt/7mb /dev/rmt/7mnb /dev/rmt/c16t3d0BESTb /dev/rmt/c16t3d0BESTnb
tape 8 0/10/0/0.97.26.255.1.3.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/8m /dev/rmt/8mn /dev/rmt/c16t3d1BEST /dev/rmt/c16t3d1BESTn
/dev/rmt/8mb /dev/rmt/8mnb /dev/rmt/c16t3d1BESTb /dev/rmt/c16t3d1BESTnb
tape 3 0/12/0/0.97.25.255.1.3.1 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/3m /dev/rmt/3mn /dev/rmt/c14t3d1BEST /dev/rmt/c14t3d1BESTn
/dev/rmt/3mb /dev/rmt/3mnb /dev/rmt/c14t3d1BESTb /dev/rmt/c14t3d1BESTnb
tape 4 0/12/0/0.97.25.255.1.3.2 stape CLAIMED DEVICE HP Ultrium 2-SCSI
/dev/rmt/4m /dev/rmt/4mn /dev/rmt/c14t3d2BEST /dev/rmt/c14t3d2BESTn
/dev/rmt/4mb /dev/rmt/4mnb /dev/rmt/c14t3d2BESTb /dev/rmt/c14t3d2BESTnb
裝置也沒有什麼異常情況。
4.接著netbackup start,再手工啟動策略問題依然存在。
5.再次netbackup stop後執行bp.kill_all,徹底殺掉nbu程式,再netbackup start啟動nbu,vmdareq -a一切正常。
# netbackup start
NetBackup Database Server started.
NetBackup Notification Service started.
NetBackup Enterprise Media Manager started.
NetBackup Resource Broker started.
Media Manager daemons started.
NetBackup request daemon started.
NetBackup compatibility daemon started.
NetBackup Job Manager started.
NetBackup Policy Execution Manager started.
NetBackup Service Layer started.
NetBackup is not configured for clustering.
NetBackup Service Monitor started.
# vmdareq -a
Drive2 - AVAILABLE
bfbkup UP
erpdb UP
Drive3 - AVAILABLE
bfbkup UP
erpdb UP
HPUltrium2-SCSI0 - AVAILABLE
bfbkup UP
erpdb UP
HPUltrium2-SCSI1 - AVAILABLE
bfbkup UP
erpdb UP
6.結論
出現這種問題,可能是由nbu程式的異常造成的。但是正常的重啟可能仍然不能解決問題,這時候需要執行bp.kill_all指令碼來停止nbu的後臺駐留程式。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29500582/viewspace-1867276/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- SQL SERVER恢復資料錯誤解決:The backup set holds a backup of a database other than the existingSQLServerDatabase
- centos 重啟掛載錯誤 failed to mount /backupCentOSAI
- oracle rman backup命令檢查資料庫錯誤Oracle資料庫
- ORA-03113錯誤解決一例
- RMAN-06133 錯誤解決一例
- rman backup database 出現 ORA-01422錯誤Database
- 解決client端的ORA-01882錯誤client
- full backup 與 level 0 incremental backupREM
- MySQL 5.6 GTID常見錯誤解決一例MySql
- ORA-02063錯誤解決一例
- ORA-12514: 錯誤解決一例
- PostgreSQL DBA(29) - Backup&Recovery#2(日期格式導致的錯誤)SQL
- svn This client is too old to work with working copy錯誤解決方案client
- Linux共享連結庫錯誤解決一例(轉)Linux
- Veritas Backup
- Job for mysqld.service failed because the control process exited with error code錯誤解決MySqlAIError
- ORA-02019錯誤解決一例
- 應對 "RMAN-06023: no backup or copy of datafile 1 found to restore"錯誤REST
- SQLBackupAndFTP12.0 failed to backup database with full backup typeSQLFTPAIDatabase
- nbu client錯誤解析client
- backup site collection
- Oracle Secure BackupOracle
- Cold backup script
- GCS shadows traversed, 4001 replayed 錯誤解決一例GC
- 通過sql跟蹤解決ORA-00942錯誤一例SQL
- backup archivelog like 報rman-20242錯誤處理過程Hive
- 影片講解:PX-Backup安裝
- python程式碼錯誤RuntimeError: Session is closedPythonErrorSession
- 誤刪libc提示Kernel panic not syncing: Attempted to kill init解決辦法
- 理解備份集backup set與備份片backup piece
- 解決了一例Shutdown時碰到Ora-600錯誤的問題
- oracle full database backupOracleDatabase
- SQL Server Backup & RestoreSQLServerREST
- TFS Express backup and restoreExpressREST
- backup and restore tipsREST
- oracle cold backup scriptsOracle
- rman backup script(引用)
- Rman backup standby databaseDatabase