Veritas InfoScale™ 8.0.2 Release Notes - Windows
- Introduction and product requirements
- Changes introduced in this release
- Executive Order logging
- Limitations
- Deployment limitations
- Cluster management limitations
- Storage management limitations
- Multi-pathing limitations
- Replication limitations
- Solution configuration limitations
- Internationalization and localization limitations
- Interoperability limitations
- Known issues
- Deployment issues
- Cluster management issues
- Cluster Server (VCS) issues
- Cluster Manager (Java Console) issues
- Global service group issues
- VMware virtual environment-related issues
- Cluster Server (VCS) issues
- Storage management issues
- Storage Foundation issues
- VEA console issues
- Snapshot and restore issues
- Snapshot scheduling issues
- Multi-pathing issues
- Replication issues
- Solution configuration issues
- Disaster recovery (DR) configuration issues
- Fire drill (FD) configuration issues
- Quick recovery (QR) configuration issues
- Internationalization and localization issues
- Interoperability issues
- Miscellaneous issues
- Fibre Channel adapter issues
- Deployment issues
Enabling logs
InfoScale introduced a VCS_ENABLE_PUBSEC_LOG variable to enable the pubsec logs. This variable controls all the logs in C:\Program Files\Veritas\Cluster Server
folder generated by the VCS processes. The default value is disabled. If it is enabled, the VCS process writes logs with additional information which is timestamped in YYYY-MM-DDTHH:MM:SS.mmm+UTC format, followed by the hostname in FQDN format, and then followed by the log statement. In addition to this, it also logs any read-only command executed by the HAD process.
You can enable or disable EO specific logging by executing following command in command prompt / Powershell.
To enable EO based logging for VCS, set:
VCS_ENABLE_PUBSEC_LOG to 1
To disable EO based logging for VCS, set:
VCS_ENABLE_PUBSEC_LOG to 0
You can also enable EO based logging using the following steps.
To enable cluster server logs, follow these steps:
- Press Windows + R to start run command prompt.
- Type sysdm.cpl and press Enter.
- Go to Advanced tab.
- Click the Environment Variablesbutton.
- In System Variables section, click New button.
- Enter variable name as VCS_ENABLE_PUBSEC_LOG and enter value as 1.
- Click OK.
- Restart the following services by executing the following commands in command prompt/Powershell to see the updated logging as per EO standards.
Stop VCS engine service:
hastop -local -force
Start VCS engine service:
hastart
Stop VCS command server:
net stop cmdserver
Start VCS command server:
net start cmdserver
Stop VCS auth server:
net stop vcsauthserver
Start VCS auth server:
net start vcsauthserver