Highlighted

Multiple Shares issue

We have four Windows 2008 R2 SP1 SFW 5.1 HA clusters haring Files.

The all have same configuration in terms of service pack, version of SFW 5.1 CP8 and Windows 2008 R2 SP1 however the way sharing works differ between these clusters.

If SFW creates a share on Cluster 1 nodes, the share is available when addresses the node hostname.

For example, we create virtual name with Lanman Resource \\VIRTUAL01\SHARE01

When the share resource is brought up on cluster #1 we can access SHARE01 using \\CLUSTER01\SHARE01 as well as \\VIRTUAL01\SHARE01

When the same share resoure is brought on Cluster #2 we cannot do it using \\CLUSTER02\SHARE02 and can only do it \\VIRTUAL01\SHARE01

CLUSTER01 and CLUSTER02 are physical nodes hostnames.

There's also another difference.

When Storage Foundation creaes a Lanman Vistual Name on Cluster #1, we can see all the root windows drives with that virtual name e.g.

\\VIRTUAL01\c$

When the same virtual name is created on cluster 2, we cannot access trhe root drives.

 

This essentially leads to interesting scenarios:

on the node where the SFW does not mix with the Windows sharing we can create two identical sharenames and point them to different locations.

e.g. on Cluster Node 2 we can do "SHARE01" -> pointing to c:\Dir1 from Windows and also bring a Vierual Cluster Resource and Create "SHARE01" pointing to D:\Dir2 but accessingle only via the Virtual Lanman Resoirce name, created by the Storage Foundation.

When looking at the Share and Storage management from Windows - we can see both Shares identically named pointing to different locations.

We cannot do so on Cluster 1 as creating the same share name will conflict with existing share name.

 

We are trying to nail this down but so far went through the setu (which was done from same image of OS and enabled same features).. Server Policy, SFW 5.1 version and updates - all to no avail.

 

We need to understand this behaviour and what it coudl be related to.

Any feedback is appreciated.

Thank you.

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Hi Sergy,   Windows 2008

Hi Sergy,

 

Windows 2008 Failover clustering introduced a new concept for fileshares that all clustered fileshares are scoped to the virtual server name and is only accessible via the vitual server name.  SFW-HA originally followed Microsoft's lead and implemented scoped clustered fileshares.  However, many of our customers did not like this behavior and we introduced a patch (Hotfix_5_1_20002_2220352) that is included in CP8. 

SFW-HA offers serveral different ways to disable fileshare scoping.  You can create a couple of registry key entries as outlined in the readme of the hot fix or you can clear out the LanmanResName attribute of the FileShare resource(s) that scoping should be disabled.

It appears that your clusters are not as similar as you think.  The cluster that is not scoping the FileShares has a registry entry that is not there on the other cluster or the LanmanResName attribute is not defined.

 

For details on the FileShare scoping hot fix got to https://sort.symantec.com/patch/detail/5897 and search for Hotfix_5_1_20002_2220352.)

Thank you,

Wally

View solution in original post

4 Replies
Highlighted
Accepted Solution!

Hi Sergy,   Windows 2008

Hi Sergy,

 

Windows 2008 Failover clustering introduced a new concept for fileshares that all clustered fileshares are scoped to the virtual server name and is only accessible via the vitual server name.  SFW-HA originally followed Microsoft's lead and implemented scoped clustered fileshares.  However, many of our customers did not like this behavior and we introduced a patch (Hotfix_5_1_20002_2220352) that is included in CP8. 

SFW-HA offers serveral different ways to disable fileshare scoping.  You can create a couple of registry key entries as outlined in the readme of the hot fix or you can clear out the LanmanResName attribute of the FileShare resource(s) that scoping should be disabled.

It appears that your clusters are not as similar as you think.  The cluster that is not scoping the FileShares has a registry entry that is not there on the other cluster or the LanmanResName attribute is not defined.

 

For details on the FileShare scoping hot fix got to https://sort.symantec.com/patch/detail/5897 and search for Hotfix_5_1_20002_2220352.)

Thank you,

Wally

View solution in original post

Highlighted

Hi Wally

Is there a fix/solution for SFW-HA 6.0 as well?

Regards,

Frode

Highlighted

Hi Frode, That fix is already

Hi Frode,

That fix is already rolled into the 6.0 product.  You can use the workaround of clearing out the LanmanResName attribute or you can check the Bundled Agents Guide to see how to disable FileShare scoping in 6.0.

The Bundled Agents guide can be found on the 6.0 installation media or on the https://sort.symantec.com/land website.

Thank you,

Wally

Highlighted

Registry key did the trick

Onnly found the registry description in the hotfix readme file.

DisableServerNameScoping=1 under HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\<VirtualName> and a reboot was the trick.

Thanks Wally!

-frode