Veritas Access Installation Guide
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux requirements
- Network and firewall requirements
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installing the operating system on each node of the cluster
- Installing Veritas Access on the target cluster nodes
- About managing the NICs, bonds, and VLAN devices
- About VLAN tagging
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading the operating system and Veritas Access
- Performing a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Configuring the secure shell for communications
- Appendix C. Manual deployment of Veritas Access
Per-Core licensing model
The Per-Core licensing model is based on time period. You can license Veritas Access as per your requirement for the raw capacity. Veritas provides support of 12 months, 24 months, and 36 months for the licensing model.
Note:
The Per-Core licensing model is supported in this release only if you upgrade to Veritas Access 7.4.2 from an earlier version of Veritas Access that uses this license model. However, Veritas recommends that you use the Per-TB licensing model.
For more information about the Per-TB licensing model:
The time-based license category includes the following licenses:
Perpetual license: You can procure a perpetual license to use the Veritas Access software for an unlimited period.
Subscription license: You can procure a subscription license to use the Veritas Access software for a specified period. After the subscription period is over, you need to renew the subscription license. The subscription period can be of 1 year, 2 years, 3 years, and so on.
Trialware license: You can download a trial version of the Veritas Access software from the Veritas website to evaluate it for 60 days.
For more information about functional enforcements and notes related to licensing: