Veritas Cloud Scale

Technology Deployment
Guide Using Terraform for
Microsoft Azure

Release 10.5
Veritas Cloud Scale Technology deployment guide
using Terraform for Azure cloud
Last updated: 2024-09-23

Legal Notice
Copyright © 2024 Veritas Technologies LLC. All rights reserved.

Veritas, the Veritas Logo, Veritas Alta, and NetBackup are trademarks or registered trademarks
of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may
be trademarks of their respective owners.

This product may contain third-party software for which Veritas is required to provide attribution
to the third party (“Third-party Programs”). Some of the Third-party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the Third-party Legal Notices document accompanying this
Veritas product or available at:

https://www.veritas.com/about/legal/license-agreements

The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Veritas Technologies LLC SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.

Veritas Technologies LLC

2625 Augustine Drive
Santa Clara, CA 95054
http://www.veritas.com

Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:

https://www.veritas.com/support

You can manage your Veritas account information at the following URL:

https://my.veritas.com

If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:

Worldwide (except Japan) [email protected]

Japan [email protected]

Documentation
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. The latest documentation is available on the Veritas
website:

https://sort.veritas.com/documents

Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:

[email protected]

You can also see documentation information or ask a question on the Veritas community site:

http://www.veritas.com/community/

Veritas Services and Operations Readiness Tools (SORT)

Veritas Services and Operations Readiness Tools (SORT) is a website that provides information
and tools to automate and simplify certain time-consuming administrative tasks. Depending
on the product, SORT helps you prepare for installations and upgrades, identify risks in your
datacenters, and improve operational efficiency. To see what services and tools SORT provides
for your product, see the data sheet:

https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
 Contents

Chapter 1 Introduction ........................................................................... 6

About this guide ............................................................................. 6

Required terminology ................................................................ 7
About Veritas Cloud Scale Technology on Azure cloud ........................... 7
About Terraform ............................................................................. 8

Chapter 2 Getting started steps for deployment .......................... 10

Steps for getting started with deployment .......................................... 10

Chapter 3 Prerequisites for setting up Azure environment

........................................................................................... 12

Before starting the deployment ........................................................ 12

Network configuration requirements ................................................. 13
Azure subscription permission requirements ...................................... 14

Chapter 4 Prerequisities for Terraform scripts .............................. 16

Terraform Management Server requirements ..................................... 16

Chapter 5 Deploying Veritas Cloud Scale Technology using

Terraform scripts .......................................................... 18
Creating and configuring Terraform Management Server ...................... 18
Installing the packages for Terraform Management Server .............. 19
About PreFlight checker (checklist) script .......................................... 22
Stages of deploying Terraform scripts on Azure .................................. 23
Parameters for base stage ...................................................... 23
Parameters for addons stage .................................................... 30
Parameters for deployment stage .............................................. 30
PaaS based PostgreSQL deployment (DBaaS) on Azure ................ 35
Installation instructions for deploying the Veritas Cloud Scale
Technology on Azure .............................................................. 35
Change the PostgreSQL database server password ...................... 37
 Contents 5

Chapter 6 Accessing the Veritas Cloud Scale environment

........................................................................................... 41

Accessing the Veritas Cloud Scale Technology environment after

deployment ........................................................................... 41

Chapter 7 Troubleshooting and cleanup environment steps

........................................................................................... 44

Troubleshooting issues .................................................................. 44

Cleanup steps ............................................................................. 46
 Chapter 1
Introduction
This chapter includes the following topics:

■ About this guide

■ About Veritas Cloud Scale Technology on Azure cloud

■ About Terraform

About this guide

This document provides the instructions for deploying Veritas Cloud Scale
Technology components in Azure Kubernetes Services (AKS) on Azure using
Terraform. The intended audience for this document includes backup administrators,
cloud administrators, architects, and system administrators. The purpose of this
guide is to help understand the deployment of Veritas Cloud Scale Technology
using Terraform scripts.
Veritas Cloud Scale Technology is a cloud native build your own form factor that
uses cloud infrastructure components built on Kubernetes technology. To deploy
this product, you will need the following expertise on your team in order to install
and manage this environment:
■ Kubernetes (also known as K8s) is an open-source system for automating
deployment, scaling, and management of containerized applications.
■ Cloud native based deployments is a software approach of building, deploying,
and managing modern applications in cloud computing environments. Knowledge
about cloud networking, cloud commutating, and cloud storage are required to
store, access, maintain, and manage data through a cloud computing provider.
Veritas also supports traditional virtual machine (VM) based IaaS deployments for
Alta Data Protection. If you need further assistance on determining the best fit for
your environment or have any additional questions, reach out to your local Sales
team.
 Introduction 7
About Veritas Cloud Scale Technology on Azure cloud

Required terminology
The table describes the important terms used in this guide for deploying Veritas
Cloud Scale Technology on Azure.

Table 1-1 Important terms

Term Description

Azure Virtual Azure Virtual Network provides secure, private networking for your
Network Azure and on-premises resources.

DNS DNS translates domain names to IP addresses so browsers can load

internet resources.

ACR Azure Container Registry allows you to build, store, and manage
container images and artifacts in a private registry for all types of
container deployments.

AKS cluster Azure Kubernetes Service (AKS) offers the quickest way to start
developing and deploying cloud-native apps in Azure, datacenters,
or at the edge with built-in code-to-cloud pipelines and guardrails.

About Veritas Cloud Scale Technology on Azure

cloud
Veritas Cloud Scale Technology redefines data management for the next decade.
Cloud Scale Technology’s service elasticity and modern web-scale technologies
enable NetBackup to operate cloud-natively within a cloud yet deliver a consistent
experience across multiple clouds to improve cloud return on investment (ROI),
service resiliency, and security while reducing operational complexity and costs.
The solution facilitates an orchestrated deployment of the following components
on Kubernetes clusters:
■ NetBackup: You can deploy NetBackup on the Kubernetes clusters of AWs or
Azure for scaling the capacity of the NetBackup host to server large number of
requests concurrently running on the NetBackup primary server at its peak
performance capacity.
■ MSDP Scaleout: In addition to the NetBackup components namely primary and
media servers, the deduplication engine (1 to 16) replicas may also be deployed.
■ NetBackup Snapshot Manager: You can deploy NetBackup Snapshot Manager
with autoscaling capabilities for data movement.
 Introduction 8
About Terraform

Veritas Cloud Scale Technology is a new generation of the proven NetBackup

architecture. This technology is designed to operate cloud-natively and use
technologies such as containers and microservices along with web-scale IT
techniques such as service elasticity and hyper-automation. Some of the benefits
of this technology are:
■ A containerized, Kubernetes-based deployment model that can be used to create
a new cloud-native NetBackup environment or complement an existing one that
spans the data center and the cloud.
■ A microservices-based architecture that provides the portability to work within
multiple clouds and resiliency for service availability.
■ Elastic services which autonomously grow and shrink as needed to optimize
cloud resource usage and costs.
■ API-driven microservices that enable cross-domain workflow automation.
■ Simplified deployment directly from public cloud marketplaces and native tools.

About Terraform
Terraform is an open source "Infrastructure as Code" tool created by HashiCorp.
It manages resources (such as cloud infrastructure, network appliances, Software
as a Service, and Platform as a Service) with the providers.
Using Terraform, you can create and manage resources on cloud platforms and
other services through their application programming interfaces (APIs). Service
providers enable Terraform to work virtually with any platform or service with an
accessible API.
Here are some advantages of Terraform:
■ Manage any infrastructure: Terraform uses immutable approach which reduces
the complexity of upgrading or modifying your services and infrastructure.
■ Tracks infrastructure status: A state file keeps track of your environment and
suggests changes to your infrastructure to match the configuration.
■ Standardize configurations: Terraform supports reusable configuration
components called modules that define configurable collections of infrastructure.
Terraform supports several cloud infrastructure providers such as Microsoft Azure,
Amazon Web Services (AWS), Cloudflare, IBM Cloud, Google Cloud Platform, and
Oracle Cloud Infrastructure.
The table describes you about the high-level steps involved in the deployment.
 Introduction 9
About Terraform

Table 1-2 Getting started using Terraform scripts for deploying Veritas
Cloud Scale Technology on Azure

Steps

1. Ensure that the prerequisites for creating the Terraform Management Server are met.

2. Configure the Terraform Management Server.

3. Authentication with Azure

4. Execute the PreFlight checker script.

5a. Learn about the stages involved in the Terraform deployment.

5b. Installation instructions for deploying the Veritas Cloud Scale Technology.

6. Access Veritas Cloud Scale Technology UI after deployment.

 Chapter 2
Getting started steps for
deployment
This chapter includes the following topics:

■ Steps for getting started with deployment

Steps for getting started with deployment

The topic helps you to understand the initial configuration for deploying the Veritas
Cloud Scale Technology. The following table shows the steps involved in setting
up the configuration.

Table 2-1 Getting started using Terraform scripts for deploying Veritas
Cloud Scale Technology on Azure

Steps Description

1. Ensure the prerequisites for Ensure that the Terraform Management Server
creating Terraform Management prerequisites and networking requirements are met.
Server are met.
Refer See “Terraform Management Server
requirements” on page 16.

2. Configure Terraform Management Refer See “Creating and configuring Terraform

Server Management Server” on page 18.

Refer See “Installing the packages for Terraform

Management Server” on page 19.

3. Authentication with Azure User / role which you will be using for deployment
should have minimum permissions. Refer

See “Azure subscription permission requirements”

on page 14.
 Getting started steps for deployment 11
Steps for getting started with deployment

Table 2-1 Getting started using Terraform scripts for deploying Veritas
Cloud Scale Technology on Azure (continued)

Steps Description

4. Execute the PreFlight checker This checklist is executed to verify the environment
script. readiness before deploying theVeritas Cloud Scale
Technology. Refer to the section See “About PreFlight
checker (checklist) script” on page 22.

5a. Learn about the stages involved See “Stages of deploying Terraform scripts on Azure”
in the Terraform deployment on page 23.

5b. Installation instructions for See “Installation instructions for deploying the Veritas
deploying the Veritas Cloud Scale Cloud Scale Technology on Azure” on page 35.
Technology

6. Access Veritas Cloud Scale See “Accessing the Veritas Cloud Scale Technology
Technology UI after deployment environment after deployment” on page 41.
 Chapter 3
Prerequisites for setting up
Azure environment
This chapter includes the following topics:

■ Before starting the deployment

■ Network configuration requirements

■ Azure subscription permission requirements

Before starting the deployment

To set up the Veritas Cloud Scale Technology deployment on the Azure environment,
there are some prerequisites to be met.
■ Ensure that the See “Network configuration requirements” on page 13. are met.
■ Ensure that the See “Azure subscription permission requirements” on page 14.
are assigned to the user before starting the deployment.
 Prerequisites for setting up Azure environment 13
Network configuration requirements

Network configuration requirements

Figure 3-1 Network configuration for managing Terraform Management
Server in Azure

Ensure that the below networking requirements are met.

■ VNet and subnets must be created in Azure account before the Terraform scripts
are executed.
■ Required address spaces:
■ For cluster subnet: This subnet is required with /22 or /24 subnet address
space ( used for node pool).
■ Load balancer subnet: This subnet is required with - /26 address space
(This subnet needs to be empty with no virtual machines / devices installed).

■ Create DNS entries in the Private Hosted Zone:

■ Primary (1): primary.example.com (10.x.x.x)
■ MSDP (1): msdp.example.com(10.x.x.x)
■ Snapshot Manager (1): snapshotmanager.example.com(10.x.x.x)
 Prerequisites for setting up Azure environment 14
Azure subscription permission requirements

■ Outbound internet access is required from Terraform Management Server to

communicate with resources, services, and the servers.
■ While configuring the components or resources, avoid using prefixes like -
netbackup, primary or media. The installation may fail if these keywords are
used in the configuration.
■ Azure reserves the first four addresses and the last address, for a total of five
IP addresses within each subnet. Refer to the link for more details.

Azure subscription permission requirements

The permissions in Azure are required for the user to create clusters, deploy the
Veritas Cloud Scale Technology on the Azure cloud environment, also to support
backup and recovery operations. These are the minimum permission that will help
user to setup the whole environment required to deploy the Veritas Cloud Scale
Technology. There are two ways to assign these permission to the admin user
which is used in the deployment and you will have to choose any one method.
■ Use Azure subscription with contributor and user admin role.
■ Create a custom role with following permissions attached to the user which is
used for deploying the Veritas Cloud Scale Technology in Azure –

Microsoft.ContainerService/managedClusters/read
Microsoft.ContainerService/managedClusters/write
Microsoft.ContainerService/managedClusters/delete
Microsoft.ContainerService/managedClusters/start/action
Microsoft.ContainerService/managedClusters/stop/action
Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action
Microsoft.ContainerService/managedClusters/listClusterUserCredential/action
Microsoft.ContainerService/managedClusters/listClusterMonitoringUserCredential/action
Microsoft.ContainerService/managedClusters/privateEndpointConnectionsApproval/action

Microsoft.ContainerService/managedClusters/runCommand/action
Microsoft.ContainerService/managedClusters/agentPools/read
Microsoft.ContainerService/managedClusters/agentPools/write
Microsoft.ContainerService/managedClusters/agentPools/delete
Microsoft.ContainerService/managedClusters/resolvePrivateLinkServiceId/action
Microsoft.ContainerService/managedClusters/agentPools/upgradeNodeImageVersion/write
Microsoft.ContainerService/managedClusters/extensionaddons/read
Microsoft.ContainerService/managedClusters/extensionaddons/write
Microsoft.ContainerService/managedClusters/privateEndpointConnections/read
Microsoft.ContainerService/managedClusters/privateEndpointConnections/write
 Prerequisites for setting up Azure environment 15
Azure subscription permission requirements

Microsoft.ContainerService/managedClusters/privateEndpointConnections/delete

Microsoft.ContainerService/managedclustersnapshots/read
Microsoft.ContainerService/managedclustersnapshots/write
Microsoft.ContainerService/managedclustersnapshots/delete
Microsoft.Authorization/permissions/read
Microsoft.ContainerRegistry/registries/write
Microsoft.ContainerRegistry/registries/delete
Microsoft.ContainerRegistry/registries/read
Microsoft.ContainerRegistry/registries/listCredentials/action
Microsoft.ContainerRegistry/registries/privateEndpointConnections/read
Microsoft.ContainerRegistry/registries/privateEndpointConnections/delete
Microsoft.ContainerRegistry/registries/privateEndpointConnections/write
Microsoft.ContainerRegistry/registries/pull/read
Microsoft.ContainerRegistry/registries/push/write
Microsoft.Authorization/roleAssignments/read
Microsoft.Authorization/roleAssignments/write
Microsoft.Authorization/roleAssignments/delete
Microsoft.Authorization/roleDefinitions/read
Microsoft.Authorization/roleDefinitions/write
Microsoft.Authorization/roleDefinitions/delete
Microsoft.ManagedIdentity/userAssignedIdentities/assign/action
Microsoft.ManagedIdentity/userAssignedIdentities/delete
Microsoft.ManagedIdentity/userAssignedIdentities/read
Microsoft.ManagedIdentity/userAssignedIdentities/write
Microsoft.ManagedIdentity/userAssignedIdentities/listAssociatedResources/action
Microsoft.ManagedIdentity/identities/read
Microsoft.Network/privateDnsZones/write
Microsoft.Network/privateDnsZones/delete
Microsoft.Network/privateDnsZones/virtualNetworkLinks/write
Microsoft.Network/privateDnsZones/virtualNetworkLinks/delete
Microsoft.Network/privateLinkServices/privateEndpointConnections/write
Microsoft.Network/privateLinkServices/privateEndpointConnections/delete
Microsoft.Network/privateLinkServices/write
Microsoft.Network/privateLinkServices/delete
Microsoft.Network/privateEndpoints/privateDnsZoneGroups/write
Microsoft.Network/privateEndpoints/privateDnsZoneGroups/delete
Microsoft.Network/privateEndpoints/delete
Microsoft.Network/privateEndpoints/write
Microsoft.Network/*/read
 Chapter 4
Prerequisities for
Terraform scripts
This chapter includes the following topics:

■ Terraform Management Server requirements

Terraform Management Server requirements

Terraform Management Server (also known as jump host) is required to execute
the scripts. Ensure that the below server requirements are met before executing
the scripts.
■ Virtual machine with Linux operating system. The recommended configuration
for the virtual machine is:
■ Ubuntu / RHEL
■ 2 CPUs
■ 8 GB memory
■ > = 64 GB free disk space in /var folder. The space is required to load the
Docker images and copy the tar file on the /var folder.

■ The following packages are required to be installed on the Terraform

Management server. To install the below mentioned packages, refer to the
section See “Installing the packages for Terraform Management Server”
on page 19.
■ Terraform version >= 1.5.0 or later
■ Latest version of Docker
■ In case of RHEL operating system, use PODMAN.
 Prerequisities for Terraform scripts 17
Terraform Management Server requirements

■ kubectl (A command line tool for communicating with Kubernetes cluster's

control plane. Refer the Azure documentation for more details.
■ Helm package manager
■ Azure CLI version >= 2.9.xx or later
■ BASH version >= 5.0.17 or later
■ Linux utilities like GREP, AWK, tr, PING, ENVSUBST, TAR, JQ, SED, and
CUT
■ Ensure that you have enough space using the command: ~$ df -h

■ Outbound internet access is required to communicate with resources, services,

and the servers.
■ Copy the Veritas binary file bundle (NetBackup tar of Kubernetes.tar) file and
Terraform script bundle from the Veritas Download center and copy on the
Terraform Management Server which is also called as jump host. Unzip this file
to access the scripts and files for deployment.
 Chapter 5
Deploying Veritas Cloud
Scale Technology using
Terraform scripts
This chapter includes the following topics:

■ Creating and configuring Terraform Management Server

■ About PreFlight checker (checklist) script

■ Stages of deploying Terraform scripts on Azure

■ Installation instructions for deploying the Veritas Cloud Scale Technology on

Azure

Creating and configuring Terraform Management

Server
Terraform Management Server is a linux host which is required to execute terraform
scripts. To deploy the Veritas Cloud Scale Technology, creating and configuring
the Terraform Management Server is the first step.
The following steps describe how the Terraform Management Server is created
and deployed in AWS / Azure environment.
1. Deploy an Ubuntu / RHEL version 22 virtual machine. Choose the appropriate
instance type that matches these specifications:
■ 2 CPUs
■ 8 GB memory
 Deploying Veritas Cloud Scale Technology using Terraform scripts 19
Creating and configuring Terraform Management Server

■ >= 64 GB space on /var folder.

After the deployment is complete, note the IP address to connect.

2. Once the virtual machine is created, log in into the system using SSH client.
ssh -i example.pem [email protected]

3. Ensure you have min 30 GB free space in /var folder. Use the below command
to verify:
~$ df -h

4. If you are using non-root user, run the following command:

sudo gpasswd -a "non root user" docker

For example: sudo gpasswd -a <user> docker

Restart the docker using the command:sudo systemctl restart docker
5. Install the listed packages from the section Installing the packages for Terraform
Management Server.
6. Outbound internet access is required from Terraform Management Server to
communicate with resources, services, and the servers.

Installing the packages for Terraform Management Server

This step is required to setup the Terraform Management Server as jump host. A
jump host is an intermediary server which can be accessed beyond a firewall. It
provides information needed to communicate with the target device. You can connect
to the jump host a private key or username and password.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 20
Creating and configuring Terraform Management Server

Installing packages on Terraform Management Server

1 Install Docker
Follow these steps to allow non-root user to access and leverage Docker.
a. Create and APT keyring directory using commands:
mkdir /etc/apt/keyrings

chmod 755 /etc/apt/keyrings

b. Download the docker.gpg file and place in the keyring folder:

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg
--dearmor -o /etc/apt/keyrings/docker.gpg

c. Download the Docker repository. Ensure that the below command is to be

pasted as single shell. It only takes a second to run.
echo deb [arch=$(dpkg --print-architecture)
signed-by=/etc/apt/keyrings/docker.gpg]
https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable
| tee /etc/apt/sources.list.d/docker.list

d. Install the Docker files using the next two commands one by one.
apt update

2 apt install -y docker-ce docker-ce-cli containerd.io

docker-buildx-plugin docker-compose-plugin

e. Confirm the Docker is installed correctly.

docker run hello-world
 Deploying Veritas Cloud Scale Technology using Terraform scripts 21
Creating and configuring Terraform Management Server

3 Install Terraform package using root user

a. Download GPG key and place in same keyrings directory created during
Docker install (Step1a).
curl -sSL https://apt.releases.hashicorp.com/gpg | gpg --dearmor
-o /etc/apt/keyrings/hashicorp-archive-keyring.gpg

b. Download and install Terraform repository .Ensure that the below command
is to be pasted as single shell.
echo deb
[signed-by=/etc/apt/keyrings/hashicorp-archive-keyring.gpg]
https://apt.releases.hashicorp.com $(lsb_release -cs) main | tee
/etc/apt/sources.list.d/hashicorp.list

c. Install Terraform 1.5.0 package using command:

apt update

apt install -y terraform=1.5.0

4 Install Kubectl using root user

a. Download the kubectl binary.
curl -LO https://dl.k8s.io/release/v1.25.0/bin/linux/amd64/kubectl

b. Install the kubectl binary into /usr/local/bin

install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl

5 Install Helm package manager

a. Download the binary file:
curl -sSL https://get.helm.sh/helm-vx.xx.x-linux-amd64.tar.gz -o
helm-vx.xx.x-linux-amd64.tar.gz

Example: curl -sSL

https://get.helm.sh/helm-v3.15.2-linux-amd64.tar.gz -o
helm-v3.15.2-linux-amd64.tar.gz

b. Unarchive the Helm binary file.

tar xvf helm-vx.xx.x-linux-amd64.tar.gz

c. Copy the binary into /usr/local/bin

cp linux-amd64/helm /usr/local/bin/helm

chmod 775 /usr/local/bin/helm

 Deploying Veritas Cloud Scale Technology using Terraform scripts 22
About PreFlight checker (checklist) script

6 Install the Azure command line interface:

a. Download the Azure CLI bundle, version 2.9.xx
curl -sSL
https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt
-o azurecli-exe-linux-x86_64-2.9.xx.zip

b. Unzip the bundle (LOTS of files in this unzip)

unzip azurecli-exe-linux-x86_64-2.9.xx.zip

c. Execute the installation script:

./azure/install

7 Copy over the Veritas binary file bundle and Terraform script bundle. This is a
large file which may take sometime.
8 Unzip the file downloaded on the location : /var/terraform folder.

Configuring Terraform on RHEL

Using the following commands you can configure Terraform for RHEL operating
system:
■ 1. To configure the Terraform, use the following command: sudo dnf
config-manager --add-repo.

■ 2. To install the Terraform on RHEL, use the command: sudo dnf install -y
dnf-plugins-core

About PreFlight checker (checklist) script

The initial most important check with your environment readiness to deploy the
Veritas Cloud Scale Technology. The PreFlight checklist enables you to understand
the prerequisites in very detailed manner and also helps in readiness and
troubleshooting the environment, if any.
The script checks for all the necessary permissions, IP address availability, network
infrastructure to make sure the Veritas Cloud Scale Technology is deployed using
Terraform script flawlessly.
Refer to the See “Installation instructions for deploying the Veritas Cloud Scale
Technology on Azure” on page 35. on how to execute the PreFlight checker script.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 23
Stages of deploying Terraform scripts on Azure

Stages of deploying Terraform scripts on Azure

There are 3 stages to Azure provisioning and deployment. Each stage is executed
separately in each phase of their respective subdirectories.
■ Stage 1: Base stage
■ Stage 2: Addons stage
■ Stage 3: Deployment stage
The below mentioned points lets you know what actions are taken in each
deployment stage.
1. Base stage
■ Creates Azure Kubernetes Service (AKS) cluster.
■ Creates container registry.
■ Creates roles.

2. Addons stage
■ Installs Cert Manager
■ Installs Trust Manager

3. Deployment stage
■ Loads the Cloud Scale container images to local repository.
■ Tag and push the container images and Helm chart to ACR.
■ Deploys Veritas Cloud Scale Technology using Helm chart.

Parameters for base stage

Refer to the following tables and provide the configuration details depending on the
type of installation you want to perform.

Note: Refer the sample.tfvars file which is placed in the base directory which
has a format for passing the input parameters. Ensure you follow the parameter
order.

Note: Veritas Cloud Scale Technology deployment is supported on hybrid DNS

environment.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 24
Stages of deploying Terraform scripts on Azure

Table 5-1 Parameters for base stage

Parameters Description

Networking parameters that already exists

vnet_rg_name Resource group name that contains the Virtual Network.

vnet_name Virtual Network name where to provision cloud scale

resources.

subnet_name_cluster Subnet name where to provision cloud scale in AKS

cluster.

subnet_name_loadbalancer Subnet name where to provision cloud scale AKS load

balancer.

Cloud Scale resources created by Terraform

cpdata_node_pool_scaling Scaling configuration block for the cpdata pool nodes.

See default value for example.

desired_size: Desired number of nodes in cpdata

pool.

max_size: Maximum number of nodes in the cpdata

pool when autoscaling is enabled.

min_size: Minimum number of nodes in the cpdata

pool when autoscaling is enabled.

custom_tags Additional tags to be added to resources.

zone Specify an availability zone in which AKS cluster should

be located.

cloudscale_instance_id A unique identifier to be used in tags and names to

identify the Veritas Cloud Scale Technology resources
specific to this deployment.

new_rg_name Name of new resource group to be provisioned.

new_user_identity_name Name of new User Managed Identity to be provisioned.

location Location region to provision resources.

aks_name Name of the Veritas Cloud Scale Technology AKS

cluster.

enable_role_base false
d_access_control_for_aks
 Deploying Veritas Cloud Scale Technology using Terraform scripts 25
Stages of deploying Terraform scripts on Azure

Table 5-1 Parameters for base stage (continued)

Parameters Description

new_acr_name Name of new container registry to be provisioned.

use_existing_private_dns_zone Option to use an existing private DNS zone.

private_dns_zone_rg_name The resource group name where the private DNS zone
resides.

dns_to_vnet_link_name Name for the DNS zone virtual network link used for
Veritas Cloud Scale Technology cluster. Required if
creating a new private DNS zone.

use_existing_nbsm_role Option to use existing role or to create new NetBackup

Snapshot Manager (NBSM) role. Default is set to false

If this role is set to false, provisioning will automatically

create the required roles needed for deployment.

If this role is set to true, provide nbsm_role_name

values.

Refer to See “Permissions attached to nbsm_role”

on page 30. in case if you use the Terraform to create
an new nbsm_role.

nbsm_role_name This role is set if the use_existing_nbsm_role is

set to true.

This value is the name of an existing role to be used for

NetBackup Snapshot Manager to work with Azure
assets. This property cannot be changed after the
cluster is created.

aks_network_profile The network profile for the cluster. See the

modules/cloudscale-aks/REAMDE.md for defaults.

See documentation for options.

use_existing_storage_acc Set it to true only if you want to use existing storage

account to create NFS PVC.

storage_acc_id This is required in case of use_existing_storage_acc is

set to true. Mention resource id of storage account name

storage_acc_rg_name This is required in case of use_existing_storage_acc is

set to true. Mention storage account resource group
name

aks_private_dns_zone_id Mention resource id of custom private DNS zone

 Deploying Veritas Cloud Scale Technology using Terraform scripts 26
Stages of deploying Terraform scripts on Azure

Table 5-1 Parameters for base stage (continued)

Parameters Description

ACR private DNS zone values created by Terraform When the

use_existing_acr_private_dns_zone = false

use_existing_acr_private_dns_zone Option to use an existing private DNS zone for ACR

acr_dns_to_vnet_link_name This parameter is required only while creating new Azure

Container Registry (ACR) private DNS zone. The virtual
network link name is used to link the ACR private DNS
to the ACR virtual network.

acr_private_dns_zone_rg_name For existing private DNS zone: This is the resource

group name where it exists.

For creating a new private DNS zone: This is the

resource group name where to provision the zone.

When the use_existing_acr_private_dns_zone = true

acr_private_endpoint_name Name of the private endpoint when provisioning a

private ACR.

acr_rg_name The Resource Group name where the ACR resides.

acr_public_network_access_enabled Option to enable public access on a new ACR.

acr_private_service_connection_name Name of the private service connection when

provisioning a private ACR.

cloud_environment Specify which cloud environment to use.

Default value is public and possible values are public,

usgovernment, german, and china.

kubernetes_version Specify which Kubernetes version to use. The default

used is the latest Kubernetes version available in the
region

acr_private_dns_zone_group_name Name of the private DNS zone group when provisioning

a private ACR.

node_instance_size_primary_pool The node virtual machine size of the primary nodes.

Use Azure virtual machine skus

node_instance_size_media_pool The node virtual machine size of the media nodes. Use
Azure virtual machine skus.

node_instance_size_msdp_pool The node virtual machine size of the msdp nodes. Use
Azure virtual machine skus.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 27
Stages of deploying Terraform scripts on Azure

Table 5-1 Parameters for base stage (continued)

Parameters Description

node_instance_size_cpdata_pool The node virtual machine size of the cpdata nodes. Use
Azure virtual machine skus.

primary_node_pool_scaling Scaling configuration block for the Primary pool nodes.

See default value for example.

desired_size: 1 Desired number of nodes in primary

pool.

max_size: 2 Maximum number of nodes in the

primary pool when autoscaling is enabled.

min_size: 1 Minimum number of nodes in the primary

pool when autoscaling is enabled.

msdp_node_pool_scaling Scaling configuration block for the storage pool nodes.

See default value for example.

desired_size:1 Desired number of nodes in msdp

pool.

max_size: 1 Maximum number of nodes in the msdp

pool when autoscaling is enabled.

min_size: 1 Minimum number of nodes in the msdp

pool when autoscaling is enabled.

media_node_pool_scaling Scaling configuration block for the media pool nodes.

See default value for example.

desired_size:1 Desired number of nodes in media

pool.

max_size:1 Maximum number of nodes in the media

pool when autoscaling is enabled.

min_size:1 Minimum number of nodes in the media

pool when autoscaling is enabled.

cpdata_node_pool_scaling Scaling configuration block for the cpdata pool nodes.

See default value for example.

desired_size:1 Desired number of nodes in cpdata

pool.

max_size:1 Maximum number of nodes in the cpdata

pool when autoscaling is enabled.

min_size:1 Minimum number of nodes in the cpdata

pool when autoscaling is enabled.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 28
Stages of deploying Terraform scripts on Azure

Table 5-1 Parameters for base stage (continued)

Parameters Description

private_dns_zone_name The name of the private DNS Zone resource used for
cloud scale. Needs to be a unique name in the Azure
Subscription. This is not required in case of Hybrid DNS
environment.

DBaaS configuration.

The db_* variables are not required while using internal database (db_create = false)

db_create Specifies whether to create Azure Flexible Server

PostgreSQL

db_subnet_name The name of the subnet to create the PostgreSQL

Flexible Server. (Should not have any resource deployed
in) This parameter is optional and only required if
db_create is set to true.

db_username Username for the master DB user. This parameter is

optional and only required if db_create is set to true.

db_compute_tier Tier for PostgreSQL Flexible server sku : Compute and

storage options in Azure database. Possible values are:
GeneralPurpose, Burstable, MemoryOptimized. This
parameter is optional and only required if db_create
is set to true.

db_compute_size Size for PostgreSQL Flexible server sku : Compute and

storage options in Azure database for PostgreSQL This
parameter is optional and only required if db_create is
set to true.

db_zone Specify availability-zone for PostgreSQL flexible main

server. This parameter is optional and only required if
db_create is set to true.

db_standby_zone Specify availability-zone to enable high_availability and

create standby PostgreSQL Flexible Server. (Null to
disable high-availability) This parameter is optional and
only required if db_create is set to true.

db_backup_retention_days The days to retain backups for. Must be between 1 and

35. This parameter is optional and only required if
db_create is set to true.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 29
Stages of deploying Terraform scripts on Azure

Table 5-1 Parameters for base stage (continued)

Parameters Description

db_maintenance_day The day of week for maintenance window. i.e. Sunday

= 0, Monday = 1. Defaults to 0. This parameter is
optional and only required if db_create is set to true.

db_maintenance_hour The start hour for maintenance window. Defaults to 0.

This parameter is optional and only required if
db_create is set to true.

db_maintenance_minute The start minute for maintenance window. Defaults to

0. This parameter is optional and only required if
db_create is set to true.

db_parameters PostgreSQL configurations to enable. This parameter

is optional and only required if db_create is set to true.

db_geo_redundant_backup_enabled Enable Geo Redundant Backup for the PostgreSQL

Flexible Server. This parameter is optional and only
required if db_create is set to true.

db_postgresql_version Version of PostgreSQL Flexible Server. Possible values

are:

Version of PostgreSQL Flexible Server

This parameter is optional and only required if db_create

is set to true.

db_server_name The name of PostgreSQL Flexible Server instance. This

parameter is optional and only required if db_create is
set to true.

db_standby_zone Specify availability-zone to enable high_availability and

create standby PostgreSQL Flexible Server.

This parameter is optional and only required if db_create

is set to true.

db_storage_mb Storage allowed for PostgresSQL Flexible server.

Possible values : azurerm_postgresql_flexible_server

This parameter is optional and only required if db_create

is set to true.

Parameters for addons stage

There are no parameters required for addons stage.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 30
Stages of deploying Terraform scripts on Azure

Permissions attached to nbsm_role

While deploying the Base stage, Terraform creates a nbsm_role if the
use_existing_nbsm_role is set to false. By default, the Terraform assigns
permissions required for below features:

Backup from snapshot

Creating backup from snapshot
Restore from backup from snapshot
Protection of Virtual Machines
Restore disks from snapshots/restore point
Rollback restore/Cleanup in restore
Restore disk
Cleanup
List Resources
Discovery
Snapshots and Restores
Snapshot
List restore points
List snapshots
List disk snapshots
Write snapshots
Snapshot cleanup
Create restore point collections
Restore VM
Get cluster information
Scale-in/Scale-out
High availability

Refer to the section Configuring permissions on Microsoft Azure from the guide
NetBackup™ Snapshot Manager Install and Upgrade Guide to get more details
about permissions for the listed features and add new permissions in case you want
to use features which are not listed here.

Parameters for addons stage

There are no parameters required for addons stage.

Parameters for deployment stage

Refer to the following tables and provide the configuration details depending on the
type of installation you want to perform.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 31
Stages of deploying Terraform scripts on Azure

Table 5-2 Parameters for deployment stage

Parameters Description

tar_file_location NetBackup Cloud Scale tar location.

tar_file_name Name of the NetBackup Cloud Scale tar.

media_server_replica_count Provide the number of replicas for media server. The

desired size of the media server pool and the replica
count should be same. The
media_server_replica_countmust be between
1-16. The default is 1.

storage_server_replica_count Provide the number of replicas for Storage Server. The

desired size of the storage server node pool and the
replica count should be same. The
storage_server_replica_count must be between
1-16. The default is 1.

primary_server_ip_fqdn_mapping Provide IP hostname mapping for NetBackup primary

server. The primary username must be of 1-32
characters long and must start with a lowercase letter
and can only contain alphanumeric characters,
hyphens, and underscores.

storage_server_ip_fqdn_mapping Provide hostname of NetBackup storage server.

Storage server IP FQDN entries must be equal to
storage server replica count. You can add multiple
entries and it can be provided as comma separated
objects like [{},{}].

snapshot_manager_ip_fqdn_mapping Provide mapping of NetBackup Snapshot Manager

Server.

primary_username Provide username to configure primary server. The

primary_username must be of 1-32 characters long
and must start with a lowercase letter and can only
contain alphanumeric characters, hyphens, and
underscores.

It is used to login into NetBackup web UI.

primary_password Provide password for the user to configure the primary

server

The primary_password must be at least 8 characters

long and must have at least a number, a lowercase,
uppercase, and a special character (@$%!*?&.).
 Deploying Veritas Cloud Scale Technology using Terraform scripts 32
Stages of deploying Terraform scripts on Azure

Table 5-2 Parameters for deployment stage (continued)

Parameters Description

host_master_key_id Provide the Host Master Key ID. The

host_master_key_id must be of 1-32 characters
long, must contain only lowercase alphanumeric
characters, hyphens, and underscores.

host_master_key_passphrase Provide the Host Master Key passphrase. The

host_master_key_passphrase must be at least
12 characters long and must have at least a number,
a lower case, an upper case and a special character
(@$%!*?&.).

key_protection_key_id Provide the Key Protection Key ID. The

key_protection_key_id must be of 1-32 characters
long, must contain only lowercase alphanumeric
characters, hyphens, and underscores.

key_protection_key_passphrase Provide the Key Protection Key passphrase. The

key_protection_key_passphrase must be at least
12 characters long and must have at least a number,
a lowercase,an uppercase and a
specialcharacter(@$%!*?&.)

storage_server_kms_key_group Provide the name of KMS Key Group for storage server.
The storage_server_kms_key_group must be of
1-64 characters long with at least one lowercase
alphabet, other characters include alphanumeric
characters and hyphens.

storage_server_kms_ Provide the KMS key name for storage server. The
key_secret_name storage_server_kms_key_secret_name must be
of 1-32 characters long, must contain only lowercase
alphanumeric characters, hyphens or underscores.

storage_server_kms_ Provide the KMS key password for storage server. The
key_secret_password storage_server_kms_key_secret_password
must be at least 12 characters long and must have at
least a number, a lower case, an upper case and a
special character (@$%!*?&.).

storage_server_kms_ Provide the KMS key username for storage server.

key_secret_username

storage_server_credential_ Provide the credential name for storage server.

secret_name
 Deploying Veritas Cloud Scale Technology using Terraform scripts 33
Stages of deploying Terraform scripts on Azure

Table 5-2 Parameters for deployment stage (continued)

Parameters Description

storage_server_credential_ Provide the username for storage server credentials.

secret_username The
storage_server_credential_secret_username
must be of 1-62 characters long, must be in the
printable ASCII range (0x20-0x7E) except for spaces,
leading/trailing quotes and the special characters ('*',
'\', '/', '^', '(', ')','"', '<', '>', '&', '[', ']', '%', '@', '#).

storage_server_credential_ Provide the password for storage server credentials.

secret_password The
storage_server_credential_secret_password
must be of 8-62 characters long, must be in the
printable ASCII range (0x20-0x7E) except for spaces,
leading/trailing quotes and the special characters ('*',
'\', '/', '^', '(', ')','"', '<', '>', '&', '[', ']', '%', '@', '#').

primary_server_catalog_size_in_gi Provide the size for primary server catalog volume. It

must be at least 100 Gi.

primary_server_log_size_in_gi Provide the size for primary server log volume. It must
be at least 30 Gi.

primary_server_data_size_in_gi Provide the size for primary server data volume. It must
be at least 30 Gi.

media_server_log_size_in_gi Provide the size for media server log volume. It must
be at least 30 Gi.

media_server_data_size_in_gi Provide the size for media server data volume. It must
be at least 50 Gi.

storage_server_log_size_in_gi Provide the size for storage server log volume. It must
be at least 5 Gi.

storage_server_data_size_in_gi Provide the size for storage server data volume. It must
be at least 5 Gi.

snapshot_manager_log_size_in_gi Provide the size for snapshot manager log volume. It

must be at least 5 Gi.

snapshot_manager_data_size_in_gi Provide the size for snapshot manager data volume. It

must be at least 30 Gi.

fluentbit_log_collector_size_in_gi Provide the size of the fluentbit log collector. It must be

at least 100 Gi.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 34
Stages of deploying Terraform scripts on Azure

Table 5-2 Parameters for deployment stage (continued)

Parameters Description

snapshot_manager_vx_http_proxy Provide the value to be used as the HTTP proxy for all
connections for snapshot manager. This is optional
field.

snapshot_manager_vx_https_proxy Provide the value to be used as the HTTPS proxy for

all connections for snapshot manager. This is optional
field.

snapshot_manager_vx_no_proxy Provide the addresses that are allowed to bypass the

proxy server. You can specify host names, IP
addresses, and domain names in this parameter as
comma separated. This is optional field. While providing
multiple values please escape commas and dots in urls
if any with \\. For example
"localhost\\,mycompany\\.com\\,1.2.3.4"

dr_info_secret_name Name of secret to pass DR information. This is an

optional field.

dr_info_secret_passphrase Details of DR passphrase. This is an optional field.

dr_info_secret_email_address Details of DR email address. This is an optional field.

email_server_configmap_name Name of the configmap that will contain all required

information to configure email server. This is an optional
field.

email_server_configmap_details Details required to configure email server. This is an

optional field. Provide all the required fields comma
separated. Please escape commas with \\ while
providing values.

For example: email_server_configmap_details=

"smtp=smtpServerName:port\\

,ssl-verify=ignore\\,smtp-use-starttls"

global_timezone Provide timezone for Primary server pods. This is an

optional field.

For example:
primary_server_timezone="/usr/share/zoneinfo/Asia/Kolkata"
 Deploying Veritas Cloud Scale Technology using Terraform scripts 35
Installation instructions for deploying the Veritas Cloud Scale Technology on Azure

PaaS based PostgreSQL deployment (DBaaS) on Azure

PostgreSQL is a service which adds support to use external database instead of
the internal one to use with Veritas Cloud Scale Technology services. Using the
external PostgreSQL database which manages the database, it improves the
resiliency, allows the database to be scaled up as needed, and reduces the
maintenance requirements for NetBackup's database services in AKS.
DBaaS deployment is selected by setting `db_create = true` in the Terraform
deployment input file at the base step.
Refer to the section See “Stages of deploying Terraform scripts on Azure”
on page 23. for more details on the stages of deployment.
Refer to the troubleshooting section See “Troubleshooting issues” on page 44.
To reset the password for PostgreSQL database, refer to the section See “Change
the PostgreSQL database server password” on page 37.
For maintenance purpose after deployment, refer to the section Managing
PostrgreSQL DBaaS from the guide NetBackup™ Deployment Guide for Kubernetes
Clusters

Installation instructions for deploying the Veritas

Cloud Scale Technology on Azure
Following steps are required to build the infrastructure for deploying the Veritas
Cloud Scale Technology environment.

Note: Terraform stores the state about your managed infrastructure and
configuration. This state is used by Terraform to map real world resources to your
configuration, keep track of metadata, and improve performance for large
infrastructures. This state is stored by default in a local file named
terraform.tfstate in 3 respective directories. Terraform uses state to determine
what changes to make to your infrastructure. Hence, the terraform.tfstate is
very crucial and we recommend taking backup of whole terraform source code
along with terraform.tfstate files by creating zip file and uploading it into the
storage account after completing the deployment successfully.

Before proceeding to execute the scripts, you need to execute the PreFlight checker
script twice. To know about the PreFlight checker, refer to the section See “About
PreFlight checker (checklist) script” on page 22.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 36
Installation instructions for deploying the Veritas Cloud Scale Technology on Azure

How to execute the PreFlight checker scripts

1 Locate the script from the repository and execute it before the Base step using
the command:
./cloudscale-preflight-check.sh -p azure -t preInfra

2 Execute the Base stage instructions:

■ Log in and authenticate the Azure account using Azure CLI.
■ Change the directory using the command:
cd azure/base

■ Create a new .tfvars based on the sample .tfvars with the appropriate
values and execute the commands below:
terraform init
terraform plan -var-file <vars-file>.tfvars
terraform apply -var-file <vars-file>.tfvars

3 Execute the Addons steps instruction given in the next procedure.

■ Change the directory using the command:
cd azure/addons
terraform init
terraform plan
terraform apply

4 Again execute the PreFlight script after the Addons step using the command:
./cloudscale-preflight-check.sh -p azure -t postInfra

You will have to provide the Base input .tfvars file and Deployment input .tfvars
file path for validation. Before running the postInfra script you will have to
modfiy the of deployment.tfvars file.
5 Execute the Deployment steps given in the next procedure.
■ Change the directory using the command:
cd azure/deployment

■ Create new .tfvars file based on the sample .tfvars with the appropriate
values.
■ terraform init

■ terraform plan -var-file <vars-file>.tfvars

 Deploying Veritas Cloud Scale Technology using Terraform scripts 37
Installation instructions for deploying the Veritas Cloud Scale Technology on Azure

■ terraform apply -var-file <vars-file>.tfvars

6 Execute the steps mentioned in the section See “Change the PostgreSQL
database server password” on page 37.. Terraform stores input values in the
state file and to improve the security reset the db password after deployment.

Change the PostgreSQL database server password

This section describes on how to change the database password. Using the Azure
CLI, you have to first create the Azure CLI container, run the reset password
command from that container and then change the password.

Note: When setting the PostgreSQL password in DBaaS, ensure that the password
does not contain the following special characters: equal (=), double quote ("), single
quote ('), percentage (%), at sign (@), ampersand (&), question mark (?), underscore
(_), and hash (#)

Steps to change password

1 Launch an Azure CLI pod into the AKS cluster using the following command:
$ kubectl run az-cli --image=mcr.microsoft.com/azure-cli:2.53.0
--command sleep infinity

Note: Access to Azure Key Vault is restricted to specific subnets. Passwords

that are stored in Azure Key Vault can be easily updated from a pod running
in AKS.

2 Using exec, log in into the Azure CLI pod:

$ kubectl exec -it az-cli -- /bin/ash

3 From the Azure CLI pod, log in into the Azure account:
$ az login --scope https://graph.microsoft.com//.default

4 (Optional step) Create a Key Vault policy to allow the current user to retrieve
the database credential. Keep a note of your resource group, key vault, and
ID of the current user by using the following respective commands:
■ Resource group name:
$ RESOURCE_GROUP=<resource_group_name>

■ Key Vault name:

$ KEY_VAULT_NAME=$(az keyvault list --resource-group
$RESOURCE_GROUP --resource-type vault | jq -r '.[].name')
 Deploying Veritas Cloud Scale Technology using Terraform scripts 38
Installation instructions for deploying the Veritas Cloud Scale Technology on Azure

■ Current user ID name:

$ USER_ID=$(az account show | jq -r '.user.name')

■ Create a Key Vault access policy:

$ az keyvault set-policy -n $KEY_VAULT_NAME --upn $USER_ID
--resource-group $RESOURCE_GROUP --secret-permissions all

5 Note the log in name for the key vault (DBADMINUSER):

$ DBADMINUSER=$(az keyvault secret show --vault-name
$KEY_VAULT_NAME --name dbadminlogin | jq -r .value)

6 Note the password for the Key Vault (OLD_DBADMINPASSWORD):

$ OLD_DBADMINPASSWORD=$(az keyvault secret show --vault-name
$KEY_VAULT_NAME --name dbadminpassword | jq -r .value)

7 Note the server name (DBSERVER):

DBSERVER=$(az postgres flexible-server list --resource-group
$RESOURCE_GROUP | jq -r '.[].name')

8 To set a new password, follow the steps:

NEW_DBADMINPASSWORD="<new_password>" az postgres flexible-server
execute -p $OLD_DBADMINPASSWORD -u $DBADMINUSER -n $DBSERVER -d
postgres -q "ALTER USER\"nbdbadmin\" WITH PASSWORD
'$NEW_DBADMINPASSWORD';"

To re-encrypt the current password without changing it

az postgres flexible-server execute -p $OLD_DBADMINPASSWORD -u
$DBADMINUSER -n $DBSERVER -d postgres -q "ALTER USER\"nbdbadmin\"
WITH PASSWORD '$OLD_DBADMINPASSWORD';"

Note: You also have an option to reset the flexible server password using the
command. az postgres flexible-server update -g $RESOURCE_GROUP
-n $DBSERVER --admin-password <password> This command can be run
outside of the Azure CLI (az-cli) container.
 Deploying Veritas Cloud Scale Technology using Terraform scripts 39
Installation instructions for deploying the Veritas Cloud Scale Technology on Azure

9 To verify if the password uses the correct encryption method

(SCRAM-SHA-256), run the command:
$ az postgres flexible-server execute -p "<new_password>" -u
$DBADMINUSER -n $DBSERVER -d postgres -q "SELECT * from
azure_roles_authtype();"

+---------------------------+-----------+
| rolename | authtype |
|---------------------------+-----------|
| azuresu | NOLOGIN |
| pg_database_owner | NOLOGIN |
| pg_read_all_data | NOLOGIN |
| pg_write_all_data | NOLOGIN |
| pg_monitor | NOLOGIN |
| pg_read_all_settings | NOLOGIN |
| pg_read_all_stats | NOLOGIN |
| pg_stat_scan_tables | NOLOGIN |
| pg_read_server_files | NOLOGIN |
| pg_write_server_files | NOLOGIN |
| pg_execute_server_program | NOLOGIN |
| pg_signal_backend | NOLOGIN |
| azure_pg_admin | NOLOGIN |
| replication | NOLOGIN |
| nbdbadmin | SCRAM-256 |
+---------------------------+-----------+
SELECT 15
Time: 0.009s

10 To store the updated password in the key vault using the command:
$ az keyvault secret set --vault-name $KEY_VAULT_NAME --name
dbadminpassword --value "<new_password>"

11 (Optional step) To delete the Key Vault access policy that is created in step 4:
$ az keyvault delete-policy -n $KEYVAULT --upn $USER_ID

12 To exit from the Azure CLI pod using the command:

$ exit
 Deploying Veritas Cloud Scale Technology using Terraform scripts 40
Installation instructions for deploying the Veritas Cloud Scale Technology on Azure

13 To delete the Azure CLI pod using the command:

$ kubectl delete pod az-cli

14 To restart the primary pod using the command Applicable only for an existing
Veritas Cloud Scale deployment:
$ kubectl rollout restart "statefulset/${PRIMARY}" --namespace
"${NAMESPACE}"

In the command:
■ NAMESPACE is the namespace containing your NetBackup deployment.
■ PRIMARY is the name of the primary pod's stateful set.
To obtain the NAMESPACE and PRIMARY, use the command:
$ kubectl get --namespace "${NAMESPACE}" primaryserver -o
jsonpath='{.items[0].status.attributes.resourceName}'

For resetting the password for a containerized PostgreSQL database, refer to the
section Changing database server password in DBaaS from the guide.
NetBackup™ Deployment Guide for Kubernetes Clusters
 Chapter 6
Accessing the Veritas
Cloud Scale environment
This chapter includes the following topics:

■ Accessing the Veritas Cloud Scale Technology environment after deployment

Accessing the Veritas Cloud Scale Technology

environment after deployment
Once the operators are created successfully, the Terraform scripts display
deployment as successful. To verify the product deployment status, execute the
below commands from the same Terraform Management Server.
1. Login to Azure environment and execute the command:
kubectl get namespaces

After executing the above command, you will get list of namespaces created.
You can also view by navigating through UI under Kubernetes resources.
2. To view the Veritas Cloud Scale Technology deployment environment, execute
the below command and refer the table for output:
kubectl get --namespace netbackup
all,environments,primaryservers,mediaservers,msdpscaleouts,cpservers

3. Output:

NAME READY STATUS

RESTARTS AGE
pod/10-244-117-22.aks-nbux-medium-cfg-te-15902.internal 2/2
Running 0 11m
pod/dedupe1-uss-agent-54j9t 1/1
 Accessing the Veritas Cloud Scale environment 42
Accessing the Veritas Cloud Scale Technology environment after deployment

Running 0 11m
pod/dedupe1-uss-agent-6jnff 1/1
Running 0 11m
pod/dedupe1-uss-agent-bbsmn 1/1
Running 0 11m
pod/dedupe1-uss-agent-lrktl 1/1
Running 0 11m
pod/dedupe1-uss-controller-0 1/1
Running 0 11m
pod/dedupe1-uss-mds-1 1/1
Running 0 12m
pod/flexsnap-agent-59fb7f957b-5t5vj 1/1
Running 0 2m20s
pod/flexsnap-api-gateway-7b89c8957d-vlj5j 1/1
Running 0 2m21s
pod/flexsnap-certauth-65944c6797-vvspm 1/1
Running 0 3m45s
pod/flexsnap-coordinator-84ccfd95c5-59ztr 1/1
Running 0 2m20s
pod/flexsnap-fluentd-9b22l 1/1
Running 0 3m8s
pod/flexsnap-fluentd-collector-85fbc6677b-k2b56 1/1
Running 0 3m7s
pod/flexsnap-fluentd-rqqkd 1/1
Running 0 3m8s
pod/flexsnap-listener-8654fb56d9-4ltrs 1/1
Running 0 2m18s
pod/flexsnap-nginx-787878dfb6-j6m6r 1/1
Running 2 2m21s
pod/flexsnap-notification-548bf5fdb6-tdwm6 1/1
Running 0 2m19s
pod/flexsnap-rabbitmq-0 1/1
Running 0 2m57s
pod/flexsnap-scheduler-578d4646fd-z8fcv 1/1
Running 0 2m19s
pod/flexsnap-workflow-general-1709012159-12c95675-tpnqw 1/1
Running 0 78s
pod/media1-media-0 1/1
Running 0 6m58s
pod/nb-postgresql-0 1/1
Running 0 39m
pod/nucleus-env-primary-0 1/1
Running 0 34m
 Accessing the Veritas Cloud Scale environment 43
Accessing the Veritas Cloud Scale Technology environment after deployment

NAME READY AGE

statefulset.apps/dedupe1-uss-controller 1/1 11m
statefulset.apps/flexsnap-rabbitmq 1/1 2m58s
statefulset.apps/media1-media 1/1 6m59s
statefulset.apps/nb-postgresql 1/1 39m
statefulset.apps/nucleus-env-primary 1/1 34m

NAME
COMPLETIONS DURATION AGE
job.batch/flexsnap-workflow-general-1709012159-12c95675 0/1
79s 79s

NAME TAG AGE

STATUS
primaryserver.netbackup.veritas.com/nucleus-env 10.4 38m
Success

NAME AGE TAG SIZE READY

msdpscaleout.msdp.veritas.com/dedupe1 12m 20.4 1 1

NAME TAG AGE PRIMARY

SERVER STATUS
mediaserver.netbackup.veritas.com/media1 10.4 7m59s
<buildnumber>.aks-nbux-medium-cfg-te-15902.internal Success

NAME TAG AGE STATUS

cpserver.netbackup.veritas.com/cpserver-1 10.4 3m56s Success

4. Access theVeritas Cloud Scale TechnologyWeb UI using the

https://%3Cprimaryserver%3E/webui/login.
The primaryserver is the host name or IP address of the NetBackup primary
server that you want to sign in to.
Terraform scripts helps to quickly and easily build the infrastructure and deploy
Veritas Cloud Scale Technology on desired cloud environment.
 Chapter 7
Troubleshooting and
cleanup environment steps
This chapter includes the following topics:

■ Troubleshooting issues

■ Cleanup steps

Troubleshooting issues
The following table lists some of the issues that you may come across while
deploying Terraform on Azure.

Table 7-1 List of troubleshooting issues

Sr.No Issue Description / Resolution

1 Error: The deployment scripts request the db

password to encrypt the password using
"psql: error: connection to SCRAM_SHA-256 method but Azure encrypts
server at it using MD5.
"smveritas1-postgres.postgres.database.azure.com"
Resolution: You may have to re-encrypt the
(10.119.74.36), port 5432 passwords after deploying the AKS and
failed: FATAL: no DBaaS infrastructure.
pg_hba.conf entry for host
"10.119.72.151",
user "nbdbadmin", database
"postgres", no encryption"
 Troubleshooting and cleanup environment steps 45
Troubleshooting issues

Table 7-1 List of troubleshooting issues (continued)

Sr.No Issue Description / Resolution

2 The Terraform supports the Resolution: The Podman does not support
podman-based Veritas Cloud Scale engineering binary installation as the nbbuilder
Technology deployments which will script supports only docker installation.
not support the docker implemented
nbbuilder script for engineering binary
installations.

3 Even after executing the destroy If you want to delete the entire infrastructure,
command, execute the manual steps using the Azure Portal:
provided in the resolution if there are
■ Delete resource group
any folders that are not removed from
the en4vironment. For the clean deployment next time, ensure
that you have also deleted the following:

■ .tfstate
■ .tfstate.backup
■ .terraform.lock.hcl file
■ terraform folder from base, addons, and
deployment

4 Error: Azure API returned the Resolution: Retry the base deployment.
following

Error: updating Flexible Server

(Subscription: "1afb8748-7dc0-4ddc-8faf-e453dccb7ca3"
│ Resource Group Name: "rg-ananmainldbrem"
│ Flexible Server Name: "anshadbrem-postgres"):
polling after Update: polling failed: the Azure API
returned the following error: │ │ Status: "Failed" │
Code: "Failed" │ Message: "Server anshadbrem-postgres
is busy with other operations. Please try later" │

5 Before executing the terraform Reason:As per official documentation from

destroy command, execute the Microsoft, it is recommended to run the az
following command: acr login command before executing any
docker command as the acr login expires
"TOKEN=$(az acr login --name
after 3 hours.
acr_name --expose-token
--output tsv --query
accessToken);helm registry
login acr_name --username
00000000-0000-0000-0000-000000000000
--password $TOKEN""
 Troubleshooting and cleanup environment steps 46
Cleanup steps

Cleanup steps
These steps are to be followed if you wish to cleanup the resource which are created
during the deployment including infrastructure and product deployment.
Terraform destroy command can be used destroy the resources created during
the deployment. The destroy operation is perform in reverse order from that of
creation. It is used instead of deleting the assets individually.

Note: Before executing the terraform destroy command, execute the following
command:
"TOKEN=$(az acr login --name acr_name --expose-token --output tsv
--query accessToken);helm registry login acr_name --username
00000000-0000-0000-0000-000000000000 --password $TOKEN""

Sequence to cleanup the deployment infrastructure

■ Pass the input variable files (.tfvars) used as they were during creation phases,
navigate to respective directories and execute the below command:
■ 1. Deployment
cd azure/deployment
terraform destroy -var-file <vars-file>.tfvars
You may need to run the destroy command twice to cleanup the environment.

Note: It may happen that even after executing the destroy command, the
environment is not cleaned. Execute the manual steps to cleanup the remains.
Refer to the pt.3 from theSee “Troubleshooting issues” on page 44.

■ 2. Addons
cd azure/addons
terraform destroy

■ 3. Base
cd azure/base
terraform destroy -var-file <vars-file>.tfvars

Sequence to cleanup the values from keyvault

■ 1. Deploy base
■ 2. Deploy addons
■ 3. Deploy deployment
 Troubleshooting and cleanup environment steps 47
Cleanup steps

■ 4. destroy deployment
■ 5. Execute following commands:
kubectl delete pvc --all -n netbackup
kubectl delete pvc --all -n netbackup-operator-system
kubectl delete pv --all

■ 6. destroy addons