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 path name (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.
-noauth
Directs 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.
-localauth
Directs 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.
-verbose
Directs 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.
-help
Prints 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(8dfs) 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.
More:
Fileset Location Database Information