Veritas NetBackup for Microsoft Azure Stack Administrator's Guide

Last Published:
Product(s): NetBackup (8.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

Backing up Microsoft Azure Stack VMs

The following diagram provides an overview of the backup flow:

Figure: Backup flow

Backup flow

As illustrated in the diagram:

  1. A scheduled backup job is triggered from the master server.

  2. Backup job for Microsoft Azure Stack is a compound job. When the backup job is triggered, first a discovery job runs.

  3. During discovery, the first backup host connects with the Azure Resource Manager (ARM) Endpoint and performs a discovery to get details of VMs and their associated metadata that needs to be backed up.

  4. A workload discovery file is created on the backup host. The workload discovery file contains the details of the data that needs to be backed up from the different VMs.

  5. The backup host uses the workload discovery file get the details of data that it will backup. Individual workload discovery files are created for each backup host.

  6. Individual backup jobs are executed for each backup host. As specified in the workload distribution files, data is backed up.

  7. Data blocks are streamed simultaneously from different VMs to multiple backup hosts. The number of parallel streams is the same as the number of backup hosts.

The compound backup job is not completed until all the child jobs are completed.