NetBackup™ Marketplace Deployment on AWS

Last Published:
Product(s): NetBackup & Alta Data Protection (10.2)
  1. NetBackup marketplace deployment on AWS
    1.  
      About Veritas NetBackup Marketplace Deployment on AWS
    2.  
      Before you begin the deployment
    3.  
      Network configuration
  2. Deploying NetBackup on AWS Cloud using the marketplace offer
    1.  
      Deploying NetBackup on AWS Cloud using the marketplace offer
  3. Deployment options (Delivery methods) for NetBackup on AWS cloud
    1.  
      Deployment options (Delivery methods) for NetBackup on AWS cloud
    2.  
      Option 1: Primary server only
    3.  
      Option 2: Media server only
    4.  
      Option 3: Primary and Media servers
    5. Option 4: Snapshot Manager server only
      1. Prerequisites for using the Snapshot Manager template
        1.  
          Configuring AWS permissions for Snapshot Manager
      2.  
        Resources created by the Snapshot Manager template
      3.  
        Snapshot Manager EC2 instance configuration details
      4.  
        Instance failures and Auto Scaling Group behavior
    6.  
      Option 5: Primary, Media, and Snapshot Manager servers
    7.  
      Option 6: Cloud Recovery server only
    8.  
      Option 7: Malware Scanner Only
  4. NetBackup configuration parameters
    1.  
      NetBackup configuration parameters
    2.  
      Instance configuration parameters
    3.  
      VPC and Subnet details for deployment in existing VPC
    4.  
      VPC and Subnet configuration for deployment in new VPC
    5. NetBackup installation parameters for the primary server
      1.  
        IAM role required for the primary server
    6.  
      NetBackup installation parameters for Media server
    7. NetBackup installation parameters for Snapshot Manager Server
      1.  
        IAM role required for Snapshot Manager instance
      2.  
        AWS endpoints used by Snapshot Manager
    8. NetBackup installation parameters for Cloud Recovery Server
      1.  
        IAM role required for Cloud Recovery Server
  5. Encryption enabled NetBackup primary server
    1.  
      Additional steps on CRS if encryption is enabled NetBackup primary server
  6. Accessing the NetBackup servers
    1.  
      How to access the NetBackup servers
  7. Upgrade NetBackup Snapshot Manager from AWS Marketplace
    1.  
      Upgrade NetBackup Snapshot Manager from AWS Marketplace
    2.  
      Perform the following steps to upgrade a Snapshot Manager deployment using a new AWS CloudFormation stack
  8. Troubleshooting section
    1.  
      Troubleshooting
    2.  
      Deployment Logs

Upgrade NetBackup Snapshot Manager from AWS Marketplace

The upgrade process is similar to when you are deploying a new instance using the Snapshot Manager CFT. Upgrading a Snapshot Manager CloudFormation stack difference is in some of the parameters where you are required to specify the values used in the existing Snapshot Manager deployment.

Prerequisites for the upgrade:

Perform the following steps before you proceed with the upgrade:

  1. Gather the following details about the existing Snapshot Manager instance; these are required later during the actual upgrade:

    • Snapshot Manager metadata volume ID.

      Perform the following steps to get the volume ID

      • In the AWS Console, from the menu on the left, click Services, and then from under Management & Governance, click CloudFormation

      • From the list of stacks, click on the Snapshot Manager stack and then click the Resources tab.

      • From the list of resources displayed, locate a volume of type of AWS::EC2::Volume and Logical ID as NewVolume. This is the volume that contains the Snapshot Manager metadata.

      • Copy the entry that appears in the Physical ID column. The entry is of the format vol-123456abc789 and it represents the volume ID.

    • Snapshot Manager metadata disk snapshot ID.

      Using the Snapshot Manager metadata volume ID that you noted earlier, perform the following steps to find out the metadata disk's snapshot ID:

      • In the AWS Console, from the menu on the left, click Services, and then from under Compute, click EC2.

      • From the EC2 Dashboard navigation menu on the left, under Elastic Block Store, click Snapshots.

      • Search for the snapshot ID using the Snapshot Manager metadata volume ID as the search parameter.

      • Copy the snapshot ID listed under the Snapshot ID column

    • AWS IAM role that is attached to the Snapshot Manager configuration.

    • AWS Elastic IP that is associated with the Snapshot Manager instance.

    • Snapshot Manager administrator username and password.

    • AWS SNS Topic ARN that is created for the existing Snapshot Manager stack. If required, you can also use another SNS topic ARN altogether.

  2. Verify that there are no protection policy snapshot or other operations in progress.
  3. Stop Snapshot Manager gracefully. Log on to the Snapshot Manager instance and then run the following command:

    # sudo docker run --rm -it -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:current_version stop

    The Snapshot Manager containers are stopped one by one. Messages similar to the following appear on the command line:

    Stopping the services

    Stopping container: flexsnap-agent.e425d969dd4 ...done

    Stopping container: flexsnap-agent.4704fd318322 ...done

    Stopping container: flexsnap-fluentd ...done

    Stopping container: flexsnap-mongodb ...done

    Stopping container: flexsnap-rabbitmq ...done

    Wait for all the Snapshot Manager containers to be stopped.

  4. Unmount the Snapshot Manager file system on the instance and then detach the Snapshot Manager metadata volume mounted at /cloudpoint. Type the following command on the instance:

    # umount /cloudpoint

  5. Disassociate the AWS Elastic IP that is assigned to the existing Snapshot Manager instance. From the AWS console, click on the EC2 Service and then from under Network and Security, select Elastic IPs. Select the Elastic IP address assigned to the instance and then click Actions > Disassociate address and then confirm the action. You will associate the same IP address with the newer instance later during the upgrade.