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
Limitations on restricting user privileges
The following limitations apply when you restrict user privileges by setting the VCS_RESTRICT_LOCAL_ADMIN_GROUP environment variable to 1:
Even if a user of the local Administrators group cannot stop a cluster using hastop due to insufficient privileges, they can stop the cluster by killing the HAD process. The user can then manually edit the cluster configuration to assign themselves any role, and thereby perform any cluster operation after the cluster is started again.
Restricted privileges are applicable only when HAD is running. So even if users do not have any privileges in the cluster, if they belong to the local Administrators group on a cluster node, they can start HAD by using hastart.
Even though the Operator privilege is specified for an AD group in the cluster configuration, when a user from that group logs in to Cluster Manager, they are granted the Guest privilege. You can work around this limitation by performing the following procedure.
To ensure that Cluster Manager honors Operator privilege assigned to users in an AD group
- Log on to the cluster node as the user who is granted Guest privilege even though its AD group has Operator privilege specified in the configuration.
- Navigate to
%VCS_HOME%\eat\bin
and run vssat showcred. - Note the groupName and domainName values for the AD group that is mentioned in the cluster configuration.
- Add these values in the groupName@domainName format to either the AdministratorGroups or the OperatorGroups attribute of the cluster as follows:
haclus -modify AdministratorGroups -add groupName@domainName
or
haclus -modify OperatorGroups -add groupName@domainName
For example:
C:\Program Files\Veritas\cluster server\eat\bin>vssat showcred showcred ... Found: 2 ************************************* User Name: HADUSER1 Domain Name: VCSWIN Domain Type: nt Issued By: /CN=broker/OU=root@manish-vm222.vcswin.in/O=vx Issued To: /CN=HADUSER1/OU=VCSWIN/O=nt Friendly Name: Serial Number: 0x61 Root Credential: 0 Trusted Credential: 0 Expiry Interval: Dec 14 11:54:02 2017 GMT Group Information: Group Count: 12 Group Name: VCSWIN\Users Group Name: VCSWIN\Domain Users Group Name: VCSWIN\hadgroup1 Group Name: MANISH-VM222\Users Group Name: MANISH-VM222\Administrators Group Name: MANISH-VM222\Everyone Group Name: NT AUTHORITY\INTERACTIVE Group Name: MANISH-VM222\CONSOLE LOGON Group Name: NT AUTHORITY\Authenticated Users Group Name: NT AUTHORITY\This Organization Group Name: MANISH-VM222\LOCAL Group Name: MANDATORY LABEL\Medium Mandatory Level Certificate Hash 818cf13273170c8cd3b51dab36b6f5e820d6dcbf UUID: {6820ff7e-6c06-4cc2-b85a-fead694340a8} *************************************
Here, Group Name = VCSWIN\hadgroup1 and Domain Name = VCSWIN.
So, you need to run a command as:
haclus -modify AdministratorGroups -add VCSWIN\hadgroup1@ VCSWIN