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 相关的附录
Virtual Machine Creation CLIs
You can use command-line interface to perform various operations related to VM creation from client backup.
Submitting a job for VM creation from backup
Submit a job for VM creation using command nbrestorevm from master server or any client with administrative privilege. In case you fire nbrestorevm without any parameter, following help is displayed.
For VM restore:
nbrestorevm -bmr {-vmw|-vmhv} -C vm_client [-S master_server] [-O] [-R rename_file (must be an absolute path)] [-L progress_log [-en]] [-k "keyword phrase"] [-disk_media_server media_server] [-s mm/dd/yyyy [HH:MM:SS]] [-e mm/dd/yyyy [HH:MM:SS]] [-w [hh:mm:ss]] [-vmtm vm_transport_mode] [-vmserver vm_server] [-vmproxy vm_proxy] [-vmpo] [-vmtd] [-vmfd] [-vmbz] [-vmdrs] [-vmpdrs] [-vmvxd] [-vmkeephv] [-vmid] [-vmsn] [-vmrb] [-force] [-vcd] [-vcdred] [-vcdovw] [-vcdrte] [-vcdtemplate] [-vcdlfree] [-vcdremv] [-ir_activate] [-temp_location temp_location_for_writes] [[-ir_deactivate | -ir_reactivate | -ir_done] instant_recovery_identifier] [-ir_reactivate_all [-vmhost vm_host] [-media_server media_server_activate_vm]] [-ir_listvm]
For BMR VM Conversion:
nbrestorevm -bmr {-vmw|-vmhv} -C vm_client [-S master_server] [-O] -vmserver vm_server -vmproxy vm_proxy -veconfig ve_config_file_Path (must be an absolute path) [-config bmr_config_name] [-vmpo] [-vmsn] [-systemOnly]
Where,
-vmw : VMWare
-C : Name of the client to be converted to VM
-S : Name of the master server
-O : Option to overwrite VM if already exists with the same name
-vmserver : vCenter or ESX server name
-vmproxy : Virtual Image Converter or NB-Proxy name
-veconfig : File full path containing virtual environment details
-vmpo : [optional] If provided VM will be automatically powered On
Example:
nbrestorevm -bmr -vmw -C d1950-17.punbmr.com -vmserver bmrrh10.vxindia.veritas.com -vmproxy ix3650-21.punbmr.com -veconfig C:\B2V\veconfig-vmw1.txt -config current -O -vmpo
[Info] V-433-32 Successfully submitted job. For more details please see VM Conversion Tasks
Details for -veconfig file.
For example, C:\B2V\veconfig.txt contains below information in parameter = value manner.
esxhost="bmrvmw1.vxindia.veritas.com"
name="Test_NBRestoreVM"
network="VM Network"
diskformat="ThinVdisk"
toolsIsoPath="C:\B2V\windows_esx5.iso"
datacenter="/TestFolderAboveDC/Public Datacenter"
folder=[optional]"/TestFolderAboveDC/Public Datacenter/vm"
resourcepool= [optional]"/TestFolderAboveDC/Public Datacenter/host/bmrvmw1.vxindia.veritas.com/Resources"
harddisk=0:"B2V_4TB"
harddisk=1:"storage1 (2)"
harddisk=2:"storage2 (1)"
Tracking VM creation jobs
You can track submitted VM creation jobs using following CLIs.
On master server, to list submitted jobs which are in running state, fire:
<C:\Program Files\Veritas\NetBackup\bin>bmrs -operation list -resource B2VrestoreTask
On master server, to list VM creation jobs history (successfully completed or failed), fire:
<C:\Program Files\Veritas\NetBackup\bin>bmrs -operation list -resource B2VrestoreTaskLog
Deleting VM creation related task logs
On master server, to clean-up logs from the database, fire:
<C:\Program Files\Veritas\NetBackup\bin>bmrs -o delete -resource b2vrestoretasklog -id <p2vRestoreTaskLogId>
You can get by using command in the list operation for task log keyword.
For more information, refer NetBackup Commands Reference Guide.