Storage Foundation and High Availability Solutions 7.3.1 HA and DR Solutions Guide for Microsoft SharePoint 2010 - Windows
- Introducing Storage Foundation and High Availability Solutions for SharePoint 2010
- About clustering solutions with SFW HA
- About high availability
- How a high availability solution works
- About replication
- About disaster recovery
- What you can do with a disaster recovery solution
- Typical disaster recovery configuration
- About high availability support for SharePoint Server
- About the SharePoint Search service application
- Introducing the VCS agent for SharePoint Server 2010
- Configuration workflows for SharePoint Server 2010
- Reviewing the HA configuration
- Reviewing the disaster recovery configuration
- High availability (HA) configuration
- Disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring the storage hardware and network
- Configuring the cluster using the Cluster Configuration Wizard
- Using the Solutions Configuration Center
- About the Solutions Configuration Center
- Starting the Solutions Configuration Center
- Options in the Solutions Configuration Center
- About launching wizards from the Solutions Configuration Center
- Remote and local access to Solutions wizards
- Solutions wizards and logs
- Workflows in the Solutions Configuration Center
- Installing and configuring SharePoint Server 2010 for high availability
- Configuring disaster recovery for SharePoint Server 2010
- Introducing the VCS agent for SharePoint Search Service Application
- About the VCS agent for SharePoint Search service application
- Configuring the SharePoint Search Service Application service group
- Prerequisites for configuring a service group for a SharePoint Search service application
- Installing and configuring SharePoint Server 2010
- Changing the index location of the Crawl and Query components
- Configuring a service group for a SharePoint Search service application manually
- Configuring the service group for a Search service application using the wizard
- Verifying the application service group
- Configuring a Search service application for disaster recovery
- Administering the SharePoint Search Service Application service group
- Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
- About Just In Time Availability
- Prerequisites
- Setting up a plan
- Deleting a plan
- Managing a plan
- Viewing the history tab
- Limitations of Just In Time Availability
- Getting started with Just In Time Availability
- Supported operating systems and configurations
- Viewing the properties
- Log files
- Plan states
- Troubleshooting Just In Time Availability
VCS logging
VCS generates two error message logs: the engine logs and the agent logs. Log file names are appended by letters. Letter A indicates the first log file, B the second, C the third, and so on.
The agent log is located at %VCS_HOME%\log\agent_A.txt. The format of agent log messages is:
Timestamp (Year/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource Name | Entry Point | Message Text
The following table describes the agent log message components and their descriptions.
Table: Log message components and their description
Log message component | Description |
|---|---|
Timestamp | Denotes the date and time when the message was logged. |
Mnemonic | Denotes which Veritas product logs the message. For Cluster Server, the mnemonic is 'VCS'. |
Severity | Denotes the severity of the message. Severity is classified into the following types:
Among these, CRITICAL, ERROR, and WARNING indicate actual errors. NOTE and INFO provide additional information. |
Unique Message ID (UMI) | UMI is a combination of Originator ID, Category ID, and Message ID. For example, the UMI for a message generated by the SharePoint agent would resemble: V-16-20083-107. Originator ID for all VCS products is 'V-16.' Category ID for SharePoint agent is 20083. Message ID is a unique number assigned to the message text. |
Message Text | Denotes the actual message string. |
You can view these message logs using Notepad or any text editor. All messages are logged to the engine and the agent logs. Messages of type CRITICAL and ERROR are written to the Windows event log.
A typical agent log resembles:
2012/09/20 07:53:51 VCS ERROR V-16-20083-107 SharePointSearch:SharePointSearch_VM_Admin:monitor: Failed to open connection with the helper process. Error: 2.