InfoScale™ 9.0 Cluster Server Administrator's Guide - Windows
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- Agent classifications
- About cluster control, communications, and membership
- About security services
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Getting started with VCS
- Administering the cluster from the command line
- About administering VCS from the command line
- Stopping the VCS engine and related processes
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- About administering resource types
- About administering clusters
- Configuring resources and applications in VCS
- About configuring resources and applications
- About Virtual Business Services
- About Intelligent Resource Monitoring (IMF)
- About fast failover
- How VCS monitors storage components
- About storage configuration
- About configuring network resources
- About configuring file shares
- About configuring IIS sites
- About configuring services
- Before you configure a service using the GenericService agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Adding resources to a service group
- About application monitoring on single-node clusters
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- Modifying the cluster configuration
- Section III. Administration - Beyond the basics
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- List of event triggers
- Controlling VCS behavior
- Section IV. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- Configuring replication resources in VCS
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from Cluster Manager (Java console)
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Connecting clusters–Creating global clusters
- Section V. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- VCS agent statistics
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting and recovery for global clusters
- VCS utilities
- VCS performance considerations
- Section VI. Appendixes
- Appendix A. VCS user privileges—administration matrices
- Appendix B. Cluster and system states
- Appendix C. VCS attributes
- Appendix D. Configuring LLT over UDP
- Appendix E. Handling concurrency violation in any-to-any configurations
- Appendix F. Accessibility and VCS
- Appendix G. Executive Order logging
Log forwarding
You can enable log forwarding on Windows server machines. To set up event forwarding, minimum two systems are required. One system is used as event forwarder and another system as event collector server.
From event forwarder system, forward all the events to the collector system.
To forward the logs from forwarder system
- Open PowerShell console on forwarder system.
- Type winrm quickconfig to see winrm is running correctly. If not running 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. e.g. 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.