Veritas InfoScale™ 7.3 Release Notes - Linux
- About this document
- Important release information
- About the Veritas InfoScale product suite
- Licensing Veritas InfoScale
- About Veritas Services and Operations Readiness Tools
- Changes introduced in 7.3
- Changes related to Veritas Cluster Server
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to virtualization
- Changes related to replication
- Changes related to operating systems
- Changes related to Veritas Cluster Server
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Virtualization known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Cluster Server agents for Volume Replicator known issues
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Storage Foundation for Sybase ASE CE known issues
- Application isolation feature known Issues
- Issues related to installation and upgrade
- Software Limitations
- Virtualization software limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation for Sybase ASE CE software limitations
- Documentation
Support for systemd in Linux
systemd is an initialization system that controls how services are started, stopped, or otherwise managed on RHEL 7 and SLES12 or later systems. The LSB files for the VCS stack have been replaced with the corresponding systemd unit service files. In the older RHEL distributions, the init.d daemon managed the related services. Now, systemd manages them as unit service files.
To provide systemd support for those services in Linux, the following VCS unit service files and startup scripts are made available:
Old LSB file | New unit service file located at: | Corresponding script file (SourcePath) |
---|---|---|
/etc/init.d/amf | amf.service | /opt/VRTSamf/bin/amf |
/etc/init.d/gab | gab.service | /opt/VRTSgab/gab |
/etc/init.d/llt | llt.service | /opt/VRTSllt/llt |
/etc/init.d/vcs | vcs.service | /opt/VRTSvcs/bin/vcs |
/etc/init.d/vcsmm | vcsmm.service | /opt/VRTSvcs/rac/bin/vcsmm |
/etc/init.d/vxfen | vxfen.service | /opt/VRTSvcs/vxfen/bin/vxfen |
To start, stop, restart, or view the status of one of these services, use the following command:
systemctl [start | stop | restart | status] unitServiceFile
Note:
The status option of the systemctl command displays only the status of the unit service file, like whether it is active, inactive, or failed.
To view the actual status information about the module or to view the HAD status, use:
serviceSourceScript status
For example:
/opt/VRTSvcs/bin/vcs status
To view the source path of any service, you can use the systemctl command as follows:
# systemctl show unitServiceFile -p SourcePath
For example:
# systemctl show vcs -p SourcePath
The systemctl command displays the source path as follows:
SourcePath=/opt/VRTSvcs/bin/vcs
Wherever systemd support is available, all the process in the VCS stack start in system.slice instead of user.slice.