Veritas NetBackup™ for Microsoft Azure Stack Administrator's Guide
- Introduction
- Pre-requisites for configuring the Microsoft Azure Stack plug-in for NetBackup
- Configuring NetBackup and Microsoft Azure Stack
- Overview of configuring NetBackup and Microsoft Azure Stack
- Managing backup hosts
- Adding a Microsoft Azure Stack custom role to provide access permissions to NetBackup administrator
- Configuring the Microsoft Azure plug-in using the azurestack.conf configuration file
- Creating a file that contains Microsoft Azure Stack credentials
- Adding Microsoft Azure Stack credentials in NetBackup
- Creating a BigData policy for Microsoft Azure Stack using the NetBackup Policies utility
- Stale Snapshot cleanup
- Performing backups and restores of Microsoft Azure Stack
- About backing up Microsoft Azure virtual machines
- About restoring Microsoft Azure Stack virtual machines
- About the restore scenarios for Microsoft Azure Stack VMs from the BAR interface
- Using the BAR interface to restore an Microsoft Azure Stack VM at the same location
- Using the bprestore command to restore Microsoft Azure Stack VM at the same location
- Using the BAR interface to restore an Microsoft Azure Stack VM to different location
- Using the BAR interface to restore an Microsoft Azure Stack VM with modified metadata at a different location
- Using the bprestore command to restore Microsoft Azure VM with modified metadata to an alternate location
- Using the bprestore command to restore Microsoft Azure Stack VM with modified metadata to an alternate region
- Troubleshooting
- About NetBackup for Microsoft Azure debug logging
- Known limitations for Microsoft Azure protection using NetBackup
- Backup fails with error 6662
- Backup fails with error 6661
- Backup fails with error 6646
- Backup fails with error 6629
- Backup fails with error 6626
- Backup fails with error 6630
- Restore fails with error 2850
- Backup fails with error 1
- Adding Azure Stack credentials to NetBackup fails with error 9101
- Adding Azure Stack credentials to NetBackup fails with error 7610
Using the bprestore command to restore Microsoft Azure Stack VM with modified metadata to an alternate region
NetBackup lets you restore Microsoft Azure Stack data to another resource group and modify the metadata. This type of restore method is also referred to as redirected restores.
To perform redirected restore for Microsoft Azure Stack
- Modify the values for rename_file and listfile as follows:
Parameter
Value
rename_file
Add ALT_APPLICATION_SERVER= entry to specify ARM endpoint of the alternate region
Too update the
VmNamemetadata, add:change
/21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/VmName=OldVmNameto
/21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/VmName=NewVmNameTo change the power state of the VM, add:
change
/21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/PowerState=runningto
/21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/PowerState=deallocateThe file paths must start with / (slash).
Add a new entry for all the metadata options that you want to modify.
Note:
For the VM size metadata, specify the modified value in the Microsoft Azure Stack recommended format. The new VM size must be part of your subscription.
For more information, refer to Virtual machine sizes supported in Azure Stack.
listfile
List of all the Microsoft Azure files to be restored
- To fetch the credentials information for the alternate Azure Stack:
Add a tpconfig entry for the new Azure Stack ARM end point.
Change the name of the generated encrypted file in /usr/openv/var/global to match the name of the source client encrypted credentials file.
For example, if
arm-end-point1.confis the encrypted source client file and arm-end-point2.conf is the encrypted alternate client file. Make a copy of arm-end-point1.conf to arm-end-point1.conf_org and then copy arm-end-point2.conf to arm-end-point1.conf before running the bprestore command. - List of files can be obtained by running the following bplist command:
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
listfilein the editor and remove the special characters at the end of the line. Remove all the paths ending with / that correspond 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 -X -s bktime -e bktime -L progress log -f listfile | filenames
Where,
-S master_serverSpecifies the name of the NetBackup master server.
-D backup_hostSpecifies the name of the backup host.
-C clientSpecifies 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 listfileSpecifies 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_logSpecifies the name of whitelisted file path in which to write progress information.
-t 44Specifies BigData as the policy type.
-R rename_fileSpecifies the name of a file with name changes for alternate-path restores.
ALT_APPLICATION_SERVER=management.vtsz2.vxi.vs.com
change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/BootDiagnostics=hupsta to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HeadsUp-RestoreRG20/skuvm1/Metadata/BootDiagnostics=stasub2testrgg change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/Nsg=HUp-RestoreRG20-nsg to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/Nsg=rs-md-21-nsg change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/RgName=HUp-RestoreRG20 to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/RgName=rshney-perf-set6 change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/ SubId=3f6a2463-d473-4639-a1d0-f762c4e0371a to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/ SubId=b326ed58-7537-4c81-b2ac-5b16d6a524b3 change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/VmName=skuvm1 to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/VmName=skuvm1-restore2 change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/Vnet=HUp-RestoreRG20-vnet to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/Metadata/Vnet=rshney-perf-set6-vnet change /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/HUpsta.blob.vtszs1.vxi.vs.com/vhds/ skuvm1-UMD-RESTORE-1599155872.vhd to /3f6a2463-d473-4639-a1d0-f762c4e0371a/HUp-RestoreRG20/skuvm1/stasub2testrgg.blob.vtszs2.vxi.veritas.com/ vhds/skuvm1-UMD-RESTORE-1599155872.vhd