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
Setting the timeout duration for which the VMNSDg agent waits for all the disks to arrive before importing the disk group
During the disk group import operation, the VMNSDg agent waits for all the disks to arrive before importing the disk group. In case there are some missing disks, the VMNSDg resource will fault after this time. The default timeout duration is 60s. This time duration can also be controlled using the following registry key:
HKLM\Software\Veritas\VCS\BundledAgents\VMNSDg\<resource_name>\DgImportWaitTimeOut:
Set the value of the DgImportWaitTimeOut key to the time duration in seconds for which the VMNSDg agent waits for all the disks to arrive before importing the disk group.
You must create this registry key manually. Perform the following steps to create and set the DgImportWaitTimeOut registry key.
Note:
Incorrectly editing the registry may severely damage your system. Make a backup copy before making changes to the registry.
To configure DgImportWaitTimeOut registry parameter:
- To open the Registry Editor, press Window+R on the desktop (opens the Run dialog box), type regedit, and then click OK.
- In the registry tree (on the left), navigate to HKLM\SOFTWARE\VERITAS\VCS\BundledAgents.
- Click Edit > New > Key and create a key by the name VMNSDg , if it does not exist already.
- Select the VMNSDg key and click Edit > New > Key and create a key by the name <resource_name>.
Here <resource_name> should be the resource name of the VMNSDg resource.
The newly created registry key should look like this:
HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\VMNSDg\<resource_name>
- Select the key that you created in step 4 (<resource_name>) and add a DWORD type of value.
The value name should be DgImportWaitTimeOut and value data should be the desired timeout duration in seconds The value indicates the timeout interval for which the VMNSDg agent waits for the all the disks to arrive.
- If there are multiple service groups to be used in the non-shared storage environment, repeat steps 4 and 5 for each VMNSDg resource that is configured in the service group.
- Save and exit the Registry Editor.