NetBackup™ Snapshot Manager Install and Upgrade Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.1)
  1. Introduction
    1.  
      About the deployment approach
    2.  
      Deciding where to run Snapshot Manager
    3.  
      About deploying Snapshot Manager in the cloud
  2. Section I. NetBackup Snapshot Manager installation and configuration
    1. Preparing for NetBackup Snapshot Manager installation
      1.  
        Meeting system requirements
      2.  
        Snapshot Manager host sizing recommendations
      3.  
        Snapshot Manager extension sizing recommendations
      4.  
        Creating an instance or preparing the host to install Snapshot Manager
      5.  
        Installing container platform (Docker, Podman)
      6.  
        Creating and mounting a volume to store Snapshot Manager data
      7.  
        Verifying that specific ports are open on the instance or physical host
      8.  
        Preparing Snapshot Manager for backup from snapshot jobs
    2. Deploying NetBackup Snapshot Manager using container images
      1.  
        Before you begin installing Snapshot Manager
      2.  
        Installing Snapshot Manager in the Docker/Podman environment
      3.  
        Verifying that Snapshot Manager is installed successfully
      4.  
        Restarting Snapshot Manager
    3. Deploying NetBackup Snapshot Manager extensions
      1.  
        Before you begin installing Snapshot Manager extensions
      2.  
        Downloading the Snapshot Manager extension
      3. Installing the Snapshot Manager extension on a VM
        1.  
          Prerequisites to install the extension on VM
        2.  
          Installing the extension on a VM
      4. Installing the Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
        1.  
          Prerequisites to install the extension on a managed Kubernetes cluster in Azure
        2.  
          Installing the extension on Azure (AKS)
      5. Installing the Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
        1.  
          Prerequisites to install the extension on a managed Kubernetes cluster in AWS
        2. Installing the extension on AWS (EKS)
          1.  
            Install extension using the extension script
      6. Installing the Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
        1.  
          Prerequisites to install the extension on a managed Kubernetes cluster in GCP
        2.  
          Installing the extension on GCP (GKE)
      7.  
        Install extension using the Kustomize and CR YAMLs
      8.  
        Managing the extensions
    4. NetBackup Snapshot Manager cloud plug-ins
      1.  
        How to configure the Snapshot Manager cloud plug-ins?
      2. AWS plug-in configuration notes
        1.  
          Prerequisites for configuring the AWS plug-in
        2.  
          Configuring AWS permissions for Snapshot Manager
        3.  
          AWS permissions required by Snapshot Manager
        4.  
          Before you create a cross account configuration
      3. Google Cloud Platform plug-in configuration notes
        1.  
          Google Cloud Platform permissions required by Snapshot Manager
        2.  
          Configuring a GCP service account for Snapshot Manager
        3.  
          Preparing the GCP service account for plug-in configuration
      4. Microsoft Azure plug-in configuration notes
        1.  
          Configuring permissions on Microsoft Azure
        2.  
          About Azure snapshots
      5. Microsoft Azure Stack Hub plug-in configuration notes
        1.  
          Configuring permissions on Microsoft Azure Stack Hub
        2.  
          Configuring staging location for Azure Stack Hub VMs to restore from backup
    5. NetBackup Snapshot Manager application agents and plug-ins
      1.  
        About the installation and configuration process
      2. Installing and configuring Snapshot Manager agent
        1.  
          Downloading and installing the Snapshot Manager agent
        2. Linux-based agent
          1.  
            Preparing to install the Linux-based agent
          2.  
            Registering the Linux-based agent
        3. Windows-based agent
          1.  
            Preparing to install the Windows-based agent
          2.  
            Registering the Windows-based agent
      3. Configuring the Snapshot Manager application plug-in
        1.  
          Configuring an application plug-in
        2. Microsoft SQL plug-in
          1.  
            Microsoft SQL plug-in configuration requirements
          2.  
            Restore requirements and limitations for Microsoft SQL Server
          3.  
            Steps required before restoring SQL AG databases
          4.  
            Additional steps required after restoring SQL AG databases
          5. Additional steps required after a SQL Server instance snapshot restore
            1.  
              Steps required after a SQL Server host-level restore
            2.  
              Steps required after a SQL Server instance disk-level snapshot restore to new location
        3. Oracle plug-in
          1. Oracle plug-in configuration requirements
            1.  
              Optimizing your Oracle database data and metadata files
          2.  
            Restore requirements and limitations for Oracle
          3.  
            Additional steps required after an Oracle snapshot restore
      4. NetBackup protection plan
        1.  
          Creating a NetBackup protection plan for cloud assets
        2.  
          Subscribing cloud assets to a NetBackup protection plan
      5.  
        Configuring VSS to store shadow copies on the originating drive
      6.  
        Additional steps required after restoring an AWS RDS database instance
    6. Protecting assets with NetBackup Snapshot Manager's agentless feature
      1.  
        About the agentless feature
      2. Prerequisites for the agentless configuration
        1.  
          Configuring SMB for Windows (Optional)
        2.  
          Configuring WMI security for Windows (optional)
      3.  
        Configuring the agentless feature
      4.  
        Configuring the agentless feature after upgrading Snapshot Manager
    7. Volume Encryption in NetBackup Snapshot Manager
      1.  
        About volume encryption support in Snapshot Manager
      2.  
        Volume encryption for Azure
      3.  
        Volume encryption for GCP
      4.  
        Volume encryption for AWS
    8. NetBackup Snapshot Manager security
      1.  
        Configuring security for Azure Stack
      2.  
        Configuring the cloud connector for Azure Stack
      3.  
        CA configuration for Azure Stack
      4.  
        Securing the connection to Snapshot Manager
  3. Section II. NetBackup Snapshot Manager maintenance
    1. NetBackup Snapshot Manager logging
      1.  
        About Snapshot Manager logging mechanism
      2. How Fluentd-based Snapshot Manager logging works
        1.  
          About the Snapshot Manager fluentd configuration file
        2.  
          Modifying the fluentd configuration file
      3.  
        Snapshot Manager logs
      4.  
        Agentless logs
      5.  
        Troubleshooting Snapshot Manager logging
    2. Upgrading NetBackup Snapshot Manager
      1.  
        About Snapshot Manager upgrades
      2.  
        Supported upgrade path
      3.  
        Upgrade scenarios
      4.  
        Preparing to upgrade Snapshot Manager
      5.  
        Upgrading Snapshot Manager
      6.  
        Upgrading Snapshot Manager using patch or hotfix
      7. Migrating and upgrading Snapshot Manager
        1.  
          Before you begin migrating Snapshot Manager
        2.  
          Migrate and upgrade Snapshot Manager on RHEL 8.6 or 8.4
      8. Post-upgrade tasks
        1.  
          Upgrading Snapshot Manager extensions
      9.  
        Post-migration tasks
    3. Uninstalling NetBackup Snapshot Manager
      1.  
        Preparing to uninstall Snapshot Manager
      2.  
        Backing up Snapshot Manager
      3.  
        Unconfiguring Snapshot Manager plug-ins
      4.  
        Unconfiguring Snapshot Manager agents
      5.  
        Removing the Snapshot Manager agents
      6.  
        Removing Snapshot Manager from a standalone Docker host environment
      7.  
        Removing Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
      8.  
        Restoring Snapshot Manager
    4. Troubleshooting NetBackup Snapshot Manager
      1.  
        Troubleshooting Snapshot Manager
      2.  
        SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the Snapshot Manager host
      3.  
        Disk-level snapshot restore fails if the original disk is detached from the instance
      4.  
        Discovery is not working even after assigning system managed identity to the control node pool
      5.  
        Performance issue with GCP backup from snapshot
      6.  
        Post migration on host agents fail with an error message
      7.  
        File restore job fails with an error message

Steps required after a SQL Server instance disk-level snapshot restore to new location

Perform these steps after you have restored a disk-level SQL Server instance snapshot from the NetBackup UI. These steps are required only if the snapshot is restored to a new location. New location refers to a new host that is different from the one where the SQL instance is running.

Note:

These steps are applicable only in case of a SQL Server instance snapshot restore to a new location. These are not applicable for a SQL Server database snapshot restore.

Clear the read-only mode of the new disk attached to the host

Perform the following steps

  1. Connect to the new Windows host where the SQL Server instance is running.

    Ensure that you use an account that has administrator privileges on the host.

  2. Open a command prompt window. If Windows UAC is enabled on the host, open the command prompt in the Run as administrator mode.
  3. Start the diskpart utility using the following command:

    diskpart

  4. View the list of disks on the new host using the following command:

    list disk

    Identify the new disk that is attached due to the snapshot restore operation and make a note of the disk number. You will use it in the next step.

  5. Select the desired disk using the following command:

    select disk <disknumber>

    Here, <disknumber> represents the disk that you noted in the earlier step.

  6. View the attributes of the selected disk using the following command:

    attributes disk

    The output displays a list of attributes for the disk. One of the attributes is read-only, which we will modify in the next step.

  7. Modify the read-only attribute for the selected disk using the following command:

    attributes disk clear readonly

    This command changes the disk to read-write mode.

  8. Bring the disk online.

    From the Windows Server Manager console, navigate to Files and Storage Devices > Disks and then right click on the newly attached disk and select Bring online.

  9. Assign drive letters to the volumes on the disk that you brought online in the earlier step. Drive letters are required to view the shadow copies associated with each volume on the disk.

    Go back to the command prompt window and perform the following steps:

    • View the list of volumes on the new host using the following command:

      list volume

      From the list of volumes displayed, identify the volume for which you want to assign, modify, or remove a drive letter.

    • Select the desired volume using the following command:

      select volume <volnumber>

      Here, <volnumber> represents the volume that you noted in the earlier step.

    • Assign a drive letter to the selected volume using the following command:

      assign letter=<driveletter>

      Here, <driveletter> is the drive letter that you wish to assign to the volume. Ensure that the specified drive letter is not already in use by another volume.

    • Repeat these steps to assign a drive letter to all the SQL Server volumes on the disk.

  10. Quit the diskpart utility using the following command:

    exit

    Do not close the command prompt yet; you can use the same window to perform the remaining steps described in the next section.

Revert shadow copy using the Microsoft DiskShadow utility

Perform the following steps

  1. From the same command window used earlier, start the diskshadow command interpreter in the interactive mode using the following command:

    diskshadow

  2. View the list of all the shadow copies that exist on the new host. Type the following command:

    list shadows all

    Identify the shadow copy that you want to use for the revert operation and make a note of the shadow copy ID. You will use the shadow ID in the next step.

  3. Revert the volume to the desired shadow copy using the following command:

    revert <shadowcopyID>

    Here, <shadowcopyID> is the shadow copy ID that you noted in the earlier step.

  4. Exit the DiskShadow utility using the following command:

    exit

Attach .mdf and .ldf files to the instance database

Perform the following steps:

  1. Ensure that the disk-level snapshot restore operation has completed successfully and a new disk is created and mounted on the application host.
  2. Log on to Microsoft SQL Server Management Studio as a database administrator.
  3. From the Object Explorer, connect to an instance of the SQL Server Database Engine and then click to expand the instance view.
  4. In the expanded instance view, right-click Databases and then click Attach.
  5. In the Attach Databases dialog box, click Add and then in the Locate Database Files dialog box, select the disk drive that contains the database and then find and select all the .mdf and .ldf files associated with that database. Then click OK.

    The disk drive you selected should be the drive that was newly created by the disk-level snapshot restore operation.

  6. Wait for the requested operations to complete and then verify that the database is available and is successfully discovered by NetBackup.