# 配置Oracle备份策略
# bpplinfo Oracle_Backup -add -policytype Oracle -residence Primary_Disk -retention 7 -client client01

# 添加Oracle备份计划
# bpplsched -add Oracle_Backup -stype FULL -freq 0 -cal 2 -incr 0 -window 21:00-06:00 -days Sun

# 配置Oracle RMAN
# vi /opt/oracle/product/19c/db_1/dbs/rman_backup.rcv

run {
allocate channel ch1 type ‘SBT_TAPE’ parms ‘SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64’;
backup database plus archivelog;
release channel ch1;
}

# 执行Oracle备份
# rman target / @/opt/oracle/product/19c/db_1/dbs/rman_backup.rcv

# 示例输出
Recovery Manager:
Release 19.0.0.0.0 – Production on Sun Apr 1 21:00:00 2026
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.

connected to target database: FGEDUDB (DBID=1234567890)

RMAN> run {
2> allocate channel ch1 type ‘SBT_TAPE’ parms ‘SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64’;
3> backup database plus archivelog;
4> release channel ch1;
5> }

using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=123 device type=SBT_TAPE
channel ch1: NetBackup for Oracle – Release 9.1 (2026010100)

Starting backup at 01-APR-26
current log archived
channel ch1: starting archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=100
input archived log thread=1 sequence=101
channel ch1: starting piece 1 at 01-APR-26
channel ch1: finished piece 1 at 01-APR-26
piece handle=backup_1234567890_1 tag=TAG20260401T210000 comment=NONE
channel ch1: backup set complete, elapsed time: 00:01:00
channel ch1: starting full datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/oracle/app/oracle/oradata/fgedudb/system01.dbf
input datafile file number=00002 name=/oracle/app/oracle/oradata/fgedudb/sysaux01.dbf
input datafile file number=00003 name=/oracle/app/oracle/oradata/fgedudb/undotbs01.dbf
input datafile file number=00004 name=/oracle/app/oracle/oradata/fgedudb/users01.dbf
channel ch1: starting piece 1 at 01-APR-26
channel ch1: finished piece 1 at 01-APR-26
piece handle=backup_1234567891_1 tag=TAG20260401T210000 comment=NONE
channel ch1: backup set complete, elapsed time: 00:30:00
channel ch1: starting archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=102
channel ch1: starting piece 1 at 01-APR-26
channel ch1: finished piece 1 at 01-APR-26
piece handle=backup_1234567892_1 tag=TAG20260401T210000 comment=NONE
channel ch1: backup set complete, elapsed time: 00:01:00
Finished backup at 01-APR-26

released channel: ch1

RMAN> exit

Recovery Manager complete.

# 配置SQL Server备份策略
# bpplinfo SQL_Server_Backup -add -policytype MS-SQL-Server -residence Primary_Disk -retention 7 -client client02

# 添加SQL Server备份计划
# bpplsched -add SQL_Server_Backup -stype FULL -freq 0 -cal 2 -incr 0 -window 21:00-06:00 -days Sun

# 执行SQL Server备份
# sqlcmd -S fgedudb -U sa -P “P@ssw0rd” -Q “BACKUP DATABASE [fgedudb] TO DISK = ‘NBU’ WITH NAME = ‘Full Backup’, INIT”

# 示例输出
1> BACKUP DATABASE [fgedudb] TO DISK = ‘NBU’ WITH NAME = ‘Full Backup’, INIT
2> GO
Processed 10240 pages for database ‘fgedudb’, file ‘fgedudb’ on file 1.
Processed 256 pages for database ‘fgedudb’, file ‘fgedudb_log’ on file 1.
BACKUP DATABASE successfully processed 10496 pages in 15.000 seconds (5.598 MB/sec).

# 配置VMware备份策略
# bpplinfo VMware_Backup -add -policytype VMware -residence Primary_Disk -retention 7 -client client03

# 添加VMware备份计划
# bpplsched -add VMware_Backup -stype FULL -freq 0 -cal 2 -incr 0 -window 21:00-06:00 -days Sun

# 配置VMware备份选项
# bpplinfo VMware_Backup -modify -vmware_backup_type FULL -vmware_transport_method NBDSSL

# 执行VMware备份
# bpbackup -i -p VMware_Backup -s “VMware Backup” -w 3600

# 示例输出
JobID 1234 started
Job 1234: Backup job started
Job 1234: Info bpbkar: start
Job 1234: Info bpbkar: VMware backup of virtual machine ‘VM01’
Job 1234: Info bpbkar: Backup completed successfully
Job 1234: Info bpbkar: EXITING with status 0

# 配置云存储单元
# nbdevconfig -createstu -storage_unit Cloud_Storage -media_server media01 -cloudprovider AWS -bucketname nbu-backup -accesskey “AKIAEXAMPLE” -secretkey “SECRETKEYEXAMPLE”

# 查看云存储单元
# nbdevconfig -liststu

# 示例输出
Storage Unit Name: Cloud_Storage
Media Server: media01
Type: Cloud
Status: UP
Cloud Provider: AWS
Bucket Name: nbu-backup
Access Key: AKIAEXAMPLE

# 配置云存储生命周期策略
# nbstl -add -name “Cloud_Backup” -description “Cloud backup storage strategy”
# nbstl -addstage -name “Cloud_Backup” -num 1 -unit Cloud_Storage -residence Cloud_Storage -on_disk no -retention 365

# 应用云存储生命周期策略到备份策略
# bpplinfo Full_Backup -modify -storage_unit Cloud_Storage -st_lifecycle Cloud_Backup

# 示例输出
{
“data”: {
“majorVersion”: 9,
“minorVersion”: 1,
“patchVersion”: 0,
“buildNumber”: 1234,
“buildType”: “RELEASE”
}
}

# 使用API创建备份策略
# cat create_policy.json
{
“data”: {
“type”: “policies”,
“id”: “Test_Policy”,
“attributes”: {
“name”: “Test_Policy”,
“policyType”: “STANDARD”,
“active”: true,
“clients”: [“client01”],
“schedules”: [
{
“name”: “Full”,
“scheduleType”: “FULL”,
“frequency”: “WEEKLY”,
“retentionLevel”: “7_Day_Retention”
}
]
}
}
}

# 调用API创建策略
# curl -k -u admin:P@ssw0rd -X POST -H “Content-Type: application/vnd.netbackup+json;version=2.0” -d @create_policy.json https://master-server:1556/netbackup/config/policies

# 示例输出
{
“data”: {
“type”: “policies”,
“id”: “Test_Policy”,
“attributes”: {
“name”: “Test_Policy”,
“policyType”: “STANDARD”,
“active”: true,
“clients”: [“client01”],
“schedules”: [
{
“name”: “Full”,
“scheduleType”: “FULL”,
“frequency”: “WEEKLY”,
“retentionLevel”: “7_Day_Retention”
}
]
}
}
}

# 查看媒体服务器
# nbemmcmd -listhosts

# 示例输出
Server Name: master-server
Machine Type: MASTER
Server Type: PRIMARY
Master Server: master-server
Client Name: master-server
NetBackup Version: 9.1.0.0

Server Name: media01
Machine Type: MEDIA
Server Type: PRIMARY
Master Server: master-server
Client Name: media01
NetBackup Version: 9.1.0.0

Server Name: media02
Machine Type: MEDIA
Server Type: PRIMARY
Master Server: master-server
Client Name: media02
NetBackup Version: 9.1.0.0

# 添加存储单元
# nbdevconfig -createstu -storage_unit New_Disk -media_server media02 -diskpath /backup/disk02 -max_media_servers 2 -max_disk_volumes 100

# 配置负载均衡
# bpplinfo Full_Backup -modify -storage_unit New_Disk -maxjobs 10

# 配置Nagios监控
# vi /usr/local/nagios/etc/objects/commands.cfg

define command {
command_name check_nbu_jobs
command_line $USER1$/check_nbu_jobs -H $HOSTADDRESS$ -u admin -p P@ssw0rd
}

define command {
command_name check_nbu_storage
command_line $USER1$/check_nbu_storage -H $HOSTADDRESS$ -u admin -p P@ssw0rd
}

# 配置监控服务
# vi /usr/local/nagios/etc/objects/services.cfg

define service {
host_name master-server
service_description NBU Backup Jobs
check_command check_nbu_jobs
max_check_attempts 3
check_interval 5
retry_interval 1
check_period 24×7
notification_interval 60
notification_period 24×7
}

define service {
host_name master-server
service_description NBU Storage Usage
check_command check_nbu_storage
max_check_attempts 3
check_interval 30
retry_interval 5
check_period 24×7
notification_interval 60
notification_period 24×7
}

# 重启Nagios服务
# systemctl restart nagios

# 查看监控状态
# curl -s http://fgedudb/nagios/cgi-bin/status.cgi | grep -E “NBU|CRITICAL|WARNING”

# 示例输出

# 1. 充分了解集成需求
# 分析业务需求和系统环境
# 确定集成目标和范围

# 2. 选择合适的集成方式
# 根据系统类型选择合适的集成插件
# 配置适当的集成参数

# 3. 测试集成效果
# 在测试环境中测试集成功能
# 验证备份和恢复操作

# 4. 监控集成状态
# 配置监控工具监控集成状态
# 及时发现并解决集成问题

# 5. 文档化集成配置
# 详细记录集成配置和操作步骤
# 建立集成维护手册

# 6. 定期更新集成组件
# 及时更新插件和补丁
# 确保集成的安全性和稳定性

# 7. 培训运维人员
# 培训运维人员熟悉集成操作
# 建立集成故障处理流程

# 8. 制定回滚计划
# 准备集成失败的回滚方案
# 确保系统的可靠性

## 背景
– 企业规模：大型企业，约2000名员工
– IT环境：
– 数据库：Oracle、SQL Server
– 虚拟化：VMware vSphere
– 云存储：AWS S3
– 监控：Nagios

## 集成需求
1. 实现数据库的自动备份
2. 实现虚拟机的快照备份
3. 实现备份数据的云存储
4. 实现备份系统的监控

## 实施过程
1. 数据库集成：
– 安装Oracle和SQL Server插件
– 配置数据库备份策略
– 测试数据库备份和恢复

2. 虚拟化集成：
– 安装VMware插件
– 配置虚拟机备份策略
– 测试虚拟机备份和恢复

3. 云存储集成：
– 安装云存储插件
– 配置AWS S3存储单元
– 配置云存储生命周期策略

4. 监控集成：
– 安装Nagios插件
– 配置Nagios监控服务
– 测试监控告警

## 实施结果
1. 数据库备份：实现了Oracle和SQL Server的自动备份，备份成功率达到99%
2. 虚拟机备份：实现了VMware虚拟机的快照备份，备份速度提高了50%
3. 云存储：实现了备份数据的云存储，存储成本降低了30%
4. 监控：实现了备份系统的实时监控，故障响应时间缩短了80%

## 经验教训
1. 充分的需求分析是集成成功的关键
2. 选择合适的集成插件可以提高集成效率
3. 测试是确保集成质量的重要环节
4. 监控是确保集成稳定性的重要手段