Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- How capacity licensing works
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- DELETE About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
ACS_SSI_INET_PORT entry in vm.conf (on UNIX)
The following configuration entry applies to NetBackup servers:
ACS_SSI_INET_PORT = ACS_library_software_hostname socket_name
The valid value for ACS_library_software_hostname is the host name of the ACS library host. Do not use the IP address of the ACS library host for this parameter.
The socket_name entry specifies the port that acsssi uses for incoming ACSLS responses. Valid values are 1024 - 65535 and 0. This value must be unique for each acsssi process.
A value between 1024 - 65535 indicates the number to be used as the TCP port on which acsssi accepts ACSLS responses.
0 (zero) indicates that the previous behavior (allow the port to be dynamically allocated) should remain in effect.
This entry, the ACS_CSI_HOSTPORT entry, and the ACS_TCP_RPCSERVICE entry are commonly used with firewall implementations. With these three entries in the vm.conf file, TCP connections use the designated destination ports. Note that TCP source ports are not restricted.
For example, a NetBackup media server has two ACSLS servers (ACSLS_1 and ACSLS_2) behind firewalls. Ports 30032 and 300033 have been opened in the firewall for acsssi to ACSLS server communication.
The entries would be as follows:
ACS_TCP_RPCSERVICE ACS_SSI_INET_PORT = ACSLS_1 30032 ACS_SSI_INET_PORT = ACSLS_2 30033 ACS_CSI_HOSTPORT = ACSLS_1 30031 ACS_CSI_HOSTPORT = ACSLS_2 30031
The NetBackup media server starts two acsssi processes. One listens for ACSLS_1 responses on port 30032, and the other listens on port 30033 for responses from ACSLS_2.