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

Configuring the Microsoft Azure plug-in using the azurestack.conf configuration file

NetBackup master server uses the azurestack.conf file to save the configuration settings for communication with Microsoft Azure Stack.

You must create the azurestack.conf file in the /usr/openv/var/global directory.

Configuration definitions must be in the format of "attribute = value"; the single space before and after the '=' is required.

The options and values are case-sensitive.

Note:

You must not provide a blank value for any of the parameters, or the backup job fails.

Here is a sample of the azurestack.conf file:

VM_STATE = Running
FETCH_STORAGE_KEYS = false
CA_FILE_PATH = //directory_path_system_CA_certificate/certificate_name.crt
VM_SNAPSHOT_IN_DISCOVERY = true
NO_OF_BACKUP_STREAMS_PER_NODE = 1
ENABLE_SNAPSHOT_CLEANUP = 0
SNAPSHOT_CLEANUP_MIN = 1440
SNAPSHOT_FETCH_RETRY_COUNT = 60
ASYNC_SNAPSHOT_SUPPORT = true
SET_PUBLIC_IP_DURING_RESTORE = false
STAGING_STORAGE_ACCOUNTS = headsuptsta, restorestadisks, stafordiskstorages
  • The possible values for VM_STATE are Running, Deallocated, or Stopped.

  • The value for SNAPSHOT_FETCH_RETRY_COUNT specifies the maximum retries that can happen if a VM snapshot process fails. The value cannot exceed 3.

  • The value for FETCH_STORAGE_KEYS specifies whether the storage account with access key is required in the Azure Stack credentials file. The value can be either true or false. If the value is true, then you do not specify the storage account with access keys in the credential file. The default value is true.

  • The value for CA_FILE_PATH is the directory path of the system CA certificate and the certificate name. For example, /etc/pki/tls/certs/ca-bundle.crt. This directory path is the default path for all system CA certificates.

  • The value for VM_SNAPSHOT_IN_DISCOVERY defines whether VM disk snapshots are created for all disks that are attached to the VMs that are specified in the backup selection in the backup policy. The default value is false, specifying that snapshots of all disks that are attached to a single VM are created at a time during the backup job.

  • The value for NO_OF_BACKUP_STREAMS_PER_NODE specifies the maximum number of backup streams per backup host. The default value is 1. You can define the value up to 8.

  • The value for ENABLE_SNAPSHOT_CLEANUP specifies when to clean up stale snapshots. You can use the following values:

    • 0

      Do not delete the stale snapshots. This is the default value.

    • 1

      Delete the stale snapshots after the backup job completes.

    • 2

      Delete the stale snapshots as part of the next discovery job.

  • The value for SNAPSHOT_CLEANUP_MIN specifies the time in minutes after which the snapshot is deleted. The default value is 1440 minutes (24 hours). The ideal value is the time difference in minutes between two backup job.

  • The value for SNAPSHOT_FETCH_RETRY_COUNT specifies the retry count for the plug-in to check for the snapshot in a given storage container. The default value is 60 and the values can be between 60 and 120.

  • The value for ASYNC_SNAPSHOT_SUPPORT specifies that unmanaged disk snapshots are taken using the async REST API. The default value is true. Set the value to false to disable unmanaged disk snapshots using the async REST API.

  • The value for SET_PUBLIC_IP_DURING_RESTORE specifies whether to use a public IP address during the VM restore. The default value is true that specifies that the VM is restored with a public IP address. Set the value as false, to restore the VM with a private IP address.

  • The value for STAGING_STORAGE_ACCOUNTS is a comma separated list of storage account names that are already available on Azure Stack and the value is required for only managed disks VM restore or recovery. You can specify one or many storage accounts names for this key. Storage account name is required for restoring VHD blobs for the managed disks conversion operation. As per the target subscription location that is the selected as restore location, Netbackup Azure Stack plug-in automatically picks only one storage account from the list that is provided for this key. This is a one-time activity where you can specify all storage accounts needed for all restore jobs as per the target location selected for each restore job.

Note:

Do not add VM_STATE in the azurestack.conf file if you want to take a backup if all VMs.