InfoScale™ 9.0 Storage Foundation and High Availability Solutions Solutions Guide - Windows
- Section I. Introduction
- Introducing Storage Foundation and High Availability Solutions
- Using the Solutions Configuration Center
- SFW best practices for storage
- Section II. Quick Recovery
- Section III. High Availability
- High availability: Overview
- How VCS monitors storage components
- Deploying InfoScale Enterprise for high availability: New installation
- Notes and recommendations for cluster and application configuration
- Configuring disk groups and volumes
- Configuring the cluster using the Cluster Configuration Wizard
- About modifying the cluster configuration
- About installing and configuring the application or server role
- Configuring the service group
- About configuring file shares
- About configuring IIS sites
- About configuring applications using the Application Configuration Wizard
- About configuring the Oracle service group using the wizard
- Modifying the application service groups
- Adding DMP to a clustering configuration
- High availability: Overview
- Section IV. Campus Clustering
- Introduction to campus clustering
- Deploying InfoScale Enterprise for campus cluster
- Notes and recommendations for cluster and application configuration
- Reviewing the configuration
- Configuring the cluster using the Cluster Configuration Wizard
- Creating disk groups and volumes
- Installing the application on cluster nodes
- Section V. Replicated Data Clusters
- Introduction to Replicated Data Clusters
- Deploying Replicated Data Clusters: New application installation
- Notes and recommendations for cluster and application configuration
- Configuring the cluster using the Cluster Configuration Wizard
- Configuring disk groups and volumes
- Installing and configuring the application or server role
- Configuring the service group
- About configuring file shares
- About configuring IIS sites
- About configuring applications using the Application Configuration Wizard
- Configuring a RVG service group for replication
- Configuring the resources in the RVG service group for RDC replication
- Configuring the VMDg or VMNSDg resources for the disk groups
- Configuring the RVG Primary resources
- Adding the nodes from the secondary zone to the RDC
- Verifying the RDC configuration
- Section VI. Disaster Recovery
- Disaster recovery: Overview
- Deploying disaster recovery: New application installation
- Notes and recommendations for cluster and application configuration
- Reviewing the configuration
- About managing disk groups and volumes
- Setting up the secondary site: Configuring SFW HA and setting up a cluster
- Setting up your replication environment
- About configuring disaster recovery with the DR wizard
- Installing and configuring the application or server role (secondary site)
- Configuring replication and global clustering
- Configuring the global cluster option for wide-area failover
- Possible task after creating the DR environment: Adding a new failover node to a Volume Replicator environment
- Maintaining: Normal operations and recovery procedures (Volume Replicator environment)
- Testing fault readiness by running a fire drill
- About the Fire Drill Wizard
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- Deleting the fire drill configuration
- Section VII. Microsoft Clustering Solutions
- Microsoft clustering solutions overview
- Deploying SFW with Microsoft failover clustering
- Tasks for installing InfoScale Foundation or InfoScale Storage for Microsoft failover clustering
- Creating SFW disk groups and volumes
- Implementing a dynamic quorum resource
- Deploying SFW with Microsoft failover clustering in a campus cluster
- Reviewing the configuration
- Establishing a Microsoft failover cluster
- Tasks for installing InfoScale Foundation or InfoScale Storage for Microsoft failover clustering
- Creating disk groups and volumes
- Implementing a dynamic quorum resource
- Installing the application on the cluster nodes
- Deploying SFW and VVR with Microsoft failover clustering
- Part 1: Setting up the cluster on the primary site
- Reviewing the prerequisites and the configuration
- Part 2: Setting up the cluster on the secondary site
- Part 3: Adding the Volume Replicator components for replication
- Part 4: Maintaining normal operations and recovery procedures
- Section VIII. Server Consolidation
- Server consolidation overview
- Server consolidation configurations
- Typical server consolidation configuration
- Server consolidation configuration 1 - many to one
- Server consolidation configuration 2 - many to two: Adding clustering and DMP
- About this configuration
- SFW features that support server consolidation
Creating non-scoped file shares configured with VCS
File shares configured with VCS on Windows Server are accessible only using the virtual server name (Lanman resource). These file shares are not accessible using the IP address.
The FileShare agent is enhanced to address this issue. The FileShare agent behavior can be controlled using the following registry key:
HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\
Lanman\virtualName\DisableServerNameScoping
Set the DisableServerNameScoping key to have the FileShare agent support non-scoped file shares.
You must create this registry key manually.
Note:
Incorrectly editing the registry may severely damage your system. Back up the registry before making changes.
To configure the DisableServerNameScoping registry key
- 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 the following location:
HKLM\SOFTWARE\VERITAS\VCS\BundledAgents
- Click Edit > New > Key and create a key by the name Lanman, if it does not exist already.
- Select the Lanman key and click Edit > New > Key and create a key by the name virtualName.
Here, virtualName should be the virtual computer name assigned to the file share server. This is the VirtualName attribute of the Lanman resource in the file share service group.
The newly created registry key should look like this:
HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\ Lanman\virtualName
- Select the key that you created in step 4 (virtualName) and add a DWORD type of value.
The value name should be DisableServerNameScoping and value data should be 1.
The value 1 indicates that the FileShare and Lanman agents support non-scoped file shares on Windows Server systems.
- If there are multiple file share service groups to be used in the non-scoped mode, repeat steps 4 and 5 for each Lanman resource that is configured in the file share service group.
- Save and exit the Registry Editor.
You must create this key only for Lanman resources that are part of VCS file share service groups. Configuring this key for Lanman resources that are part of other VCS service groups may result in unexpected behavior.