NAME

fts − Introduction to the fts command suite

OPTIONS

The following options are used with many fts commands.  They are also listed with the commands that use them. 

−fileset {name | ID}
Specifies the fileset to use with the command. You can specify either a fileset name or a fileset ID.

−server machine
Specifies the File Server machine to use with the command. This option is typically used to provide the name of the File Server machine on which the fileset or filesets to use with the command reside. You can use any of the following to specify the File Server machine:

•The machine’s DCE pathname (for example, /.../abc.com/hosts/fs1)

•The machine’s host name (for example, fs1.abc.com or fs1)

•The machine’s IP address (for example, 11.22.33.44)

−aggregate name
Specifies the device name, aggregate name, or aggregate ID of the aggregate or partition to use with the command. These identifiers are specified in the first, second, and fourth fields of the entry for the aggregate or partition in the dcelocal/var/dfs/dfstab file.

−cell cellname
Specifies that the command is to be run with respect to the cell named by the cellname argument. By default, commands are executed in the local cell of the issuer of the command.

−noauthDirects the fts program to use the unprivileged identity nobody as the identity of the issuer of the command. Generally, the −noauth option is included with a command if DFS authorization checking is disabled on a server machine on which administrative privilege is required or if the Security Service is unavailable. If DFS authorization checking is disabled, DFS processes require no administrative privilege to issue any command; any user, even the identity nobody, has sufficient privilege to perform any operation. If the Security Service is unavailable, a user’s security credentials cannot be obtained.  DFS authorization checking is disabled with the bos setauth command or by including the −noauth option when the bosserver process is started on a machine. DFS authorization checking is typically disabled

•During initial DFS installation

•If the Security Service is unavailable

•During server encryption key emergencies

•To view the actual keys stored in a keytab file

Include the −noauth option with a command that requires administrative privilege only if DFS authorization checking is disabled on the necessary machines. A command that requires administrative privilege fails if the −noauth option is included and DFS authorization checking is not disabled. If you use this option, do not use the −localauth option. 

−localauthDirects fts to use the DFS server principal of the machine on which the command is issued as the identity of the issuer. Each DFS server machine has a DFS server principal stored in the Registry Database. A DFS server principal is a unique, fully qualified principal name that ends with the string dfs-server; for example, /.../abc.com/hosts/fs1/dfs-server. (Do not confuse a machine’s DFS server principal with its unique self identity.)  Use this option only if the command is issued from a DFS server machine. You must be logged into the server machine as root for this option to work.  If you use this option, do not use the −noauth option. 

−verboseDirects the fts program to provide detailed information about its actions as it executes the command. This is useful mainly for debugging or trace purposes. The amount of additional information displayed when the −verbose option is specified varies for different commands. 

−helpPrints the online help for the command. All other valid options specified with this option are ignored. For complete details about receiving help, see the dfs_intro(1m) reference page. 

DESCRIPTION

Most commands in the fts command suite are administrative-level commands used only by system administrators to contact the Fileset Server and the Fileset Location Server (FL Server). (The primary exception is the fts lsquota command, which is also issued by users to determine the quota of filesets with which they work.) Commands in the fts suite are used to instruct the Fileset Server to create and delete filesets, as well as to move, replicate, and back up filesets. The FL Server automatically records in the Fileset Location Database (FLDB) any changes in fileset status and fileset location resulting from fts commands.  If the execution of an fts command is interrupted by a server or a process failure, subsequent execution of the command continues at the interruption point rather than at the beginning of the operation. Therefore, before executing a command, the Fileset Server and the FL Server verify that running the command has an effect. If the desired end-state already exists, the command is not executed; if the end-state does not yet exist, the command continues as necessary to achieve it.  If the issuer explicitly interrupts a fileset operation with an interrupt signal, the fileset is locked. The issuer must unlock it with the fts unlock command before proceeding. 

DCE Local File System

The DCE Local File System (DCE LFS) is a high-performance, log-based file system. It supports the use of DCE LFS aggregates, which are physically equivalent to standard UNIX disk partitions but also contain a specialized log of metadata about the structure and location of information they house.  DCE LFS aggregates, in turn, support the use of DCE LFS filesets.  DCE LFS filesets are hierarchical groupings of files managed as a single unit. They can vary in size but are almost always smaller than a disk partition. As a result, multiple DCE LFS filesets can be stored on a single aggregate. Non-LFS filesets occupy the entire partition on which they reside.  Because of the differences between DCE LFS and non-LFS filesets, the following fts commands function only with DCE LFS filesets. Refer to the appropriate command reference pages for more information about the functionality provided by these commands. 

•fts addsite(1m)

•fts clone(1m)

•fts clonesys(1m)

•fts create(1m)

•fts delete(1m)

•fts lsreplicas(1m)

•fts move(1m)

•fts release(1m)

•fts rmsite(1m)

•fts setquota(1m)

•fts setrepinfo(1m)

•fts statrepserver(1m)

•fts update(1m)

•fts zap(1m)

Fileset Location Database Information

The Fileset Location Database (FLDB) is maintained by the Fileset Location Server (FL Server). A master copy of the FLDB is stored on one Fileset Database machine, with copies synchronized on other Fileset Database machines via the Ubik library of facilities. It is essential that the information in the FLDB correspond to the status of the filesets on the File Server machines.  Therefore, any fts command that affects fileset status also changes the corresponding FLDB entry automatically. If an fts operation is interrupted before completion, information in the FLDB can differ from information on a File Server machine. In these cases, the fts syncfldb and fts syncserv commands must be used to align the information.  There is an entry in the FLDB for each read/write DCE LFS and non-LFS fileset.  Each entry for a DCE LFS fileset also records information about the read-only and backup versions of the fileset, because these versions do not have their own entries. The information in an FLDB entry includes the fileset’s name and fileset ID number, the ID numbers of its read-only and backup versions (if it is a DCE LFS fileset), site definitions, site counts, and status flags.  Complete details about the FLDB are included in Part 1 of the . 

Fileset Header Information

A separate fileset header is stored at the site of each copy of a DCE LFS fileset, regardless of its type (read/write, read-only, or backup). The data structure of the fileset header records the physical memory addresses of the files in the fileset on the partition on which the fileset is stored. The fileset header binds all the files into a logical unit without requiring that they be stored in contiguous memory blocks.  The header of a DCE LFS fileset includes the following information: the fileset’s name; its fileset ID number; its type (read/write, read-only, or backup); its size; the ID numbers of its parent, clone, and backup versions; its creation date; and the date of its last modification. 

Cautions

Specific cautionary information is included with individual commands. 

Receiving Help

There are several different ways to receive help about DFS commands. The following examples summarize the syntax for the different help options:

$ man ftsDisplays the reference page for the command suite. 

$ man fts_command
Displays the reference page for an individual command. You must use an _ (underscore) to connect the command suite to the command name. Do not use the underscore when issuing the command in DFS.

$ fts helpDisplays a list of commands in a command suite. 

$ fts help command
Displays the syntax for a single command.

$ fts apropos -topic string
Displays a short description of any commands that match the specified string.

Consult the dfs_intro(1m) reference page for complete information about the DFS help facilities. 

Privilege Required

Most fts commands can be issued by users included in either the admin.ft file or the admin.fl file. Some commands require that the issuer be included on both lists; some commands also require that the user have certain permissions for a file or directory. Specific privilege information is listed with each command’s description. 

RELATED INFORMATION

Commands: dfs_intro(1m), fts addsite(1m), fts aggrinfo(1m), fts apropos(1m), fts clone(1m), fts clonesys(1m), fts create(1m), fts crfldbentry(1m), fts crmount(1m), fts crserverentry(1m), fts delete(1m), fts delfldbentry(1m), fts delmount(1m), fts delserverentry(1m), fts dump(1m), fts edserverentry(1m), fts help(1m), fts lock(1m), fts lsaggr(1m), fts lsfldb(1m), fts lsft(1m), fts lsheader(1m), fts lsmount(1m), fts lsquota(1m), fts lsreplicas(1m), fts lsserverentry(1m), fts move(1m), fts release(1m), fts rename(1m), fts restore(1m), fts rmsite(1m), fts setquota(1m), fts setrepinfo(1m), fts statftserver(1m), fts statrepserver(1m), fts syncfldb(1m), fts syncserv(1m), fts unlock(1m), fts unlockfldb(1m), fts update(1m), fts zap(1m) Files: admin.fl(4), admin.ft(4), dfstab(4)

Hewlett-Packard Company  —  OSF DCE 1.1/HP DCE 1.5