Using the bprestore command to restore Microsoft Azure VM with modified metadata to an alternate location

Run the following bplist command to list the files:
bplist -S master_server -C configuration_server_01 -unix_files -R 3 -t 44 -X -s <bktime> -e <bktime> "/21c71fdf-3ee5-4b57-8c51-18ebe7032237/skrg1/bkvm15" > listfile
Open the listfile in the editor and remove the special characters at the end of the line. Remove all the paths that end with forward slash / that corresponds to directories.
Run the following command on the NetBackup master server using the modified values for the mentioned parameters in step 1.
bprestore -S master_server -D backup_host -C client -R rename_file -t 44 -L progress log -f listfile | filenames
Where,
-S master_server
Specifies the name of the NetBackup master server.
-D backup host
Specifies the name of the backup host.
-C client
Specifies a configuration server as a source to use for finding backups or archives from which to restore files. This name must be as it appears in the NetBackup catalog.
-f listfile
Specifies a file (listfile) that contains a list of files to be restored and can be used instead of the file names option (filenames). In listfile, list each file path must be on a separate line.
-L progress_log
Specifies the name of whitelisted file path in which to write progress information.
-t 44
Specifies BigData as the policy type.
-R rename_file
Specifies the name of a file with name changes for alternate-path restores.
For example:
```
bprestore.exe -S master_server_01 -D backup_host_01 -C configuration_server_01 -t 44 -L "<install_dir>\logs\restore.log" -R "<install_dir>\renam_file_path\restore.chg" -f listfile
```

Sample rename files

Convert unmanaged disk to managed disk

change
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
headsrg4disks2.blob.vtasazs1.vxi.ver.com/vhds/sr-VM02-UMD20200826032144.vhd
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
ManagedDisks:Standard_LRS/Heads-RestoreRG20/osdisk1

Convert unmanaged disk VM to managed disk VM to the same RG

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/VmName=sr-VM02-UMD 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/VmName=sr-VM02-UMD-2md2

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD
/Metadata/UseManagedDisk=No
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/UseManagedDisk=Yes

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
headsuprg4disks2.blob.vtasazs1.vxi.ver.com/vhds/
sr-VM02-UMD20200826032144.vhd
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
ManagedDisks:Standard_LRS/HEADS-SUB3-SR/osdisk1

Convert unmanaged disk VM to a managed disk VM with a different subscription

change
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/Vnet=Heads-sub3-sr-vnet 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/Vnet=Heads-RestoreRG20-vnet

change
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/VmName=sr-VM02-UMD 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/VmName=sr-VM02-UMD-2md2

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/UseManagedDisk=No 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/UseManagedDisk=Yes

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/SubId=609c4f4d-5de7-4343-801b-6a3ac2364976 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/SubId=3f6a2463-d473-4639-a1d0-f762c4e0371a

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/Size=Standard_DS1_v2 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/Size=Standard_DS2_v2

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/RgName=Heads-sub3-sr 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/RgName=Heads-RestoreRG20

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/Nsg=sr-VM02-UMD-nsg 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/Nsg=HeadsUp-RestoreRG20-nsg

change 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/BootDiagnostics=headsuprg4diag398 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
Metadata/BootDiagnostics=headsupsta

change /609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
headsuprg4disks2.blob.vtasazs1.vxi.ver.com/vhds/
sr-VM02-UMD20200826032144.vhd 
to 
/609c4f4d-5de7-4343-801b-6a3ac2364976/Heads-sub3-sr/sr-VM02-UMD/
ManagedDisks:Standard_LRS/HeadsUp-RestoreRG20/osdisk1

Note:

Ensure that you have whitelisted all the file paths such as <rename_file_path>, <progress_log_path> that are not included as a part of NetBackup install path.

Using the bprestore command to restore Microsoft Azure VM with modified metadata to an alternate location

Feedback

Feedback