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
- About resources and resource dependencies
- Categories of resources
- About resource types
- About service groups
- Types of service groups
- About the ClusterService group
- About agents in VCS
- About agent functions
- Agent classifications
- VCS agent framework
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- Putting the pieces together
- 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
- Starting VCS
- 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
- Adding and deleting service groups
- Modifying service group attributes
- Bringing service groups online
- Taking service groups offline
- Switching service groups
- Freezing and unfreezing service groups
- Enabling and disabling priority based failover for a service group
- Enabling and disabling service groups
- Clearing faulted resources in a service group
- Linking and unlinking service groups
- Administering agents
- About administering resources
- About administering resource types
- Administering systems
- About administering clusters
- Using the -wait option in scripts that use VCS commands
- About administering simulated clusters from the command line
- 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
- Shared storage - if you use NetApp filers
- Shared storage - if you use SFW to manage cluster dynamic disk groups
- Shared storage - if you use Windows LDM to manage shared disks
- Non-shared storage - if you use SFW to manage dynamic disk groups
- Non-shared storage - if you use Windows LDM to manage local disks
- Non-shared storage - if you use VMware storage
- About storage configuration
- About configuring network resources
- About configuring file shares
- Before you configure a file share service group
- Configuring file shares using the wizard
- Modifying a file share service group using the wizard
- Deleting a file share service group using the wizard
- Creating non-scoped file shares configured with VCS
- Making non-scoped file shares accessible while using virtual server name or IP address if NetBIOS and WINS are disabled
- About configuring IIS sites
- About configuring services
- About configuring a service using the GenericService agent
- Before you configure a service using the GenericService agent
- Configuring a service using the GenericService agent
- About configuring a service using the ServiceMonitor agent
- Before you configure a service using the ServiceMonitor agent
- Configuring a service using the ServiceMonitor agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- Before you configure the MSMQ service group
- Configuring the MSMQ resource using the command-line utility
- Configuring the MSMQ service group using the wizard
- Modifying an MSMQ service group using the wizard
- Configuring MSMQ agent to check port bindings more than once
- Binding an MSMQ instance to the correct IP address
- Checking whether MSMQ is listening for messages
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Before you configure service groups using the Application Configuration wizard
- Adding resources to a service group
- Configuring service groups using the Application Configuration Wizard
- Modifying an application service group
- Deleting resources from a service group
- Deleting an application 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
- About the AutoRestart attribute
- About controlling failover on service group or system faults
- About defining failover policies
- About system zones
- Load-based autostart
- About freezing service groups
- About controlling Clean behavior on resource faults
- Clearing resources in the ADMIN_WAIT state
- About controlling fault propagation
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Changing agent file paths and binaries
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- About VCS event triggers
- Using event triggers
- List of event triggers
- About the dumptunables trigger
- About the injeopardy event trigger
- About the loadwarning event trigger
- About the nofailover event trigger
- About the postoffline event trigger
- About the postonline event trigger
- About the preonline event trigger
- About the resadminwait event trigger
- About the resfault event trigger
- About the resnotoff event trigger
- About the resrestart event trigger
- About the resstatechange event trigger
- About the sysoffline event trigger
- About the unable_to_restart_agent event trigger
- About the unable_to_restart_had event trigger
- About the violation event trigger
- Controlling VCS behavior
- Section IV. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- How VCS global clusters work
- VCS global clusters: The building blocks
- Visualization of remote cluster objects
- About global service groups
- About global cluster management
- About serialization - The Authority attribute
- About resiliency and "Right of way"
- VCS agents to manage wide-area failover
- About the Steward process: Split-brain in two-cluster global clusters
- Secure communication in global clusters
- Prerequisites for global clusters
- Setting up a global cluster
- Preparing the application for the global environment
- Configuring the ClusterService group
- Configuring replication resources in VCS
- Linking the application and replication service groups
- Configuring the second cluster
- Linking clusters
- Configuring the Steward process (optional)
- Stopping the Steward process
- Configuring the global service group
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Multi-tiered application support using the RemoteGroup agent in a global environment
- Test scenario for a multi-tiered environment
- Administering global clusters from Cluster Manager (Java console)
- Administering global clusters from the command line
- About administering global clusters from the command line
- About global querying in a global cluster setup
- Administering global service groups in a global cluster setup
- Administering resources in a global cluster setup
- Administering clusters in global cluster setup
- Administering heartbeats in a 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 booting a cluster system
- VCS performance consideration when a resource comes online
- VCS performance consideration when a resource goes offline
- VCS performance consideration when a service group comes online
- VCS performance consideration when a service group goes offline
- VCS performance consideration when a resource fails
- VCS performance consideration when a system fails
- VCS performance consideration when a network link fails
- VCS performance consideration when a system panics
- VCS performance consideration when a service group switches over
- VCS performance consideration when a service group fails over
- Monitoring CPU usage
- VCS agent statistics
- About VCS performance with non-HA products
- About VCS performance with SFW
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting secure clusters
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting the steward process
- 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
Configuring file shares using the wizard
The File Share Configuration Wizard enables you to create and modify file share service groups, making file shares highly available in a VCS cluster.
To configure file shares using the File Share Configuration Wizard
- Start the File Share Configuration Wizard.
- Review the information on the Welcome panel and click Next.
- On the Wizard Options panel, click Create service group and then click Next.
- On the Service Group Configuration panel, specify the following service group details:
Service Group Name
Type a name for the file share service group.
Group System List
Specify the systems on which to configure the service group.
To add systems to the service group's system list, select the systems in the Available Cluster Systems list and click the right arrow.
To remove systems from the service group's system list, select the systems in the Systems in Priority Order list and click the left arrow.
To change a system's priority in the service group's system list, select the system from the Systems in Priority Order and click the up and down arrow.
System priority defines the order in which service groups are failed over to systems. The system at the top of the list has the highest priority, while the system at the bottom of the list has the lowest priority.
Include selected systems in the service group's AutoStartList attribute
To enable the service group to automatically come online on one of the systems, select this checkbox.
Click Next.
- On the FileShare Configuration panel, specify the following configuration information for the file share resources to be created.
Virtual Computer Name
Type a unique virtual computer name to be assigned to the file share server. This is the name that the clients use to access the file shares.The virtual name must not exceed 15 characters.
Path
Click the field and either type the path of the directory to be shared or click the ellipsis button (...) to browse for a directory. The selected directories must meet the following conditions:
The selected drive, the mount path, and the file path must not exist in the VCS configuration.
The directories to be shared must reside on shared, non-system drives.
The wizard validates the selected directory and displays an error message if the directory does not meet any of the conditions.
Share Name
If a selected directory is already shared, the Share Name column lists the names by which it is shared. You can select a listed share name to make an existing share highly available. You can also create a new share for the same directory by typing a new share name.
Remove
To remove a file share from the configuration, click to select the file share, and then click Remove.
Configure NetApp SnapMirror Resource(s)
This is applicable in case of VCS for Windows only.
Check the Configure NetApp SnapMirror Resource(s) check box if you wish to set up a disaster recovery configuration.
The SnapMirror resource is used to monitor replication between filers at the primary and the secondary site, in a disaster recovery configuration.
Note that you must configure the SnapMirror resource only after you have configured the cluster at the secondary site.
Click Next.
- On the Share Permissions panel, specify the users for the file shares and assign permissions to them as follows:
Select the FileShare
From the drop-down list, select the file share with which to associate user permissions, or select the default All FileShares to set the same permissions for all file shares.
Select the Permission
From the drop-down list, select the permission to be associated with the user.
Select the User
Click the ellipsis button (...), select a user, and click OK.
Add
Click to add the specified user to the Selected Users list. By default, all selected users are given the READ_ACCESS permission.
Selected Users
Displays a list of selected users and the file share permissions. You can configure a maximum of 50 users for each file share. To configure more users, create a user group.
To change the file share permission associated with a user, click a user name in the Selected Users list and then select the desired permission from the Select the Permission drop-down list.
Remove
To deny file share access to a user, click the user name in the Selected Users list and click Remove.
Click Next.
- On the Share Properties panel, set the share properties for the file shares as follows:
Select the FileShare
From the drop-down list, select a file share whose properties you wish to set.
Enable access-based enumeration for this file share
Check the Enable access-based enumeration check box to enable the Windows access-based enumeration feature on the selected file share.
User Limit
Specify the number of users that are allowed access to the selected file share.
Choose from the following options:
Maximum allowed users: Select this option to allow access to the maximum numbers of users allowed on Windows.
Allow this number of users: Select this option and then type the number of users that you wish to grant access to the selected file share.
If you type zero or a value greater than what Windows supports, access is granted to the maximum users allowed on Windows.
Enable cache
Check the Enable cache check box to enable local caching of the contents of the selected file share. Then, specify how the contents of the file share are available to users for offline access.
In the drop-down list select from the following caching options:
Manual caching of files and programs: Only the files and programs specified by the user are available offline. This sets the FileShare resource attribute ClientCacheType to MANUAL.
Automatic caching of programs: All the files and programs that the users access from the file share are available offline. This sets the FileShare resource attribute ClientCacheType to DOCS.
Optimized automatic caching of files and programs: All the files and programs, including executables, are cached locally. The next time the user accesses the executable files, they are launched from the local cache. This sets the FileShare resource attribute ClientCacheType to PROGRAMS.
Hide share
Check the Hide Share check box to make the new share a hidden share.
Share all subfolder
Check the Share all subfolders check box to share the subdirectories.
Hide child shares
Check the Hide child shares check box to hide the shared subdirectories.
Apply these settings to
To apply the specified share properties to multiple file shares simultaneously, do the following:
Click the ellipsis button (...).
On the Copy Share Properties dialog box, select the file shares from the Available Shares list and click the right arrow to move them to the Selected Shares list.
Note that only those files shares that are not already shared are available for selection.
Click OK.
Note:
This option is not visible if you are configuring only one share in the service group.
Click Next.
- This is applicable in case of VCS for Windows only.
On the Initiator Selection panel, select the initiator for the virtual disk from the list of available initiators displayed for each cluster node, and then click Next.
If you are configuring multipath I/O (MPIO) over Fibre Channel (FC), you must select at least two FC initiators for each cluster node. Note that the node from which you run this wizard already has an initiator selected by default. This is the initiator that was specified when you connected the LUNs to this cluster node.
- On the Network Configuration panel, specify information related to your network as follows:
Select IPv4 to configure an IPv4 address for the virtual server.
In the Virtual IP Address field, type a unique virtual IPv4 address for the virtual server.
In the Subnet Mask field, type the subnet to which the virtual IPv4 address belongs.
Select IPv6 to configure an IPv6 address for the virtual server. The IPv6 option is disabled if the network does not support IPv6.
Select the prefix from the drop-down list. The wizard uses the prefix and automatically generates an IPv6 address that is valid and unique on the network.
For each system in the cluster, select the public network adapter name. This field displays the TCP/IP enabled adapters on a system, including the private network adapters, if applicable. To view the adapters associated with a system, click the Adapter Display Name field and click the arrow. Verify that you select the adapters assigned to the public network, not the private.
Click Advanced Settings to specify additional details for the Lanman resource.
On the Lanman Advanced Configuration dialog box, do the following:
Check Active Directory Update required check box to enable the Lanman resource to update the Active Directory with the virtual name. This sets the Lanman agent attributes ADUpdateRequired and ADCriticalForOnline to true.
In the Organizational Unit field, type the distinguished name of the Organizational Unit for the virtual server in the format
CN=containername,DC=domainname,DC=com.To browse for an Organizational Unit, click the ellipsis button (...) and search using the Windows Find Organization Units dialog box.
By default, the Lanman resource adds the virtual server to the default container "Computers."
Click OK.
The user account for VCS Helper service must have adequate privileges on the specified container to create and update computer accounts.
In the Specify ManagedIdentityClientID, enter the client ID of the user-assigned managed identity that you want to use for authenticating the Azure subscription.
You can get the managed identity details from the Azure portal.
Note:
This is applicable only if you are configuring the service group in an Azure cloud environment.
Click Next.
- On the Summary panel, review the service group configuration; the following service group details are displayed:
Resources
Displays a list of configured resources. The wizard assigns unique names to resources. Change the names of resource, if required.
To edit a resource name, select the resource name and either click it or press the F2 key. Edit the resource name and then press the Enter key to confirm the changes. To cancel editing a resource name, press the Esc key.
Attributes
Displays the attributes and their configured values, for a resource selected in the Resources list.
Click Next.
- Click Yes on the dialog that appears, informing you that the wizard will run commands to modify the service group configuration.
- On the completion panel, check Bring the service group online check box if you want to bring the service group online on the local system, and then click Finish.