Planning For Compatibility Between File Sharing Protocols; Nfs Compatibility Issues; Managing Shares - HP ProLiant 300 Series Administration Manual
Hide thumbs
Also See for ProLiant 300 Series:
- Introduction manual (22 pages) ,
- Troubleshooting manual (194 pages)
Table of Contents
•
Administrative shares are shares with a last character of $. Administrative shares are not included
in the list of shares when a client browses for available shares on a CIFS server.
•
Standard shares are shares that do not end in a $ character. Standard shares are listed whenever
a CIFS client browses for available shares on a CIFS server.
The storage server supports both administrative and standard CIFS shares. To create an administrative
share, end the share name with the $ character when setting up the share. Do not type a $ character at
the end of the share name when creating a standard share.
Planning for compatibility between file sharing protocols
When planning for cross-platform share management on the storage server, it is important to understand
the different protocols and their associated constraints. Each additional protocol that is supported adds
another level of constraints and complexity.
NFS compatibility issues
When planning to manage CIFS and NFS shares, consider two specific requirements.
NOTE:
Further information, including details about the NFS Service and the User Mapping service, is available
in the
"Services for
•
NFS service does not support spaces in the names for NFS file shares.
NFS translates any spaces in an export into an underscore character. Additional translations can
be set up for files. (See the "OEM Supplemental Help" chapter of the SFU help, found on the
storage server). This feature ensures the greatest level of compatibility with NFS clients, because
some do not work with NFS exports that contain a space in the export name.
If you plan to use the same name when sharing a folder through CIFS, and then exporting it
through NFS, do not put spaces in the CIFS share name.
•
NFS service does not support exporting a child folder when its parent folder
has already been exported.
An NFS client can access a child folder by selecting the parent folder and then navigating to the
child folder. If strict cross-platform compatibility is an administration goal, CIFS must be managed
in the same way. Do not share a folder through CIFS if the parent folder is already shared.
Managing shares
Shares can be managed through the Shares tab of the WebUI. Tasks include:
•
Creating a new share
•
Deleting a share
•
Modifying share properties
•
Publishing in DFS (see
100
Folder, Printer, and Share Management
NFS/UNIX" chapter.
"Publishing a new share in
DFS")
Table of Contents
