Veritas NetBackup for Microsoft Azure Stack Administrator's Guide

Last Published:
Product(s): NetBackup (8.1.2)
  1. Introduction
    1.  
      Protecting Microsoft Azure Stack VMs using NetBackup
    2.  
      Backing up Microsoft Azure Stack VMs
    3.  
      Restoring Microsoft Azure Stack VMs
    4.  
      NetBackup for Microsoft Azure Stack terminologies
  2. Installing and deploying Microsoft Azure Stack plug-in for NetBackup
    1.  
      About installing and deploying the Microsoft Azure plug-in
    2.  
      Pre-requisites for installing the Microsoft Azure plug-in
    3.  
      Operating system and platform compatibility
    4.  
      License for Microsoft Azure Stack plug-in for NetBackup
    5.  
      Downloading the plug-in
    6.  
      About deployment of NetBackup to protect Microsoft Azure Stack
    7.  
      Installing the Microsoft Azure Stack plug-in
    8.  
      Installing Microsoft Azure Stack plug-in on NetBackup Appliance
  3. Configuring NetBackup and Microsoft Azure Stack
    1.  
      Overview of configuring NetBackup and Microsoft Azure Stack
    2. Managing backup hosts
      1.  
        Whitelisting a backup host on NetBackup master server
    3.  
      Adding a Microsoft Azure Stack custom role to provide access permissions to NetBackup administrator
    4. Configuring the Microsoft Azure plug-in using the azurestack.conf configuration file
      1.  
        Whitelisting the configuration file path on NetBackup master server
    5. Creating a file that contains Microsoft Azure Stack credentials
      1.  
        Configuring proxy settings for communication with Microsoft Azure Stack
    6.  
      Adding Microsoft Azure Stack credentials in NetBackup
    7.  
      Creating a BigData policy for Microsoft Azure Stack using the NetBackup Policies utility
  4. Performing backups and restores of Microsoft Azure Stack
    1.  
      About backing up Microsoft Azure virtual machines
    2.  
      About restoring Microsoft Azure Stack virtual machines
    3. About the restore scenarios for Microsoft Azure Stack VMs from the BAR interface
      1.  
        Considerations for Microsoft Azure Stack VM restore and recovery
    4.  
      Using the BAR interface to restore an Microsoft Azure Stack VM at the same location
    5.  
      Using the bprestore command to restore Microsoft Azure Stack VM at the same location
    6.  
      Using the BAR interface to restore an Microsoft Azure Stack VM with modified metadata at an alternate location
    7.  
      Using the bprestore command to restore Microsoft Azure VM with modified metadata and an alternate location
  5. Troubleshooting
    1.  
      About NetBackup for Microsoft Azure debug logging
    2.  
      Backup fails with error 6662
    3.  
      Backup fails with error 6661
    4.  
      Backup fails with error 6646
    5.  
      Backup fails with error 6629
    6.  
      Backup fails with error 6626
    7.  
      Backup fails with error 6630
    8.  
      Restore fails with error 2850
    9.  
      Backup fails with error 1
    10.  
      Adding Azure Stack credentials to NetBackup fails with error 9101
    11.  
      Adding Azure Stack credentials to NetBackup fails with error 7610

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

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

  1. Modify the values for rename_file and listfile as follows:

    Parameter

    Value

    rename_file

    For example, to update the VmName metadata, add:

    change

    /21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/VmName=OldVmName

    to

    /21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/VmName=NewVmName

    To change the power state of the VM, add:

    change

    /21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/PowerState=running

    to

    /21c71fdf-3ee5-4b57-8c51-18ebe7032237/SKRG/MSvm15/Metadata/PowerState=deallocate

    The 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

  2. 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 "/subscription ID/resource group/VmName"

    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.

    "/subscription ID/resource group/VmName"

    Specifies the Microsoft Azure Stack VM that you want to restore with modified metadata or at a different location.

    Note:

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

    For example, to change the restore location of a VM, you can run the following command:

    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" "/21c71fdf-3ee5-4b57-8c51-18ebe7032237/skrg1/bkvm15"

    Here, /21c71fdf-3ee5-4b57-8c51-18ebe7032237/skrg1/bkvm15 stands for subscription ID/resource group/VmName.