Deploying a Commvault Access Node from the AWS Marketplace

From the AWS Marketplace, you can deploy an AWS instance as a cloud access node from the Commvault Cloud Access Node BYOL. The Commvault Cloud Access Node BYOL contains all the components that are required to support Linux operations in the Commvault environment. After the deployment, you can subscribe to the BYOL packages on the AWS Marketplace.

The cloud access node can be any of the following:

MediaAgent with FREL (file recovery enabler for Linux)
Access node (that is, it has the Virtual Server package and the Cloud Apps package)
Media Agent, FREL, and access node

To review the terms and conditions agreement before subscribing, see:

Requirements

If your CommServe system is a more recent release of Commvault than the MediaAgent, update the MediaAgent to the same feature release after deployment.
Obtain the host name or IP address of the CommServe host. You will enter the host name/IP address during the procedure.

Procedure

Launch an Instance in the AWS Console

From the AWS EC2 Console, go to Instances, and then click Launch Instance.

AWS opens a wizard to guide you through the deployment.
Search for "Commvault".
Display the search results for AWS Marketplace.
Select the Commvault Cloud Access Node BYOL.
Select an instance type that provides the available CPU cores and memory for the instance.
Identify a network and subnet that are available for the deployment.
If necessary, add additional storage.

By default, the Commvault Cloud Access Node BYOL provides 100 GB of storage.

Note

When you launch the instance, you must provide a key pair that can be used. You can use an existing key pair or create a new key pair as part of the deployment.

Configure a Commvault Client for the AWS Instance

From the CommCell Console, right-click Client Computers, and then select New Client > File System > Unix.
In the Client Name box, enter a descriptive label for the AWS instance.

Make a note of the client name for the AWS instance.
In the Host Name box, enter the public IP address for the AWS instance.
Click Next.
Verify the client information, and then click Finish.

Configure Network Route Settings on the Client for the CommServe Host

Right-click the CommServe node, and then select Properties.

The CommCell Properties dialog box appears.
On the Network Route Configuration tab, select the Configure Network Route Settings check box.
Click Advanced.
On the Incoming Connections sub-tab, click Add to add the proxy client connection.
Select the AWS instance in the From list.
Select BLOCKED from the State list.
Click OK.

Configure Network Route Settings on the Client for the AWS Instance

Under Client Computers, right-click the client for the AWS instance, and then select Properties.
Click Network.

The Network Properties dialog box appears.
On the Network Route Configuration tab, select the Configure Network Route Settings check box.
Click Advanced.
On the Incoming Connections sub-tab, click Add to add the CommServe host connection.
Select the client for the CommServe host in the From list.
From the State list, select Restricted.
Click OK.
To change the default tunnel port, on the Incoming Ports tab, select the Override default tunnel port check box, and enter the port number for incoming tunnel connections.

Make a note of the port number you enter, for example, 443. The default tunnel port is the Commvault Communications (CVD) service port plus 3, which is, 8403.
Click OK.
Right-click the CommCell node, and then select All Tasks > Push Network Route Configuration.
Under Client Computers, right-click the client for the CommServe host, and then select All Tasks > Push Network Route Configuration.

Register the Linux Instance with Commvault

Log on to the new instance using your Amazon EC2 user credentials, and then perform the following actions from the command line:
1. Switch to root user:
```
sudo su
```
2. Go to the /etc folder:
```
cd /etc
```
3. Run the Commvault registration script:
```
./commvaultRegistration.sh
```
4. Provide the required information. The values you enter must match the corresponding values that you provided in the preceding steps.
  - Enter Client Name: Enter the Commvault client name for the AWS instance.
  - Enter Client Hostname: Enter the fully qualified domain name (FQDN) or the public IP address for the AWS instance.
  - Enter Client Group Name: Enter the name of the client computer group where the AWS instance should be included.
  - Enter CS Name: Enter the short name for the CommServe client (without the domain name).
  - Enter CS Hostname: Enter the fully qualified host name for the CommServe host.
  - Enter CS Username: Enter the user name for the CommServe host (for example, admin).
  - Enter CS Password: Enter the password for the CommServe host user.
  - Is CS behind a firewall? (yes/no): Enter yes.
  - Enter the option (1/2/3): Enter 2 to indicate that the CommServe host should initiate the connection to the AWS instance.
    
    [Option 1] CS f/w tunnel port (client can connect to CS)
    
    [Option 2] Client f/w tunnel port (CS can connect to client)
    
    [Option 3] CS reachable via proxy
  - Enter the tunnel port number the CommServe system can use to open a connection toward the client: Enter the port number that you entered for the AWS instance (for example, 443).
  - Is HTTP proxy used for communication between the CommServe host and the client ? (yes/no): Enter no.
  - Do you wish to proceed with registration using the above information? (yes/no): Enter yes.
When the wizard completes, the instance is configured as a VSA proxy and a MediaAgent that can connect to the CommServe host.

After creating a library, to create a DDB path, use the following mount path: /mnt/commvault_ddb.

On the Linux FREL, the Commvault software components are installed to the following paths:
- /opt/commvault
- /var/log/commvault
- /var/opt/commvault_data/commvault/iDataAgent/jobResults
- /var/opt/commvault_data/commvault/MediaAgent/IndexCache
- /var/opt/commvault_ddb
Perform a remote install of all currently available Commvault feature release maintenance releases on the Linux machine.