当处理FROZEN的带,需先理解:
.FROZEN状态存储在MediaServer的MediaDB,每MasterSErver及MediaServer有自己的MediaDB
.MEdiaDB信息,包含(FROZE,FULL,Active),可以通过bpmedialist命令获得
.只能通过bpmedia命令进行unfrozen.
.被FROZEN的带不代表有缺陷。在FREEZing的带子是NBU的安全措施,可以防止更远的错误,设备破坏或者可能的数据损失.
.了解相关带,驱动器或者media server
这些日志在处理FROZEN带很有用:
.MediaServer上的bptm 日志: /usr/openv/netbackup/logs/bptm
.操作系统syslog
这些代码可能引起或因为FROZEN带:
84 - Media Write Error
If the tape unit can not read or write to the tape correctly, this status code can occur when media are frozen
86 - Media Position Error
If the tape unit can not read or write to the tape correctly, this status code can occur when media are frozen
96 - Unable to allocate new media
If media continue to become frozen, the backup job may end in a Status 96, because no more media available to mount.
造成FROZEN的可能原因:
1.同一media在备份中过多报错(脏驱动器,scsi通讯,硬件兼容,磁带兼容...)
2.在驱动器出现不期望的磁带(放入错误磁带,未配置的驱动..)
3.磁带含非NBU格式
(可以在/usr/openv/netbackup/bp.conf 加定义
ALLOW_MEDIA_OVERWRITE = DBR
ALLOW_MEDIA_OVERWRITE = TAR
ALLOW_MEDIA_OVERWRITE = CPIO
ALLOW_MEDIA_OVERWRITE = ANSI
ALLOW_MEDIA_OVERWRITE = MTF1
ALLOW_MEDIA_OVERWRITE = BE-MTF1
4.带子之前为NBU的Catalog备份用带
此情况下,需用bplabel命令重设带头
5.人为FROZEN
例如管理原因用bpmedia命令freeze带
6.带被写保护
将阻止写入,Netbackup将其frozen
如何Unfreezing FROZEN带?
.用bpmedia命令:
For UNIX
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m <mediaID> -h <name of media server that froze media>
For Windows
<Install_path>\VERITAS\Netbackup\bin\admincmd\bpmedia -unfreeze -m <mediaID> -h <name of media server that froze media>
.可以用bpmedialist命令看到被哪个server FROZEN:
For UNIX
/usr/openv/netbackup/bin/admincmd/bpmedialist -m <mediaID>
For Windows
<Install_path>\VERITAS\Netbackup\bin\admincmd\bpmedialist -m <mediaID>
1