Each directory in /.../cellname/fs usually corresponds to a separate, mounted fileset (mounted filesets can also occur anywhere in the file tree). Subdirectories of /.../cellname/fs/directory_name can be either standard directories or mount points to separate filesets. For simplified administration, group the directories and their contents into small, easily managed filesets.
Each fileset has a name unique to the cell in which it resides. Fileset names are stored in the FLDB. A fileset's name is not the same as the name of its mount point, although you can assign the same name to a fileset and its mount point.
There is a 111-character limit on the length of fileset names. However, because a nine-character .readonly extension is added when you replicate a fileset, you need to specify fileset names that contain no more than 102 characters. When creating filesets, do not add the .readonly and .backup extensions yourself; DFS automatically adds the appropriate extension when it creates a read-only or backup fileset. (DFS reserves the .readonly and .backup extensions for use with read-only and backup filesets, so you cannot create a fileset whose name ends with either of these extensions.)
You can give filesets any names that you feel are appropriate. For simplified administration, however, a fileset's name needs to
· Reflect the fileset's contents
· Reflect the name of the fileset's mount point
· Be consistent with other filesets that contain similar types of data so that you can easily manipulate groups of filesets when using the DFS Backup System
You may find it helpful to use a common prefix for related filesets. The following list summarizes this type of naming scheme:
· Use the common.type prefix for common filesets. For example, use common.etc for common configuration files (mounted at /.../cellname/fs/common/etc), and common.forms for common forms (mounted at /.../cellname/fs/common/forms).
· Use the src.type prefix for source filesets. For example, use src.dfs for DFS source files (mounted at /.../cellname/fs/src/dfs).
· Use the user.username prefix for all user filesets. For example, use user.terry for user terry's fileset (mounted at /.../cellname/fs/usr/terry).
· Use the public.username prefix for each user's public fileset. For example, use public.terry for terry's public fileset, which contains information the user wants to make available to everyone. The public.terry fileset is mounted at /.../cellname/fs/public/terry.
· Use the sys_type.distribution_dir prefix for operating system-specific filesets. For example, use pmax_osf1.bin for OSF/1 binary files (mounted at /.../cellname/fs/pmax_osf1/bin), and pmax_osf1.lib for OSF/1 library files (mounted at /.../cellname/fs/pmax_osf1/lib). In DFS, symbolic links are often created from the /bin and /lib directories (or their equivalents) on the local disk of a workstation to these DFS mount points.
(See Making Filesets and Aggregates Available for more information on additional rules for naming filesets.)