Initiates Release Replication by placing a read-only version of a read/write DCE LFS fileset at the local site
Synopsis
fts release -fileset {name | ID} [-wait] [-cell cellname] [{-noauth | -localauth}] [-verbose] [-help]
Options
-fileset {name | ID}
Specifies the complete name or fileset ID number of the read/write fileset to be replicated locally (cloned if the local replication site
is defined on the same aggregate as the read/write fileset). Once the fileset is replicated locally, the Replication Servers at the fileset's replication sites copy the replica to their sites.
-cell cellname
Specifies the cell where the command is to be run. The default is the local cell of the issuer of the command.
-wait
Directs the command to not terminate (return a prompt) until all replicas are up to date.
-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 release command is used to initiate the replication process for a fileset that uses Release Replication. The command "releases" a new read-only
copy of the DCE LFS fileset specified with the -fileset option. It places the new read-only copy at the local replication site defined on the same File Server machine as the read/write
fileset. The Replication Servers at each of the fileset's replication sites (specified File Server machines and aggregates) then update the copies of the read-only replica at the sites on their
respective machines.
Note that, as with updating a new version of a fileset that uses Scheduled Replication, releasing a fileset that uses Release 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.
Before the fts release command can be used, the fts setrepinfo command must be used to define the replication parameters for the read/write fileset. If Release Replication is to be used, the -release option must be specified with the fts setrepinfo command. The fts addsite command must also be used to define the replication sites for the read/write fileset. For Release Replication, the replication site on the same File Server machine as the read/write fileset must be defined first. The read/write fileset must have at least one replication site defined before the fts release command can be issued. The replication parameters and sites for a read/write fileset are recorded in the fileset's entry in the Fileset Location Database (FLDB).
The fts release command does not alter the replication type and parameters defined for the specified fileset. The command can be used only with a fileset that uses Release Replication; it returns an error if the specified fileset uses Scheduled Replication. The fts update command can be used to request an immediate update of the replicas of a fileset that uses Scheduled Replication.
Use the fts lsreplicas command to check the status of replicas. Use the fts statrepserver command to check the status of the Replication Server on a File Server machine.
Privilege Required
The issuer must be listed in the admin.ft file on the machine on which the source read/write fileset is stored. The issuer must also be listed in
the admin.fl files on all Fileset Database machines or own the server entries for the machine on which the source fileset resides and all machines on which the read-only replicas are to
reside.
Examples
The following command releases (initiates Release Replication for) the fileset named pmax_osf1.bin:
$ fts release pmax_osf1.bin
Related Information
Commands: cm flush(8dfs)