Hp StoreAll Storage User Manual download pdf (Page 91)

4. Create the new shares on the cluster storage and assign each share the appropriate path. For

example, assign srv1-DATA to /srv1/data, and assign srv2-DATA to /srv2/data.

Because SRV3 originally pointed to the same share as SRV1, we will assign the share

srv3-DATA the same path as srv1-DATA, but set the permissions differently.

5. Optionally, create a share having the original share name, DATA in our example. Assign a

path such as /ERROR/DATA and place a file in it named SHARE_MAP_FAILED. Doing this

ensures that if a user configuration error occurs or the map fails, clients will not gain access

to the wrong shares. The file name notifies the user that their access has failed.

When this configuration is in place, a client request to access share \\srv1\data will be translated

to share srv1-DATA at /srv1/data on the file system. Client requests for \\srv3\data will

also be translated to /srv1/data, but the clients will have different permissions. The client requests

for \\srv2\data will be translated to share srv2-DATA at /srv2/data.

Client utilities such as net use will report the requested share name, not the new share name.

Mapping old share names to new share names

Mappings are defined in the /etc/likewise/vhostmap file. Use a text editor to create and

update the file. Each line in the file contains a mapping in the following format:

VIF (or VhostName)|oldShareName|newShareName

If you enter a VhostName, it will be changed to a VIF internally.

The oldShareName is the user-requested share name from the client that needs to be translated

into a unique name. This unique name (the newShareName) is used when establishing a mount

point for the share.

Following are some entries from a vhostmap file:

99.30.8.23|salesd|q1salesd

99.30.8.24|salesd|q2salesd

salesSrv|salesq|q3salesd

When editing the /etc/likewise/vhostmap file, note the following:

• All VIF|oldShareName pairs must be unique.

• The following characters cannot be used in a share name: “ / \ | [ ] < > + : ; ,

? * =

• Share names are case insensitive, and must be unique with respect to case.

• The oldShareName and newShareName do not need to exist when creating the file; however,

they must exist for a connection to be established to the share.

• If a client specifies a share name that is not in the file, the share name will not be translated.

• Care should be used when assigning share names longer than 12 characters. Some clients

impose a limit of 12 characters for a share name.

• Verify that the IP addresses specified in the file are legal and that Vhost names can be resolved

to an IP address. IP addresses must be IP4 format, which limits the addresses to 15 characters.

IMPORTANT: When you update the vhostmap file, the changes take effect a few minutes after

the map is saved. If a client attempts a connection before the changes are in effect, the previous

map settings will be used. To avoid any delays, make your changes to the file when the SMB

service is down.

After creating or updating the vhostmap file, copy the file manually to the other servers in the

cluster.

Consolidating SMB servers with common share names 91

1 2 ... 86 87 88 89 90 91 92 93 94 95 96 ... 253 254

Comments to this Manuals

No comments

Hp StoreAll Storage User Manual Page 91

Comments to this Manuals

Related products and manuals for Storage Hp StoreAll Storage