CompositeFileShare agent

Article:HOWTO65819  |  Created: 2012-01-25  |  Updated: 2012-01-25  |  Article URL http://www.symantec.com/docs/HOWTO65819
Article Type
How To


Environment

Subject


CompositeFileShare agent

Product: VCS for Windows, SFW HA

Platform: Windows

Version: 6.0

The CompositeFileShare agent enables systems to share multiple subfolders for each of the shared folders. The folders to be shared are stored on shared disks. Using the CompositeFileShare agent you can also do the following:

  • Create hidden shares for shared folders or subfolders.

  • Dynamically share the subfolders created after the resource is brought online.

  • Configure and control existing shares.

The CompositeFileShare agent enables sharing folders shared outside VCS. However, you cannot add special shares (those created by the operating system for administrative and system use) to the VCS configuration. For example, you cannot add the shares ADMIN$, print$, IPC$, and DriveLetter$.

The agent simplifies the process of configuring multiple file shares. It defines file shares in an array, thereby eliminating the need to specify dependencies for each FileShare resource. Each CompositeFileShare resource can be configured for a maximum of 50 file shares.

The CompositeFileShare resource depends on the MountV resource. A CompositeFileShare service group also requires a Lanman resource that is dependent on the IP resource.

Dependencies

The CompositeFileShare resource depends on the MountV resource. A CompositeFileShare service group also requires a Lanman resource that is dependent on the IP resource.

The following figure illustrates the dependency.

Figure: CompositeFileShare service group dependency graph

CompositeFileShare service group dependency graph

Note:

In case of a NetApp storage environment, use the NetApp Filer and NetApp SnapDrive agents instead of the VMDg and MountV agents respectively. If you are using Logical Disk Management (LDM) for configuring your storage, use the Mount and the DiskRes agents.

Agent functions

Online

Shares the specified folders with designated permissions.

Offline

Removes the shares for the specified folders.

Monitor

Verifies at least one specified folder is shared with the designated permissions.

State definitions

ONLINE

Indicates at least one specified folder is shared.

OFFLINE

Indicates no specified folder is shared.

UNKNOWN

Indicates the agent could not determine the status of the resource.

Note:

Sharing a folder with a large number of subfolders and enabling the ShareSubdirectories attribute may cause increased failover time and high CPU and memory utilization.

Resource type definition

type CompositeFileShare
static keylist SupportedActions = { ForceControl }
static i18nstr ArgList[] = { "LanmanResName:VirtualName", MaxUsers,
"MountResName:MountPath", HiddenShare, ShareSubdirectories,
HideChildShares, AutoShare, AutoControl, ClientCacheType,
PathAndShareName, UserPermissions, AccessBasedEnumeration,
ShareComment }
str LanmanResName
str MaxUsers
str MountResName
i18nstr UserPermissions{} = { Everyone=READ_ACCESS }
boolean HiddenShare = 0
boolean ShareSubdirectories = 0
boolean HideChildShares = 0
boolean AutoShare = 1
boolean AutoControl = 1
i18nstr PathAndShareName{}
str ClientCacheType = MANUAL
boolean IgnorePermissions = 0
boolean AccessBasedEnumeration = 0
str ShareComment
)

For more information about ForceControl function, See About ForceControl function

Attributes

Table: CompositeFileShare agent required attributes

Required Attributes

Description

LanmanResName

The name of the Lanman resource on which the CompositeFileShare resource depends.

If this attribute is not specified, the agent behavior is as follows:

  • On Windows Server 2008, the FileShare resource faults.

Type and Dimension: string-scalar

MountResName

The name of the MountV resource on which the CompositeFileShare resource depends.

For NetApp storage, this is the NetAppSnapDrive resource name.

In case of Logical Disk Management, this is the Mount resource name.

Type and Dimension: string-scalar

PathandShareName

A list specifying the respective paths and share names of the folders to be shared. If the path of a shared folder is \Documents, and the share name is UserDocs, the attribute value is defined in the configuration file as

{"\\Documents" = "UserDocs"}.

While editing the attribute from the Cluster Manager (Java Console) or the command line, specify a single slash for the shared folder. While editing the configuration file main.cf directly, specify two slashes (\\); for example, \\Documents.

Note:

This attribute can take localized values.

Type and Dimension: string-association

Table: CompositeFileShare agent optional attributes

Optional Attributes

Description

AutoControl

Defines the agent behavior when share properties are modified (either within or from outside VCS) when the FileShare resource is online.

The value 1 indicates that the agent synchronizes the changes made to the share properties with those that were defined while configuring the file share service group in the cluster.

The value 0 indicates that the agent does not synchronize the share properties as per what is defined in the cluster configuration.

If this attribute is set to 0 and the share properties are modified (either within or from outside VCS), the FileShare resource goes into the UNKNOWN state. The changes made to the share properties remain in effect until the resource is in the UNKNOWN state.

To restore the state, you have to take the CompositeFileShare resource offline and bring it online again. When the resource is brought online, the agent restores the share properties as per what is defined in the cluster configuration.

Default is 1.

To make an existing share highly available, the share name and the share permissions in the configuration file must be the same as those for the file share.

Type and Dimension: boolean-scalar

AutoShare

Defines agent behavior when a folder is added to a VCS file share with shared subfolders. The value 1 indicates the agent automatically shares the newly added subfolder in its next monitor cycle. The value 0 indicates the agent does not.

Default is 1.

This attribute is considered only if the attribute ShareSubdirectories is set to 1.

Type and Dimension: boolean-scalar

ClientCacheType

A string that specifies whether the files and programs in the shared folder are cached locally on the client computer when accessed by users. It also specifies how the files are cached. The cached files are then available offline even if users are not connected to the share.

Note:

The agent does not cache the files or programs itself. It sets the value so that the server and client interfaces do the needful.

This attribute can have the following values:

  • MANUAL: Indicates that only the files and programs specified by the users are cached.

  • NONE: Indicates that files and programs from the share are not cached.

  • DOCS: Indicates that all the files and programs that the users open from the share are automatically cached. Files and programs that are not opened are not available offline.

  • PROGRAMS: Indicates that all the files and programs that the users open from the share are automatically cached and are optimized for performance. Files and programs that are not opened are not available offline.

Default is MANUAL.

Type and Dimension: string-scalar

HiddenShare

Defines whether the agent hides the file share. The value 1 indicates the agent hides the file share. The value 0 indicates it does not.

Default is 0.

Note:

To create a hidden share, set the HiddenShare attribute to 1. Do not append the share name with a $ (dollar) sign.

Type and Dimension: boolean-scalar

HideChildShares

Defines whether the agent hides the subfolder shares. The value 1 indicates the agent hides the subfolder shares. The value 0 indicates it does not.

Default is 0.

This attribute is considered only if the attribute ShareSubdirectories is set to 1.

Type and Dimension: boolean-scalar

IgnorePermissions

This attribute has been deprecated.

Please use AutoControl attribute instead.

Type and Dimension: boolean-scalar

MaxUsers

The maximum number of users that can access the file share. Default is null, which indicates access is granted to maximum users allowed on Windows.

If this attribute is set to zero or greater than the maximum users allowed on Windows, access is granted to the maximum users allowed on Windows.

Type and Dimension: string-scalar

ShareSubdirectories

Defines whether the agent shares the subfolders of the file shares defined in the attribute PathAndShareName. Subfolders are shared with their own names, that is, the share name of a subfolder is the same as the subfolder name. If a share with the same name exists, the subfolder will not be shared. However, this does not affect the state of the resource.

The value 1 indicates the agent shares the subfolders. The value 0 indicates it does not.

Default is 0.

Note:

Sharing a folder with a large number of subfolders and enabling the ShareSubdirectories attribute may cause increased failover time and high CPU and memory utilization.

Type and Dimension: boolean-scalar

UserPermissions

The permissions with which the folders are shared for users. The user permissions do not apply to individual file shares. User permissions apply to all file shares that form the CompositeFileShare resource.

The following permissions are associated with the CompositeFileShare resource:

  • FULL_CONTROL: Permission to read, write, create, execute, and delete the resource, and to modify its attributes and permissions.

  • READ_ACCESS: Permission to read, and execute the resource.

  • CHANGE_ACCESS: Permission to read, write, execute, and delete the resource.

  • NO_ACCESS: No access to the resource.

The UserPermissions are specified in the format

'Domain_Name\Username'=Permission.

For example, to give full control to user John who belongs to the domain vcs_domain, the syntax is

'VCS_DOMAIN\\John'=FULL_CONTROL

The domain name and the user name must be enclosed in quotation marks.

Default is {'Everyone' = READ_ACCESS}.

A maximum of 50 users can be configured for each file share. To configure more than 50 users for a file share, configure user groups.

Note that the agent monitors only the users and the permissions that are defined in the VCS configuration.

Note:

This attribute can take localized values.

Type and Dimension: string-association

AccessBasedEnumeration

Defines whether the agent enables the Windows Access-based Enumeration option for the specified file share. The value 1 indicates that the agent enables it and the value 0 indicates that the agent does not.

Default is 0.

Type and Dimension: boolean-scalar

ShareComment

A string that describes the share. Use this attribute to add comments to the compositefileshare resource.

If this attribute is blank, the agent uses the default VCS comment.

Type and Dimension: string-scalar

Sample configuration

CompositeCFS CFS-RES (
Critical = 1
LanmanResName = CFS_SG-Lanman
MountResName = CFS_SG-MountV
UserPermissions = { Everyone = READ_ONLY }
ShareSubdirectories = 1
PathAndShareName = { "\\share2" = share2,
"\\share3" = share3 }
AccessBasedEnumeration = 1
)
IP CFS_SG-IP (
Address = "10.212.100.184"
SubNetMask = "255.255.254.0"
MACAddress @SYSTEM1 = "00-02-B3-AD-CE-E4"
MACAddress @SYSTEM2 = "00-02-B3-AD-CB-D0"
)
Lanman CFS_SG-Lanman (
VirtualName = VNAME
IPResName = CFS_SG-IP
)
MountV CFS_SG-MountV (
MountPath = "J:"
VolumeName = PS-SPOOL
VMDGResName = CFS_SG-VMDg
)
NIC CFS_SG-NIC (
MACAddress @SYSTEM1 = "00-02-B3-AD-CE-E4"
MACAddress @SYSTEM2 = "00-02-B3-AD-CB-D0"
)
VMDg CFS_SG-VMDg (
DiskGroupName = PRINTSHARE_DG
DGGuid = e40b8ab5-88ac-42e3-ae61-cbea3a164af2
)
CFS_SG-Lanman requires CFS_SG-IP
CFS_SG-MountV requires CFS_SG-VMDg
CFS-RES requires CFS_SG-Lanman
CFS-RES requires CFS_SG-MountV
CFS_SG-IP requires CFS_SG-NIC

Legacy ID



id-SF9Y0158467_v68009537


Article URL http://www.symantec.com/docs/HOWTO65819


Terms of use for this information are found in Legal Notices