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.