当前位置:首页 » 数据仓库 » nbu如何配置ddboost
扩展阅读
webinf下怎么引入js 2023-08-31 21:54:13
堡垒机怎么打开web 2023-08-31 21:54:11

nbu如何配置ddboost

发布时间: 2023-06-03 20:21:41

⑴ nbu怎样恢复oracle数据库

1、安装操作系统
2、安装数据库系统
3、安装nbu软件及配置
--安装客户端
上传SYMCnbclient_Linux-RedHat2.6.18_7.5.0.2.tar编辑本机hosts
vi /etc/hosts
添加:192.168.99.252 hdnbu1
解压:
[root@scmtest u01]# tar -xvf SYMCnbclient_Linux-RedHat2.6.18_7.5.0.2.tar[root@scmtest u01]# cd SYMCnbclient_Linux-RedHat2.6.18_7.5.0.2[root@scmtest SYMCnbclient_Linux-RedHat2.6.18_7.5.0.2]# ./install过程当中要输入备份服务端:hdnbu1
然后再用oracle用户执行:
[root@scmtest bin]# su - oracle
[oracle@scmtest ~]$ cd /usr/openv/netbackup/bin[oracle@scmtest bin]$ ./oracle_link
Thu Feb 21 14:03:02 CST 2013
All Oracle instances should be shutdown before running this script.
Please log into the Unix system as the Oracle owner for running this scriptDo you want to continue? (y/n) [n] y
LIBOBK path: /usr/openv/netbackup/bin
ORACLE_HOME: /software/oracle/proct/10.2.0/db1Oracle version: 10.2.0.5.0
Platform type: x86_64
Linking LIBOBK:
ln -s /usr/openv/netbackup/bin/libobk.so64 /software/oracle/proct/10.2.0/db1/lib/libobk.soDone
Please check the trace file located in /tmp/make_trace.23602to make sure the linking process was successful.
4、编辑初始参数文件
这时候,需要进行修改,比如原来用的什么盘,现在用什么盘等编辑后如下:
*._addm_auto_enable=FALSE
*._b_tree_bitmap_plans=FALSE
*._db_block_numa=1
*._enable_NUMA_optimization=FALSE
*._optimizer_cartesian_enabled=FALSE
*._optimizer_skip_scan_enabled=FALSE
*.archive_lag_target=1800
*.audit_file_dest='/software/oracle/admin/ncerp/amp'
*.background_mp_dest='/software/oracle/admin/ncerp/bmp'
*.compatible='10.2.0.5.0'
*.control_files='/u01/ncerp/control/control01.ctl','/u01/ncerp/control/control02.ctl'
*.core_mp_dest='/software/oracle/admin/ncerp/cmp'
*.db_block_size=8192
*.db_cache_size=4294967296
*.db_create_file_dest='/u01/ncerp/flash_recover'
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='ncerp'
*.java_pool_size=33554432
*.job_queue_processes=10
*.large_pool_size=33554432
*.log_archive_dest_1='location=/u01/ncerp/arch'
*.log_archive_format='%s_%t_%r.log'
*.max_mp_file_size='1024'
*.open_cursors=1000
*.optimizer_dynamic_sampling=4
*.optimizer_index_cost_adj=40
*.parallel_max_servers=5
*.pga_aggregate_target=2147483648
*.processes=800
*.recyclebin='OFF'
*.shared_pool_size=838860800
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
5、根据参数文件,建相应的目录
[oracle@scmtest ~]$ mkdir -p /u01/ncerp/control/[oracle@scmtest u01]$ mkdir -p /app/oracle/admin/ncerp/cmp[oracle@scmtest u01]$ mkdir -p /app/oracle/admin/ncerp/bmp[oracle@scmtest u01]$ mkdir -p /app/oracle/admin/ncerp/amp[oracle@scmtest u01]$ mkdir -p /app/oracle/admin/ncerp/pfile[oracle@scmtest u01]$ mkdir -p /u01/ncerp/flash_recover[oracle@scmtest u01]$ mkdir -p /u01/ncerp/arch[oracle@scmtest ncerp]$ mkdir oradata
注意:这些要与参数文件对应,要不然无法启动!
6、恢复控制文件
export ORACLE_SID=ncerp
[oracle@scmtest u01]$ rman target /
Recovery Manager: Release 10.2.0.5.0 - Proction on Thu Feb 21 14:17:10 2013Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database (not started)RMAN> startup nomount pfile='/u01/ncpfile.ora';Oracle instance started
Total System Global Area 5217714176 bytesFixed Size 2103536 bytesVariable Size 905971472 bytesDatabase Buffers 4294967296 bytesRedo Buffers 14671872 bytes从nbu的服务器上查询要恢复的控制文件
hdnbu1:/tmp # bplist -C RD162 -t 4 -R -b -l / | more-rw-rw---- oracle dba 10747904 Mar 28 11:26 /c-3383507379-20130328-0b-rw-rw---- oracle dba 11010048 Mar 28 11:25 /c-2177845250-20130328-0d-rw-rw---- oracle dba 10747904 Mar 28 11:25 /cntrl_9202_1_811250475-rw-rw---- oracle dba 10747904 Mar 28 11:25 /cntrl_7788_1_811250456-rw-rw---- oracle dba 10747904 Mar 28 11:25 /c-3383507379-20130328-0a-rw-rw---- oracle dba 11010048 Mar 28 11:24 /c-2177845250-20130328-0c-rw-rw---- oracle dba 114032640 Mar 28 11:17 /al_7786_1_811249961-rw-rw---- oracle dba 123207680 Mar 28 11:17 /al_7785_1_811249961-rw-rw---- oracle dba 3670016 Mar 28 11:17 /al_9200_1_811249960-rw-rw---- oracle dba 3932160 Mar 28 11:17 /al_9199_1_811249959-rw-rw---- oracle dba 11010048 Mar 28 09:25 /c-2177845250-20130328-0b-rw-rw---- oracle dba 10747904 Mar 28 09:25 /c-3383507379-20130328-09-rw-rw---- oracle dba 10747904 Mar 28 09:25 /cntrl_9197_1_811243259-rw-rw---- oracle dba 10747904 Mar 28 09:25 /cntrl_7783_1_811243253RMAN> run
2> {
3> allocate channel c1 type 'sbt_tape';
4> send 'NB_ORA_CLIENT=RD162';
5> restore controlfile from '/cntrl_24145_1_828414748';6> release channel c1;
7> }
using target database control file instead of recovery catalogallocated channel: c1
channel c1: sid=874 devtype=SBT_TAPE
channel c1: Veritas NetBackup for Oracle - Release 7.5 (2012050902)sent command to channel: c1
Starting restore at 2013-03-28 12:41:30
channel c1: restoring control file
channel c1: restore complete, elapsed time: 00:05:16output filename=/u02/ncerp/control/control01.ctloutput filename=/u02/ncerp/control/control02.ctlFinished restore at 2013-03-28 12:46:47
released channel: c1
7、还原数据库文件
在这里要查一下数据库是否已经mount
sql> select status from v$instance;
STATUS
------------
MOUNTED
RMAN> run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
send 'NB_ORA_CLIENT=RD162';
set newname for datafile '/backup/ncerp/oradata/system01.dbf' to '/u02/ncerp/oradata/system01.dbf' ;set newname for datafile '/backup/ncerp/oradata/system02.dbf' to '/u02/ncerp/oradata/system02.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_index03_1.dbf' to '/u02/ncerp/oradata/nnc_index03_1.dbf';set newname for datafile '/backup/ncerp/oradata/undotbs1.dbf' to '/u02/ncerp/oradata/undotbs1.dbf' ;set newname for datafile '/backup/ncerp/oradata/sysaux01.dbf' to '/u02/ncerp/oradata/sysaux01.dbf' ;set newname for datafile '/backup/ncerp/oradata/users01.dbf' to '/u02/ncerp/oradata/users01.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data01_1.dbf' to '/u02/ncerp/oradata/nnc_data01_1.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data01_2.dbf' to '/u02/ncerp/oradata/nnc_data01_2.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data01_3.dbf' to '/u02/ncerp/oradata/nnc_data01_3.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data01_4.dbf' to '/u02/ncerp/oradata/nnc_data01_4.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data02_1.dbf' to '/u02/ncerp/oradata/nnc_data02_1.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data02_2.dbf' to '/u02/ncerp/oradata/nnc_data02_2.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data03_1.dbf' to '/u02/ncerp/oradata/nnc_data03_1.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data03_2.dbf' to '/u02/ncerp/oradata/nnc_data03_2.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data03_3.dbf' to '/u02/ncerp/oradata/nnc_data03_3.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data03_4.dbf' to '/u02/ncerp/oradata/nnc_data03_4.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_index02_1.dbf' to '/u02/ncerp/oradata/nnc_index02_1.dbf';set newname for datafile '/backup/ncerp/oradata/nnc_index01_1.dbf' to '/u02/ncerp/oradata/nnc_index01_1.dbf';set newname for datafile '/backup/ncerp/oradata/nnc_index01_2.dbf' to '/u02/ncerp/oradata/nnc_index01_2.dbf';set newname for datafile '/backup/ncerp/oradata/nnc_index01_3.dbf' to '/u02/ncerp/oradata/nnc_index01_3.dbf';set newname for datafile '/backup/ncerp/oradata/nnc_index01_4.dbf' to '/u02/ncerp/oradata/nnc_index01_4.dbf';set newname for datafile '/backup/ncerp/oradata/iufo01.dbf' to '/u02/ncerp/oradata/iufo01.dbf' ;set newname for datafile '/backup/ncerp/oradata/iufo02.dbf' to '/u02/ncerp/oradata/iufo02.dbf' ;set newname for datafile '/backup/ncerp/oradata/nnc_data03_5.dbf' to '/u02/ncerp/oradata/nnc_data03_5.dbf' ;Restore database;
Switch datafile all;
}
vi res_test.sh 内容如下:
export ORACLE_SID=ncerp
rman target / < run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
send 'NB_ORA_CLIENT=RD162';
做一次恢复测试看看
说明需要3556这个归档日志
所以恢复时,从这个日志进行恢复!
也可以采用后台运行方式
9、数据库恢复
SQL>
cancel
说明,如果上面日志可能有点大的时候,我们需要调整,比如说删除日志组等,然后还重新添加日志到新位置10、打开数据库
SQL> alter database open resetlogs;
Database altered.
11、创建临时表空间

⑵ nbu client 怎么配置

  1. 配/etc/hosts把master server和media server的主机名 ip加进去

  2. 配master server和media server的hosts把client的主机名和ip加进去

  3. ./install安装。安装过程中输入master和media的主机名

  4. 安装完成后到bin目录下bpclntcmd -pn检测是否有信息输出,报错说明之间端口不通

  5. 以上都成功后到master server的nbu console里面的host properties 应该能看到client信息

  6. 对应的备份策略有很多,,不知道你要备份哪一种


⑶ 请教,关于NBU media server问题

NBUversion:7.5

MediaServer:WindowsServer 2008R2 hostname:BALY

带库: IBM3584

最近在巡视时发现MediaServer备份失败,打开NBUAdministrotar Console 发现MediaServer上的一个drive出现 pathmissing。

1 TroubleShooting

在命令行执行发现一个MISSING_PATH,如下:

C:\Program Files\Veritas\Volmgr\bin>tpconfig -l

Type Num Index Type DrNum Status Comment Name Path

robot 0 - TLD - - - - bcsyyfx

drive - 9 hcart2 8 DOWN - IBM.ULT3580-TD5.009 MISSING_PATH:{4,0,6,0}:00078AD2A

Robot下一共有12个drive,其中一个出现问题,检查操作系统设备驱动发现tape驱动都正常运行,这里设置的是NBU通过操作系统驱动来获得路径的,所以肯定是NBU出问题了,经过检查这个设备驱动在操作系统的port=4bus=0 target=5 lun=0 {4,0,5,0},而NBU中设置的却是4,0,6,0,所以需要重新配置path。

2重新配置path

2.1在MediaServer上,删除现有路径

…\Volmgr\bin>tpconfig –delete –drpath –port 4 –bus 0 –target 6 –lun0 –asciiname IBM.ULT3580-TD5.009

2.2重启nbu进程

…\Netbackup\bin>bpdown –f –v

…\Netbackup\bin>bpup –f -v

2.3查看drive 状态

…\Volmgr\bin>vmoprcmd

MISS_PATH的drive已经删除,但是其他dirve状态由TLD变为restart,文档上并没有restart的介绍,上网查了一下,出现restart意思是,当在MediaServer上添加、删除、修改robot或dirve后,device path需要重新启动。好吧。不管它。

2.4重新添加path

在MasterServer上使用向导”configureStrage Devices”,勾选选择MediaserverBALY,报错”error connecting to oprd>BALY: oprd returned an abnormal status (96)”这样就无法添加drive path了,只能先解决这个问题先。

从网上搜了一个解决办法

先在MediaServer上关闭NBU进程bpdown–f –v

修改NBU安装路径下Volmgr\misc目录下的vmd.lock文件名称

开启进程bpup –f–v

在MasterServer上执行NBU安装路径\NetBackup\bin\admincmd\nbrbutil –resetMediaServer BALY

注意:1先使用nbrbutil -mp 检查没有device Allocations 卡在EMM中

2 使用nbrbutil前确保没有job运行,nbrbutil会关闭所以正常运行的job

重新在MasterServer打开控制台,向导”configureStrage Devices”可以正常使用,选中BALY,下一步,添加设备,下一步,然后OK

在MediaServer上使用vmoprcmd检查drive的状态,都是TLD,手工备份测试,可以备份了,OK大功告成。

⑷ NBU故障代码83:备份走FT的故障处理

备份走FT,报异仔友常状态码83,如下图

1.查询知道SAN client 主机名与现有的主机名不一致

2.重新添加SAN client 故障恢复

3.SAN client 上面,

一、修改bp.conf文件,注释#SANCLIENT = 1,之后 bp.kill_all,之后念做槐 bpclntcmd -clear_host_cache,之后 bp.start_all

二、完成在server上删除后,去注释#SANCLIENT = 1,之后 bp.kill_all,之后 bp.start_all

4.NBU server上面,

一、nbftconfig -deleteclient  hostname  #删除主机,若不成功如下,则胡物 nbrbutil -listorphanedpipes && nbrbutil -releaseorphanedpipes

----------------

Run 'nbrbutil -listorphanedpipes' and if the output shows orphaned pipe(s), run 'nbrbutil -releaseorphanedpipes' to release same.

Following that, run 'nbftconfig -deleteserver' command, which should be successful. If not, collect nbdb_unload information and examine output per internal notes below.

Problem

After properly deleting all FT clients associated with an FT server, the following error code may occur when trying to delete the FT server:

# nbftconfig -deleteserver ftserver01

Failed to delete the FT server

EXIT error: unable to process request because the server resources are busy

EXIT status = 134

There are some jobs on this machine

--------------------

二、 nbemmcmd -deletehost -machinename hostname    #删除主机

三、完成主机上的重新配置后,重新扫描,nbftconfig -rescanallclients

⑸ NBU备份软件词汇总结

differetial incremental backup:差异增量备份
cumulative incremental backup:累积增量备份
user backup:用户备份
user archive:用户档案
archived redo log backup:归档重做日志备份
properties:属性
item:项目
scheles:时间表、调度
frequency:频率
calendar:日历
archive files:存档文件
archive:封存、存档
keyword phrase:关键字词组
task progess:任务进度
manual backup:手动备份
retetion:保留
automatic:自动
application backup:应用程序备份
unknow schele backup:未知时间表备份
no data classification:没有数据分类
platinum:铂, 白金
gold:黄金
silver:白银
bronze:青铜
any available:任何可用
puredisk:纯磁盘
advancedisk:高级风险
catalog-backup:目录备份
limit jobs per policy:限制每个策略的作业数
job priority:工作优先级
higher number is greater priority:数字越大优先级越高
go into effect at:生效于,从什么时间开始生效
disable client-side deplicati:禁用客户端重复数据删除
use accelerator:使用加速器
keyword phrase:关键字词组
enable indexing for search :为渣宽粗搜索启用索引
must also be enabled for the schele and client:还必如镇须为计划和客户端启用
indexing server:索引服务器
multiple copies:多个副本
override policy storage selection:覆盖策略存储选择
override policy volume pool:覆盖策略卷池
override media owner:覆巧孝盖媒体所有者
media multiplexing:媒体多路复用
virtual machine selection:虚拟机选择
select manually:手动选择
select automatically through query:通过查询自动选择
browse and select virtual machine:浏览并选择虚拟机
enable vcloud director integration:启用vcloud控制器集成
netbackup host to perform automatic virtual machine selection:netbackup主机执行自动虚拟机选择
query builder:查询生成器
field:领域
operator:操作人员
value:值,价值
advanced:高级
test the query to view results. vms selected for backup may vary with any change in the virtual environment:测试查询以查看结果。 选择用于备份的虚拟机可能会随虚拟环境的变化而变化
reuse vm selection query results:重用vm选择查询结果
backup selections:备份选择
optimizations:优化
enable file recovery from vm backup:从vm备份启用文件恢复
enable block-level incremental backup:启用块级增量备份
exclude deleted blocks:排除已删除的块
Exclude swap and paging files:排除交换和分页文件
transport modes:传输方式
netbackup tries each selected transport in order from top to bottom:netbackup按从上到下的顺序尝试每个选定的传输
san: use san to move virtual disk data:san方式,使用san网络移动虚拟磁盘数据
nbd: do not encrypt the virtual disk data for over-the-network transform :nbd方式,非san方式,不要加密虚拟磁盘数据以进行网络转换
hotadd: use virtual disk files from netbackup server : hotadd方式,使用netbackup服务器中的虚拟磁盘文件
encrypt the virtual disk data for over-the-network transform : 加密虚拟磁盘数据以进行网络转换
primary vm identifier:主虚拟机标识符
orphaned snapshot handling:孤立快照处理
application protection:应用保护
enable exchange recovery:启用exchange恢复
enable sql server recovery:启用sql server恢复
print preview:打印预览
liveupdate:实时更新
undo:取消
edit:编辑
view:视图、看法、意见
toolbar:工具栏
status bar:状态栏
previous pane:前窗格
customize:定制
refresh:刷新
large icons:大图标
columns:列
to new policy:复制到新策略
activate:启用
deactivate:停用
troubleshooter:疑难解答
storage units:存储单元
storage lifecycle policies:存储生命周期策略
catalog:目录
host properties:主机属性
indexing servers:索引服务器
media and device management:媒体和设备管理
volume pools:卷池
datastore:数据存储
robots:机器人
standalone:独立的
topology:拓扑结构
credentials:证书
disk array hosts:磁盘阵列主机
access management:访问管理
bare metal restore management:裸机还原管理
vm conversion clients:虚拟机转换客户端
resources:资源
discovered configurations:发现的配置
archived boot floppies:存档的启动软盘
bare metal restore tasks:裸机还原任务
vm conversion tasks:虚拟机转换任务
logging assistant:

getting started:入门
get step-by-step help setting up netbackup:获得有关设置netbackup的分步帮助
configure storage devices:配置存储设备
define robots and drives:定义机器人和驱动器
configure disk storage servers:配置磁盘存储服务器
define servers supporting data deplication,openstorage or advanceddisk technology:定义支持重复数据删除,开放存储或高级磁盘技术的服务器
configure cloud storage servers:配置云存储服务器
define disk and media servers to be used in a disk pool:定义要在磁盘池中使用的磁盘和介质服务器
configure volumes:配置卷
inventory robots and define volumes for use in standalone drives:盘点机器人并定义用于独立驱动器的卷
configure the catalog backup:配置目录备份
specify how and when netbackup configuration and catalog information is to be backed up:指定如何以及何时备份“netbackup配置和目录信息”
create a policy:制定策略
define scheles and setting for backing up one or more clients,snapshots or virtual machines:定义用于备份一个或多个客户端,快照或虚拟机的计划和设置
import images:导入图像
this wizard will assist you in stepping through an import:该向导将帮助您逐步完成导入
recover the catalog:恢复目录
restore the catalog in a disaster recovery situation from a hot,online catalog backup:通过热的在线目录备份在灾难恢复情况下还原目录