灌溉梦想,记录脚步

Install NetBackup Client on Kylin OS V10

1、Install Process with Error:

Checking connectivity to the master server.

NOTE: Depending on the network, this action may take a few minutes.

      To continue without setting up secure communication, press Ctrl+C.

EXIT STATUS 103: error occurred during initialization, check configuration file

ERROR:   Cannot set up secure communication.

         The attempt to contact the master server failed.

继续阅读 »

WordPress代码高亮插件兼容问题

WordPress升级到6.4,PHP升级到8.2版本后,WP-SYNTAX插件提示如下错误,并导致页面无法访问。

错误信息:

( ! ) Warning: WP_Syntax::substituteToken(): Argument #1 ($match) must be passed by reference, value given in \wp-content\plugins\wp-syntax\wp-syntax.php on line 380

解决方案:

1、将wp-syntax.php第241行删除“&”符号,删除后代码如下:

public static function substituteToken( $match ) {

2、更新geshi包

从下面地址下载包,并替换:/geshi-1.0-master/src/ -> /wp-content/plugins/wp-syntax/geshi/

https://github.com/GeSHi/geshi-1.0

NBU AdvancedDisk Pool扩容

环境:

OS:RedHat 6.5 x64
NB:NetBackup 7.6

需求:

Media Server创建有一个AdvancedDisk Pool,名称为:media_advdisk_dpool,
包含/advdsk1 /advdsk2两个挂载点,现在需要将/advdsk3加入到挂载点中。

步骤:

1、首先通过“Configure Disk Pool”向导,创建一个新的AdvancedDisk Pool,

名称为:media_temp_dpool,只包含/advdsk3一个挂载点,选项默认。

2、将两个AdvancedDisk Pool状态更改为DOWN。

可通过“Device Monitro”图形界面操作,也可以使用命令:
继续阅读 »

Bad id for repo on RedHat

OS版本:redhat 6.7 x64
在配置完成本地YUM后,检查YUM配置报错如下:

[root@redhat yum.repos.d]# yum clean all
Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
This system is not registered to Red Hat Subscription Management. 
You can use subscription-manager to register.
Bad id for repo: rhel-ResilientStorage , byte =   21
Bad id for repo: rhel-ScalableFileSystem , byte =   23
Cleaning repos: rhel-HighAvailability rhel-LoadBalancer rhel-Server

可看到有两个repo提示id错误,通过检查配置发现:

[rhel-ResilientStorage ]
name=Red Hat Enterprise Linux $releasever - $basearch - ResilientStorage 
baseurl=http://xxxx.forzw.com/os/redhat_6.7_x64/ResilientStorage 
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release

[rhel-ResilientStorage ]中有空格造成,去掉即可解决。

requested media id is in use

备份、恢复、或者执行bpexpdate,提示“requested media id is in use”,随机进入排队或者错误状态。

通过检查发现Drive并未被使用,可以通过命令确认:

vmoprcmd
nbrbutil -dump

如果出现如下信息,可以确认Drive被Media Server占用。

MDS allocations in EMM:
 
        MdsAllocation: allocationKey=11139 jobType=2 mediaKey=1110097 mediaId=0513L3 driveKey=0 \ 
driveName= drivePath= stuName= masterServerName=netbackup01 mediaServerName=netbackup01 \ 
ndmpTapeServerName= diskVolumeKey=0 mountKey=0 linkKey=0
 fatPipeKey=0 scsiResType=0 serverStateFlags=0
        MdsAllocation: allocationKey=11125 jobType=1 mediaKey=1110090 mediaId=00075L \
 driveKey=2000005 driveName=IBM.ULTRIUM-HH4.001 drivePath={3,0,1,0} stuName=netbackup01-hcart-robot-tld-0 \
 masterServerName=netbackup01 mediaServerName=netbackup01 ndmpTapeServerName= diskVolumeKey=0 mountKey=0 \ 
linkKey=0 fatPipeKey=0 scsiResType=1 serverStateFlags=1

继续阅读 »

NetBackup SAN Client别名问题

在配置完成后,我们在Client中也可以看的相应的日志:

04/13/16 11:06:36.891 [Debug] NB 51216 nbftclnt 200 PID:48890088 TID:1 File ID:200 [No context] 1 [AddDevice] /dev/rmt0
 Inquiry "SYMANTECFATPIPE 0.0     zb-media4.netbackup.sr.com"
 TargetHBA:LUN:InitiatorHBA = 0:0:0 State = 1 RefCount = 0
04/13/16 11:06:36.893 [Debug] NB 51216 nbftclnt 200 PID:48890088 TID:1 File ID:200 [No context] 1 [AddDevice] /dev/rmt1
 Inquiry "SYMANTECFATPIPE 0.1     zb-media4.netbackup.sr.com"
 TargetHBA:LUN:InitiatorHBA = 0:1:0 State = 1 RefCount = 0

日志显示已经完成Add Device,但查看java console san client看不到两个Python Tape。

从日志中看到Client发现了zb-media4.netbackup.sr.com这台Media的设备,但是通过nbemmcmd -listhosts看到的是zb-media4,bp.conf中也使用的zb-media4,并不带有后缀。

这时就需要通过添加别名解决:
继续阅读 »

NetBackup SAN Client on HPUX

在完成SAN Client配置后,Windows/AIX/Linux系统中会自动发现两个Python类型的Tape Driver,但是HP-UX并不会,在日志可以看到信息如下:

/usr/openv/netbackup/bin/vxlogview -o 200 -d all
04/13/16 17:44:30.089 [Debug] NB 51216 nbftclnt 200 PID:21061 TID:1 File ID:200 [No context] 1 \
 [DiscoverDevices:HpUx] opendir failed for /dev/sctl No such file or directory
04/13/16 17:44:30.100 [Debug] NB 51216 nbftclnt 200 PID:21061 TID:1 File ID:200 [No context] 1 \
[StdDeviceInquiry] Device type 12 found on /dev/pt/pt7 Vendor/Product: "HP      OPEN-XP12000    500 "

它在干嘛?它在寻找设备,从日志可以看出它去找了两个地方/dev/sctl和/dev/pt/,会扫描这两个目录下的所有文件。

下面这个KB,指导在/dev/sctl下创建文件,供参考

https://www.veritas.com/support/en_US/article.000012701

这样就可以了吗?不行,部分主机并不会去/dev/sctl下去寻找设备,而是只扫描/dev/pt目录中的文件,所以建议使用/dev/pt路径创建文件,简要如下:
继续阅读 »