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
Log forwarding
InfoScale introduced log forwarding for Windows machines. Windows Event Forwarding (WEF) reads any operational or administrative event log on a device and forwards the events you choose to a Windows Event Collector (WEC) server.
You can enable log forwarding on Windows server machines.
To forward the logs from Windows Event Forwarding (WEF) system:
- Open PowerShell console on forwarder system.
- Type winrm quickconfig to see winrm is running correctly.
If it is not running correctly, type Y to start the service.
- Open Computer Management.
- Click Groups.
- Open Event Log Readers.
- For event forwarding to work correctly, use the system account of the computer that will be functioning as the event collector or the domain account that the collector will be running on.
- Click Add.
- Click Object Types.
- Select the Computer check box.
- Enter the event collector system name in the box and click Check Names. It will validate the name of the machine in the network.
- Click OK.
The collector server has access to read the event logs and to set up the subscription.
To set up the subscription on collector server:
- Log in to event collector server.
- Open Event Viewer.
- From the left panel, click Subscriptions.
- Right click Subscription and select Create Subscriptions.
- Give the subscription a unique name, for example: client1Events.
- In Destination Log list, select Forwarded Events.
- There are two options of Subscription type , collector initiated and source computer initiated.
Collector Initiated means that the collector system will reach out to server(s) to collect the forwarded events. Collector initiated would work well in scenarios where there are small manageable number of forwarding computers.
Source Computer Initiated means that the forwarding computers will contact the collector computer to forward the events. Source computer initiated would help lower the strain on the collector in scenarios where there are large number of forwarding computers since the forwarding computers would be initiating the event forwarding instead of the collector.
- Click appropriate option from subscription and click Select Computers.
- Click Add Domain Computers.
- Enter the name of the event forwarding system and click Check Names.
- Once the system name is validated, click Test to check the connection.
- After successful testing, click OK and then again click OK.
- In Events to Collect, click Select Events.
- Choose the events according to your requirements.
- In Event Logs list, select the logs that are to be collected.
- To save the settings, click OK.
- In Advanced settings, go to account settings to access the remote logs. By default, Machine Account is selected.
- The Event Delivery Optimization option will specify the frequency of event delivery to the collector.
The normal option will get events every 15 minutes and does not utilize the bandwidth.
The Minimize bandwidth option will limit the frequency of network connections and uses a heartbeat interval of 6 hours.
The Minimize Latency option will ensure that events are delivered most frequently. Events will be delivered every 30 seconds in this case.
- Select the appropriate option based on your requirements and click OK.
- Forwarded events will start appearing under Windows Logs in Forwarded Events.