Synchronizes FLDB entries to match their fileset headers
Synopsis
fts syncfldb -server machine [-aggregate name] [-cell cellname] [{-noauth | -localauth}]
[-verbose] [-help]
Options
-server machine
Names the File Server machine from which to compare filesets to entries in the Fileset Location Database (FLDB). Specify the File Server machine using
the machine's DCE pathname, the machine's host name, or the machine's IP address.
-aggregate name
Specifies the device name, aggregate name, or aggregate ID of the aggregate or partition on -server for which to compare filesets to FLDB
entries. 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. Do not use this
option under normal circumstances; omitting it allows synchronization of all filesets on -server. Use it only when just a single aggregate needs to be synchronized.
-cell cellname
Specifies the cell where the command is to be run. The default is the local cell of the issuer of the command.
-noauth
Directs fts to use the unprivileged identity nobody as the identity of the issuer of the command. If you use this option, do not use the
-localauth option.
-localauth
Directs fts to use the DFS server principal name of the machine on which the command is issued as the identity of the issuer. Use this option only if the
command is issued from a DFS server machine (a machine that has a DFS server principal in the local Registry Database). 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 fts to provide detailed information about its actions as it executes the command.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The fts syncfldb command inspects the fileset header of each online fileset that resides on a specified File Server machine (or, optionally, a specified
aggregate or partition on that File Server machine). The command then checks that each FLDB entry is consistent with its fileset header. If the command encounters an inconsistency between a fileset
header and its FLDB entry, the FLDB entry is changed to reflect the information in the fileset header. If the command encounters an FLDB entry without a corresponding fileset header, it deletes the
FLDB entry; if the command encounters a fileset header without a corresponding FLDB entry, it creates an FLDB entry for that fileset.
The fts syncfldb command also performs the following additional functions:
· If it finds a backup fileset whose read-write source no longer exists at the same site, it displays a warning message.
· If it finds a fileset ID number that is larger than the value of the counter used by the FL Server when allocating fileset ID numbers, it records this ID number as the new value of the counter. The next fileset to be created receives a fileset ID number one greater than this number.
· If necessary, it increments or decrements the number of fileset entries recorded as residing on a File Server machine in the FLDB entry for the server.
The fts syncfldb command checks either all of the fileset headers on the File Server machine specified with the -server option or only the filesets on the optional partition or aggregate specified with the -aggregate option. The command checks a fileset header only if the fileset is marked as being On-line. If the command encounters a busy fileset on an aggregate, it exits without checking any other filesets. (A busy fileset is one upon which a fileset-related operation such as a move, clone, or release is currently being performed.)
It is recommended that the fts syncfldb command be run on all File Server machines in a cell before the fts syncserv command is run on the File Server machines in the cell. However, nothing prohibits the commands from being executed in the reverse order or independently of each other.
Note that the fts syncfldb and fts syncserv commands cannot restore replication information lost when the entry for a DCE LFS fileset is removed from the FLDB. Replication information must be reconstructed with the fts setrepinfo and fts addsite commands.
Because non-LFS filesets do not have fileset headers, the fts syncfldb and fts syncserv commands have limited effectiveness on non-LFS filesets. For example, because non-LFS filesets do not have fileset headers, the fts syncfldb command cannot determine the name of a non-LFS fileset that has no FLDB entry. If the command determines that it needs to create an FLDB entry for a non-LFS fileset, it generates a name of the form SYNCFLDB-ADDED-number, where number is a unique number appended to the name to differentiate it from other names of the same type. The fts rename command then needs to be used to rename the fileset to its original name.
Privilege Required
The issuer must be listed in the admin.ft file on each machine that houses a version of any fileset stored at the specified site (-server
and optionally -aggregate). The issuer must also be listed in the admin.fl files on all Fileset Database machines or own the server entry for each machine that houses a version of
any fileset stored at the specified site.
Cautions
The physical disk on which a fileset resides cannot be moved from a machine in one cell to a machine in another cell with the expectation of simply running the
fts syncfldb command to create an FLDB entry for the fileset in the new cell. Any attempt to introduce a fileset from one cell into another cell risks a fileset ID conflict between the newly
introduced fileset and a fileset within the new cell that has the same fileset ID. This conflict causes one of the two conflicting filesets to be inaccessible.
Related Information
Commands: fts addsite(8dfs)
Files: dfstab(4dfs)