Requests an immediate update of replicas of a read/write DCE LFS fileset that uses Scheduled Replication
Synopsis
fts update -fileset {name | ID} {-all | -server machine} [-cell cellname]
[{-noauth |
-localauth}] [-verbose] [-help]
Options
-fileset {name | ID}
Specifies the complete name or fileset ID number of the read/write fileset whose replicas are to be updated immediately. For a fileset
that uses Scheduled Replication, the command updates the indicated replicas to match the read/write version of the fileset. For a fileset that uses Release Replication, the command updates the
replicas to match the read-only version that resides at the same site as the read/write version of the fileset.
-all
Specifies that all replicas of the fileset indicated with the -fileset option are to be updated. Use this option or use the -server option.
-server machine
Names a specific File Server machine on which the replica of the fileset indicated with the -fileset option is to be updated. Only the replica
on the specified File Server machine is updated. Specify the machine's DCE pathname, its host name, or its IP address. Use this option or use the -all option.
-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 update command asks the Replication Server to make an immediate update of replicas of the read/write DCE LFS fileset specified with the
-fileset option. The effect of the command depends on whether the fileset to be updated uses Scheduled or Release Replication, as follows:
· For a fileset that uses Scheduled Replication, the command directs the Replication Servers on the indicated File Server machines to perform an immediate update based on the read/write version of the fileset. The Replication Servers ignore the value of the MinRepDelay parameter associated with the fileset; they immediately begin updating the replicas to match the version of the read/write fileset that exists at the time the command is issued.
· For a fileset that uses Release Replication, the command directs the Replication Servers on the indicated File Server machines to perform an immediate update based on the read-only replica that is stored on the same File Server machine as the read/write fileset (the replica that was created when the fts release command was last used for the fileset). The command does not first update the read-only replica on the read/write fileset's File Server machine. Because the MinRepDelay parameter does not apply to a fileset that uses Release Replication, the replicas should already be updated to match the replica on the read/write fileset's machine; the command should have no effect.
To indicate the replicas of the specified fileset that are to be updated, use the command's -all or -server option as follows:
· To update all replicas of the specified fileset, use the -all option.
· To update the replica stored on a specific File Server machine, identity the machine with the -server option.
Note that, as with releasing a new version of a fileset that uses Release Replication, forcing an update of a fileset that uses Scheduled Replication does not ensure immediate access to data in the new version of the replica. A Cache Manager continues to provide data cached from the old version of the replica until the MaxAge for the fileset expires or until the Cache Manager needs to access data from the replica that it has not already cached.
To gain immediate access to data in the new version of the replica, issue the cm flush or cm flushfileset command to flush the old data from the cache. This forces the Cache Manager to replace data it has cached from the replica. Replication Servers begin replication in parallel; however, until all replicas have been updated, you cannot directly force the Cache Manager to access data from the new version of the replica.
The fts update command does not change the replication type and parameters defined for the specified fileset. Before the fts update command can be used, the fts setrepinfo command must be used to define the replication parameters for the read/write fileset. The fts addsite command must also be used to define at least one replication site for the read/write fileset.
Use the fts lsreplicas command to check the status of replicas of the fileset. Use the fts statrepserver command to check the status of the Replication Server on a File Server machine.
Privilege Required
No privileges are required.
Examples
The following command requests an immediate update of the replica of the read/write fileset named pmax_osf1.bin at the replication site defined on the File
Server machine named fs3:
$ fts update pmax_osf1.bin /.../abc.com/hosts/fs3
Related Information
Commands: cm flush(8dfs)