Veritas NetBackup™ for Microsoft Azure Stack Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (9.0.0.1, 9.0)
  1. Introduction
    1.  
      Protecting Microsoft Azure Stack VMs using NetBackup
    2.  
      Backing up Microsoft Azure Stack VMs
    3.  
      Restoring Microsoft Azure Stack VMs
    4.  
      Managed disk VM
    5.  
      NetBackup for Microsoft Azure Stack terminologies
  2. Pre-requisites for configuring the Microsoft Azure Stack plug-in for NetBackup
    1.  
      Operating system and platform compatibility
    2.  
      License for Microsoft Azure Stack plug-in for NetBackup
    3.  
      Settings for Backup host in IPV6 setup
    4.  
      Time Sync with Azure Stack
    5.  
      About deployment of NetBackup to protect Microsoft Azure Stack
  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 AAD authentication
    6.  
      Adding Microsoft Azure Stack credentials in NetBackup
    7.  
      Creating a BigData policy for Microsoft Azure Stack using the NetBackup Policies utility
    8.  
      Stale Snapshot cleanup
  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 to different location
    7. Using the BAR interface to restore an Microsoft Azure Stack VM with modified metadata at a different location
      1.  
        Conversion of Unmanaged disk VM to Managed disk VM
      2.  
        Conversion of Unmanaged disk VM backed up using old plugin to Managed disk VM
    8.  
      Using the bprestore command to restore Microsoft Azure VM with modified metadata to an alternate location
    9.  
      Using the bprestore command to restore Microsoft Azure Stack VM with modified metadata to an alternate region
  5. Troubleshooting
    1.  
      About NetBackup for Microsoft Azure debug logging
    2.  
      Known limitations for Microsoft Azure protection using NetBackup
    3.  
      Backup fails with error 6662
    4.  
      Backup fails with error 6661
    5.  
      Backup fails with error 6646
    6.  
      Backup fails with error 6629
    7.  
      Backup fails with error 6626
    8.  
      Backup fails with error 6630
    9.  
      Restore fails with error 2850
    10.  
      Backup fails with error 1
    11.  
      Adding Azure Stack credentials to NetBackup fails with error 9101
    12.  
      Adding Azure Stack credentials to NetBackup fails with error 7610

Adding Microsoft Azure Stack credentials in NetBackup

To establish a seamless communication between Microsoft Azure Stack clusters and NetBackup for successful backup and restore operations, you must add and update Microsoft Azure Stack credentials to the NetBackup master server.

Use the tpconfig command to add credentials in NetBackup master server.

For more information about the tpconfig command, see the NetBackup Commands Reference Guide.

To add credentials in NetBackup

  1. Run tpconfig command from the following directory paths:

    On UNIX systems, /usr/openv/volmgr/bin/

  2. Run the following command by providing appropriate values for each parameter to add Microsoft Azure Stack credentials:

    tpconfig -add -application_server_user_id user_ID -application_type application_type -application_server application_server_name -password password_of_the_nbu_azst_user -application_server_conf "/usr/<file_path>/azurestack.creds"

    • For AAD, NetBackup uses clientID and clientSecret, so enter the value for -application_server_user_id as dummy and -password as dummy.

    Note:

    The user you want to add must have co-owner permissions to the subscription you want to protect.

    For example,

    tpconfig -add -application_server_user_id example_user_ID -application_type azurestack -application_server application_server_name -password password_of_the_nbu_azst_user -application_server_conf "/usr/openv/var/global/azurestack.creds"

    Here, the numeric value 8 can also be specified for the -application_type parameter that corresponds to Microsoft Azure Stack .

  3. Run the tpconfig -dappservers command to verify if the NetBackup master server has the Azure credentials added.

    For example, here is a sample output:

    Application Server Host Name:        management.local.azurestack.external
Application Server Type:             azurestack
Required Port:                       0
User of Application Host:            root
  4. After you use tpconfig to add the credentials, you can delete the credentials file from the location that you have used in the tpconfig -add command..
  5. Run the following command to update or delete the tpconfig credentials:

    • Delete

      tpconfig -delete -application_server_user_id user_ID -application_type application_type -application_server application_server_name -password password_of_the_nbu_azst_user -application_server_conf "/usr/<file_path>/azurestack.creds"

    • Update

      To change the attributes or options in the credentials file, update the credentials and then use the tpconfig -update command.

      tpconfig -update -application_server_user_id user_ID -application_type application_type -application_server application_server_name -password password_of_the_nbu_azst_user -application_server_conf "/usr/<file_path>/azurestack.creds"