NetBackup™ Bare Metal Restore 管理指南
- Bare Metal Restore 简介
- 配置 BMR
- 保护客户端
- 设置还原环境
- 共享资源树
- 还原客户端
- 管理 Windows 驱动程序软件包
- 管理客户端和配置
- 管理 BMR 引导服务器
- 故障排除
- 从 CD/DVD 引导时出现问题
- 还原耗时过长
- Solaris 介质引导的网络参数问题
- 如何在意外删除 BMR 配置后恢复客户端
- 在 UNIX 平台上,BMR 还原后首次引导失败
- 基于客户端网络的引导问题
- 恢复 Windows 客户端时验证备份失败
- 在 32 位体系结构的 Windows 操作系统上执行 BMR 物理备份到虚拟机的转换后,VM 需要很长时间进行引导。
- 在 Windows 平台上,启用 BMR 的物理备份到虚拟机的转换作业失败
- 有关从客户端备份创建虚拟机的故障排除问题
- 在系统引导期间和 BMR 首次引导期间,Solaris 11 及更高版本上的多项服务输出警告消息
- 执行 BMR 还原后首次引导期间,Solaris 11 及更高版本上的 Solaris 区域恢复需要一段时间进行重新配置
- 如果自定义 AI ISO 中没有文本安装程序软件包,则 Solaris BMR 还原操作将失败
- /boot 分区必须位于单独的分区上才能进行基于多设备的操作系统配置
- 在通过 ZFS 存储池还原客户端后的第一次引导过程中,可能会显示多个错误消息
- BMR 可能无法格式化或清除 ZFS 元数据
- 指定要使用自动映像复制和 BMR 保护的客户端的短名称
- A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
- 还原后 HP-UX 自动引导可能会失败
- 准备还原可能对 Solaris 客户端不起作用
- 对于 NetBackup 8.0 ,不支持在具有 NetBackup 8.1 的 Windows (x64) 上使用虚拟实例转换器 (VIC) 主机
- PTR or PTD failure because of boot server version mismatch after upgrade
- Error messages for prepare to restore, prepare to discover, and the bmrprep command with reference to secure communication in BMR
- Solaris x86 11.2 或更高版本客户端的介质还原可能会提示输入维护模式用户名和密码
- 发现任务可能会在客户端 PTD 任务成功完成后仍然处于“正在完成”状态
- 在客户端成功还原后,BMR 还原任务可能仍保持“正在完成”状态
- 如果正在创建共享资源树 (SRT) 时在引导服务器和客户端上启动了备份操作,则 BMR 还原之后,SRT 创建失败并显示错误
- 备份期间接收 BMR 信息时出错
- BMR 备份和还原作业详细信息未显示在 NetBackup Web UI 的活动监视器上
- 从客户端备份创建虚拟机
- 监视 Bare Metal Restore 活动
- 附录 A. NetBackup BMR 相关的附录
BMR client recovery to other NetBackup Domain using Auto Image Replication
This appendix explains how BMR and Auto-Image-Replication (A.I.R.) can be leveraged together to do bare metal recovery of primary domain clients onto other clients or disaster recovery domain.
NetBackup A.I.R. feature helps duplicating clients backup image onto defined destination or DR domain NetBackup setup. The feature performs fast backup import automatically providing primary data recovery readiness at DR site.
Refer to the NetBackup Administrator's Guide to learn more about A.I.R. and how to enable it.
For this dual-domain dual-site protection requirement, you need to enable Bare Metal Restore option in Auto Image Replication enabled backup policy. When Auto Image Replication and BMR enabled backup image gets imported at DR domain; NetBackup server checks if the image being imported is BMR enabled. If NetBackup server finds the image is BMR enabled then it automatically imports client BMR configuration as well. You can see client’s bare metal restore configuration node appears under UI menu > > > .
During BMR configuration import at DR site, BMR master server automatically tunes client configuration for DR site entities like NetBackup primary and media server host names and their IP-addresses. It updates older domain entries with new server details so that BMR recovery environment can approach to DR domain NetBackup servers while recovering client’s data. Optionally, you can add or update required host entries manually by copying or editing client’s imported BMR configuration. To manually edit client configuration, refer to the Managing clients and configurations chapter.
注意:
While you restore BMR configurations in a BMR A.I.R. setup, you may come across the following error: Add an appropriate host entry or host mapping for Name of the host and retry the operation.
To resolve the issue, you need to add a host in the host database of the DR domain.
Without any manual backup import or configuration change, client can be completely recovered at DR domain using BMR network or media based recovery procedure. You can also create client VM onto DR domain Virtual Environment Server using the feature.
Refer to the Creating virtual machine from client backup chapter.
注意:
It is recommended to list client short names in NetBackup backup policy at primary domain. If FQDN of DR domain is different than primary domain then client data recovery at DR domain may fail due to mismatch in client domain name. Primary domain > must enlist minimum OS file systems where NetBackup client is installed. In case of Windows, system state should be listed as well. If these points are not listed, then BMR configuration import at DR site may fail. Refer chapter Protecting Clients for more details about defining BMR backup policy.
注意:
Make sure BMR master server on DR domain is enabled; otherwise BMR configuration import at DR site fails.