Search <book_title>...

Veritas Access Installation Guide

Last Published: 2018-07-27

Product(s): Access (7.3.1)

Platform: Linux

About Veritas Access product licensing

You have to obtain a license to install and use Veritas Access.

You can choose one of the following licensing methods when you install a product:

Enter a valid perpetual license key file matching the functionality in use on the systems.
A perpetual license is like a permanent license for using Veritas Access.
Enter a valid subscription license key file matching the functionality in use on the systems.
A subscription license is a license with validity of one year.
Continue with evaluation mode, and complete system licensing later
This license is a trialware which can be used for 60 days.
Installation without a license does not eliminate the need to obtain a license. The administrator and company representatives must ensure that a server or cluster is entitled to the license level for the products installed. Veritas reserves the right to ensure entitlement and compliance through auditing.

To comply with the terms of the End User License Agreement, you have 60 days to either enter a valid subscription or perpetual license key or continue in evaluation mode.

You can invoke the license program using the ./installaccess -license command.

During the installation, you get the following prompt:

1)  Enter a valid perpetual or subscription license key file
2)  Continue with evaluation mode and complete system licensing later

How would you like to license the systems? [1-2,q,?] (2) 1

Enter 1 to register your license key.

Enter the location of a valid ACCESS perpetual or subscription 
license key file: [b]

Note:

Ensure that you place the license file in a folder on the system. You may get an invalid license key error if your file is placed in the "/" location.

If you encounter problems while licensing this product, visit the Veritas licensing Support website.

www.veritas.com/licensing/process

The Veritas Access licensing has a few functional enforcements.

Table: Functional enforcements of Veritas Access licensing

Enforcement	Action
During Validity	None
During Grace period	Nagging message (in the GUI only)
Post Grace Period	Before you restart the node, you can stop the NFS, CIFS, FTP, and S3 services, but you cannot start the services again (even if you have not restarted the node). After you restart the node, the NFS, CIFS, FTP, and S3 services do not come ONLINE on the restarted node.

Enforcement

Action

During Validity

None

During Grace period

Nagging message (in the GUI only)

Post Grace Period

Before you restart the node, you can stop the NFS, CIFS, FTP, and S3 services, but you cannot start the services again (even if you have not restarted the node).

After you restart the node, the NFS, CIFS, FTP, and S3 services do not come ONLINE on the restarted node.

If you add the Veritas Access license using the GUI:

When a node is restarted after the license has expired, the NFS, CIFS, FTP, and S3 services are stopped on that node. The status of the service appears ONLINE if the service is running anywhere in the cluster, even if it is OFFLINE on this node. Check the alerts on each node individually to see if the service is ONLINE or OFFLINE locally.
An option to start, stop, and check the status of NFS, CIFS, and S3 services is available. You cannot start, stop, or check the status of the FTP service.
You can only provide the license file from the local system, the scp path is not supported through the GUI.

If you add the Veritas Access license using the CLISH:

When a node is restarted after the license has expired, the NFS, CIFS, FTP, and S3 services are stopped on that node. You can use the support services show command to display the node-wise status of the service.
An option to start, stop, and check the status of NFS, CIFS, FTP, and S3 services is available.
You can add the license using the license add command. The license add command provides support for scp path as well.
The license list and license list details commands give details of the license installed on each node of the cluster.