Please enter search query.
Search <book_title>...
NetBackup™ 故障排除指南
Last Published:
2022-10-21
Product(s):
NetBackup (10.1)
- 介绍
- 故障排除过程
- 关于故障排除过程
- 对 NetBackup 问题进行故障排除
- 对安装问题进行故障排除
- 对配置问题进行故障排除
- 设备配置问题解决方法
- 测试主服务器和客户端
- 测试介质服务器和客户端
- 解决与 UNIX 客户端相关的网络通信问题
- 解决与 Windows 客户端相关的网络通信问题
- vnetd 代理连接故障排除
- 安全证书吊销故障排除
- 关于网络和主机名故障排除
- 验证 NetBackup 中的主机名和服务条目
- 关于 bpclntcmd 实用程序
- 使用“主机属性”窗口访问配置设置
- 解决磁盘已满的问题
- 冻结的介质故障排除注意事项
- 对 NetBackup Web 服务问题进行故障排除
- 对 NetBackup Web 服务器证书问题进行故障排除
- 解决 PBX 问题
- 远程主机验证问题故障排除
- 自动映像复制故障排除
- 对网络接口卡性能进行故障排除
- 关于 bp.conf 文件中的 SERVER 条目
- 关于存储单元不可用的问题
- 解决 Windows 上的 NetBackup 管理操作失败
- 在 UNIX 计算机上解析 NetBackup 管理控制台中显示的乱码文本
- 对 NetBackup 管理控制台中的错误消息进行故障排除
- “NetBackup 管理控制台”需要有额外的磁盘空间来存储日志和临时文件
- 在配置外部 CA 后,无法登录 NetBackup 管理控制台
- 基于文件的外部证书问题故障排除
- Windows 证书存储库问题故障排除
- 备份失败故障排除
- 对 NAT 客户端或 NAT 服务器的备份失败问题进行故障排除
- 对 NetBackup Messaging Broker(或 nbmqbroker)服务问题进行故障排除
- Windows 系统的电子邮件通知出现问题
- KMS 配置问题
- 由于密钥较大而导致启动 NetBackup CA 迁移时出现的问题
- 非特权用户(服务用户)帐户的相关问题
- auth.conf 文件中的组名称格式问题
- VxUpdate 软件包添加过程故障排除
- FIPS 模式的问题
- 恶意软件扫描问题
- 启用传输中数据加密的 NetBackup 作业问题
- 非结构化数据即时访问问题
- 使用 NetBackup 实用程序
- 灾难恢复
- 关于灾难恢复
- 关于灾难恢复要求
- 灾难恢复软件包
- 关于灾难恢复设置
- 推荐的备份方法
- 关于适用于 UNIX 和 Linux 的磁盘恢复过程
- 关于 UNIX 和 Linux 上的群集 NetBackup 服务器恢复
- 关于适用于 Windows 的磁盘恢复过程
- 关于 Windows 上的群集 NetBackup 服务器恢复
- 灾难恢复安装后在群集主服务器上生成证书
- 关于还原灾难恢复软件包
- 关于 DR_PKG_MARKER_FILE 环境变量
- 在 Windows 上还原灾难恢复软件包
- 在 UNIX 上还原灾难恢复软件包
- 关于恢复 NetBackup 目录库
- 关于在 Windows 计算机上执行 NetBackup 目录库恢复
- 关于从磁盘设备执行 NetBackup 目录库恢复
- 关于 NetBackup 目录库恢复和符号链接
- 关于 NetBackup 目录库恢复
- NetBackup 灾难恢复电子邮件示例
- 关于恢复整个 NetBackup 目录库
- 在目录库恢复之前建立与 NAT 介质服务器的连接
- 关于恢复 NetBackup 目录库映像文件
- 关于恢复 NetBackup 关系数据库
- 在配置 NetBackup Access Control 时恢复 NetBackup 目录库
- 从目录库备份的非主副本恢复 NetBackup 目录库
- 不使用灾难恢复文件恢复 NetBackup 目录库
- 从命令行恢复 NetBackup 用户控制的联机目录库备份
- 从 NetBackup 联机目录库备份还原文件
- 取消冻结 NetBackup 联机目录库恢复介质
- 在目录库恢复期间出现退出状态 5988 时要执行的步骤
- 索引
NetBackup 灾难恢复电子邮件示例
在完成目录库备份后,目录库备份策略可发送灾害恢复电子邮件。要配置目录库备份策略,请参见《NetBackup 管理指南,第 I 卷》:
http://www.veritas.com/docs/DOC5332
以下是成功备份目录库后的灾难恢复电子邮件示例:
From: NetBackup@example.com
Sent: Thursday, January 3, 2019 05:48
To: NetBackup Administrator
Subject: NetBackup Catalog Backup successful on host
master.example.com status 0
Attachments: cat_backup_1438271286_INCR
cat_backup_1438271286_INCR.drpkg
Server
master.example.com
NetBackup Version
8.1.X
Date
4/27/2017 05:46:45 AM
Policy
cat_backup
Catalog Backup Status
the requested operation was successfully completed (status 0).
WARNING: External CA-signed certificates could not be backed up.
Refer to the following article to configure external CA-signed certificates
on the host after disaster recovery installation:
https://www.veritas.com/support/en_US/article.100044249
DR image file: /dr/nbu_dr_file/cat_backup_1438271286_INCR
To ensure that the NetBackup catalog data is protected through
1/3/2019 10:46:45 AM, retain a copy of each attached file, and the
media or files listed below:
Catalog Recovery Media
Media Server Disk Image Path Image File Required
* media-server.example.com @aaaab cat_backup_1438267080_FULL
* media-server.example.com @aaaab cat_backup_1438271206_INCR
* media-server.example.com @aaaab cat_backup_1438271286_INCR
DR file written to
/dr/nbu_dr_file/cat_backup_1438271286_INCR
DR Package file written to
/dr/nbu_dr_file/cat_backup_1438271286_INCR.drpkg
The CA configuration at the time of catalog backup is as follows:
The master server ch12auto28 is configured to use NetBackup and external
CA-signed certificates.
ECA_CERT_PATH = MY\\ch12auto28.pne.ven.veritas.com
ECA_CRL_PATH = C:\Users\Administrator\Downloads\divgrt1.crl
ECA_CRL_PATH_SYNC_HOURS = 1
ECA_CRL_REFRESH_HOURS = 24
ECA_CRL_CHECK = 1
ECA_DR_BKUP_WIN_CERT_STORE = YES
The master server ms1.exampleveritas.com is configured to use the following
Key Management Servers.
KMS Server Name = kms1.example.veritas.com , KMS Server Type = KMIP
KMS Server Name = kms2.example.veritas.com , KMS Server Type = KMIP
KMS Server Name = kms3.example.veritas.com , KMS Server Type = KMIP
KMS Server Name = kms4.example.veritas.com , KMS Server Type = KMIP
KMS Server Name = ms1.exampleveritas.com , KMS Server Type = NBKMS
* - Primary Media
Catalog Recovery Procedure for the Loss of an Entire Catalog
You should create a detailed disaster recovery plan to follow should
it become necessary to restore your organization's data in the event
of a disaster. A checklist of required tasks can be a tremendous tool
in assisting associates in triage. For example, after the facility is
safe for data to be restored, the power and data infrastructure need
to be verified. When these tasks are completed, the following
scenarios will help to quickly restore the NetBackup environment, and
in turn, restore applications and data.
Disaster Recovery Procedure using the DR Package file and DR Image File
In the event of a catastrophic failure, use the following procedure to
rebuild the previous NetBackup environment.
Important Notes:
- If new hardware is required, make sure that the devices contain
drives capable of reading the media and that the drive controllers are
capable of mounting the drives.
- Keep the passphrase associated with the DR Package file handy.
This passphrase is set before the catalog backup policy configuration
using the NetBackup Administration Console or the nbseccmd command.
- If this catalog backup is encrypted using a key from a Key Management Server,
ensure that the Key Management Server is online before doing any of the following steps.
1. Install NetBackup.
a. The installation procedure prompts you to confirm if this is a DR
scenario.
i. On the UNIX installer, you can see a prompt as "Do you want to
do a disaster recovery on this master server? [y,n] (y)".
Select "y"
ii. On the Windows installer click the
"Disaster Recovery Master Server" button.
b. The installation procedure prompts you for the master server’s DR
Package
(refer to the /dr/nbu_dr_file/cat_backup_1438271286_INCR.drpkg
mentioned earlier).
Make sure that the Master Server can access the attached DR package
file.
c. Type the passphrase associated with the Master Server’s DR Package,
when prompted.
i. The installer validates the DR package using that passphrase
ii. In case of errors in validation, the installer aborts the
operation. To work around the issue, refer to the following
article: http://www.veritas.com/docs/000125933
2. Configure the devices necessary to read the media listed above.
3. Inventory the media.
4. Make sure that the master server can access the attached DR image file.
5. Start the NetBackup Recovery Wizard from the NetBackup Administration
Console. Or, start the wizard from a command line by entering
bprecover -wizard.
WARNING: CRLs are not backed as part of the DR package backup.
Refer to the following article to manually add the CRLs:
https://www.veritas.com/support/en_US/article.100044250
Disaster Recovery Procedure without the DR Image File
NOTE: ONLY ATTEMPT THIS AS A LAST RESORT If you do not have the
attachment included with this email, use the following instructions to
recover your catalog. (If using OpenStorage disk pools, refer to the
Shared Storage Guide to configure the disk pools instead of step 2 and
3 below ):
1. Install NetBackup.
2. Configure the devices necessary to read the media listed above.
3. Inventory the media.
4. Run
To recover from copy 1:
bpimport -create_db_info -stype AdvancedDisk -dp dp-advdisk
-dv /storage/advdisk
5. Run:
cat_export -client client1.example.com
6. Go to the following directory to find the DR image file
cat_backup_1438271286_INCR:
/usr/openv/netbackup/db.export/images/master.example.com/1438000000
7. Open cat_backup_1438271286_INCR file and find the BACKUP_ID
(for example: master.example.com_1438271286).
8. Run:
bpimport [-server name] -backupid master.example.com_1438271286
9. Run:
bprestore -T -w [-L progress_log] -C master.example.com -t 35
-p cat_backup -X -s 1438271286 -e 1438271286 /
10. Run the BAR user interface to restore the remaining image database
if the DR image is a result of an incremental backup.
11. To recover the NetBackup relational database, run:
bprecover -r -nbdb
12. Stop and Start NetBackup.
13. Configure the devices if any device has changed since the last
backup.
14. To make sure the volume information is updated, inventory the
media to update the NetBackup database.