Sets or changes replication type and parameters for a read/write DCE LFS fileset
Synopsis
fts setrepinfo -fileset {name | ID} [{-release | -scheduled}] [-change] [-maxage interval]
[-failage interval] [-reclaimwait interval] [-minrepdelay interval] [-defaultsiteage interval]
[-clear] [-cell cellname] [{-noauth | -localauth}] [-verbose] [-help]
Options
-fileset {name | ID}
Specifies the complete name or fileset ID number of the read/write source fileset for which the replication type and parameters are to be
set or changed. This command is used to set parameters for either Release or Scheduled Replication.
-release
Specifies that Release Replication is to be used with the fileset indicated with the -fileset option. When initially defining a fileset's replication
parameters, use this option or use the -scheduled option. Afterward, omit both options when modifying the fileset's replication parameters without changing its replication type.
To change a fileset's replication type (from Release to Scheduled, or from Scheduled to Release), include both the -change option and either the -release or -scheduled option to indicate the new type of replication to be used with the fileset.
-scheduled
Specifies that Scheduled Replication is to be used with the fileset indicated with the -fileset option. When initially defining a fileset's replication
parameters, use this option or use the -release option. Afterward, omit both options when modifying the fileset's replication parameters without changing its replication type.
To change a fileset's replication type (from Release to Scheduled, or from Scheduled to Release), include both the -change option and either the -release or -scheduled option to indicate the new type of replication to be used with the fileset.
-change
Specifies that the type of replication currently used with the fileset indicated with the -fileset option is to be changed. Include the -release
option to change the fileset's replication type from Scheduled to Release; include the -scheduled option to change the fileset's replication type from Release to Scheduled.
Omit this option when specifying the -release or -scheduled option to initially set a fileset's replication type. Also omit this option when changing a fileset's replication parameters without changing its replication type.
-maxage interval
Specifies the amount of time the Cache Manager distributes data cached from a read-only replica without attempting to verify that the data is current.
The Replication Server maintains information about the currentness of a read-only replica, which it communicates to the Cache Manager via the File Exporter. For Scheduled Replication, a replica must
remain current with respect to the read/write source fileset; for Release Replication, a replica must remain current with respect to the read-only fileset that resides on the same File Server machine
as the read/write source fileset. The default is 2 hours. An effective value must be greater than or equal to 2 minutes. Applicable to Release and Scheduled Replication.
-failage interval
Specifies the amount of time the Cache Manager distributes data cached from a read-only replica if that data cannot be verified as current. The
difference between FailAge and MaxAge is the amount of time the Cache Manager continues to distribute data cached from a read-only replica after that data cannot be verified as current. The default
is 1 day or twice the MaxAge, whichever is larger. An effective value must be greater than or equal to the MaxAge. Applicable to Release and Scheduled Replication.
-reclaimwait interval
Specifies the amount of time the File Exporter waits before it reclaims storage space from deleted files - those not referred to by a directory
(ReclaimWait). It also determines the frequency of the Cache Manager's keep-alive messages to the Replication Server.
The Cache Manager sends keep-alive messages to indicate that it is still using files on a read-only replica. A file being accessed from a replica remains available as long as the Cache Manager continues to notify the Replication Server that the file is still in use and the Replication Server continues to forward these notifications to the File Exporter. This is true even if the file has been removed from all directories on the read/write fileset in the interim. To prevent the File Exporter from reclaiming storage space occupied by deleted files, the Cache Manager sends keep-alive messages more frequently than the ReclaimWait interval. The default is 18 hours. An effective value must be greater than 2 hours; do not specify a value less than 90 minutes. Applicable to Release and Scheduled Replication.
-minrepdelay interval
Specifies how long the Replication Server waits after a read/write source fileset changes before it attempts to get a new copy of the fileset
(MinRepDelay). The Replication Server tracks the currentness of replicas by maintaining a whole-fileset token for each fileset. If a Cache Manager changes the read/write fileset, the Replication
Server relinquishes its whole-fileset token and waits for at least the time specified by MinRepDelay before requesting a new whole-fileset token. The default is 5 minutes or one-quarter of the
DefaultSiteAge, whichever is smaller. This value must be less than the MaxSiteAge specified for each replication site with the -maxsiteage option of the fts addsite command.
Applicable to Scheduled Replication only.
-defaultsiteage interval
Specifies the default value to be used as the MaxSiteAge for a replication site (DefaultSiteAge). The DefaultSiteAge is used if the
-maxsiteage option is omitted when the fts addsite command is used to add a replication site. The default is one-quarter of the MaxAge. Applicable to Scheduled Replication
only.
-clear
Removes all replication parameters previously defined for the fileset. The options associated with the type of replication in use for the fileset can then be used to
define new replication parameters, or they can all be omitted to allow the system to calculate new replication parameters for the fileset.
-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 setrepinfo command is used to set or change the replication type and parameters for a read/write DCE LFS fileset. It affects the parameters for
both Release and Scheduled Replication. It must be issued before replication sites can be defined for the fileset with the fts addsite command and before the fts release or
fts update command can be used to copy replicas to the replication sites. The replication type and parameters for a fileset are stored in the fileset's entry in the Fileset Location
Database (FLDB).
Use the following guidelines when deciding which type of replication (Release or Scheduled) to use with a read/write fileset:
· Use Release Replication if the fileset seldom changes or if the distribution of replicas must be tracked closely.
· Use Scheduled Replication if having the system release replicas of the fileset at regular intervals is preferred and the distribution of replicas does not need to be tracked.
When initially defining a fileset's replication type, include either the -release or -scheduled option. These options are then omitted from the command unless the replication type for the fileset is being changed (from Release to Scheduled, or from Scheduled to Release). To change the replication type, use the appropriate option (-release or -scheduled) to specify the new type, and include the -change option to indicate that the type is to be changed.
Note that because Release Replication does not require a replication site to have a MaxSiteAge, it is likely that one or more Release Replication sites will have a MaxSiteAge of 0 (zero), which is the default value recorded for a site if no MaxSiteAge or DefaultSiteAge is specified. When changing from Release Replication to Scheduled Replication, the -defaultsiteage option must be used to set a DefaultSiteAge if any replication site does not have a MaxSiteAge and no DefaultSiteAge exists for the source fileset; otherwise, the fts setrepinfo command fails. If the command fails for this reason, reissue it, specifying a DefaultSiteAge with the -defaultsiteage option.
The -maxage, -failage, -reclaimwait, -minrepdelay, and -defaultsiteage options are used to set the corresponding replication parameters for a read/write fileset (see the section on options for information on the replication parameter each option sets). The following table lists each option's default value and describes the dependencies between the different options when they are used to set the replication parameters for either Release or Scheduled Replication.
Replication Parameters
| Parameter | Default | Release Replication | Scheduled Replication |
| -maxage | 2 hours | Required only if -failage is specified. | Required only if one of the following is specified: -failage, -minrepdelay, or -defaultsiteage. |
| -failage | The larger of 1 day or twice -maxage | Optional. If it is specified, the following are required: -maxage and -reclaimwait. | Required only if one of the following is specified: -minrepdelay or -defaultsiteage. |
| -reclaimwait | 18 hours | Required only if -failage is specified. | Required only if one of the following is specified: -failage, -minrepdelay, or -defaultsiteage. |
| -minrepdelay | The smaller of 5 minutes or one-quarter of -defaultsiteage | Not applicable. | Required only if one of the following is specified: -failage or -defaultsiteage. |
| -defaultsiteage | One-quarter of -maxage | Not applicable. | Optional. But if the other options are specified and -defaultsiteage is not, the -maxsiteage option of the fts addsite command is required when defining replication sites for the fileset. |
· The -failage option is specified for Release Replication.
· The -failage, -minrepdelay, or -defaultsiteage option is specified for Scheduled Replication.
Once one of these options is specified, the fts program no longer performs any default calculations; interval must be provided for all applicable options. (The exception is the -defaultsiteage option for Scheduled Replication, which is always optional.) Also, because the -minrepdelay and -defaultsiteage options do not apply to Release Replication, they are recorded if specified but they are ignored.
Enter interval values as integers, using the following abbreviations to indicate units: d for days, h for hours, m for minutes, and s for seconds. The syntax for an interval is
[integer d] [integer h] [integer m] [integer s]
At least one of the four values (days, hours, minutes, or seconds) must be provided, and a unit abbreviation (d, h, m, or s) must be used with any integer. The unit abbreviations can be uppercase or lowercase, and they can be specified in any order. Examples of valid interval values are
3d2H
3M2h
1d6h30m45s
To change the replication parameters defined for a fileset, use the options for the parameters you want to change. To change all replication parameters associated with a fileset, use the -clear option to remove all replication parameters previously defined for the fileset, and use the options for the parameters you want to change to indicate the new parameters. To have the system calculate default values for all replication parameters, use only the -clear option.
Use the fts lsfldb or fts lsft command to display the replication parameters associated with a read/write fileset. Use the fts lsreplicas command to display the statuses of replicas at replication sites. Use the fts statrepserver command to display the status of the Replication Server on a File Server machine.
Note that replication is available in a cell only if the following conditions have been met: root.dfs, the cell's main read/write fileset, is a DCE LFS fileset; root.dfs was mounted with an explicit read/write mount point as a subdirectory of itself (the root.dfs fileset) when the cell was configured; and root.dfs is replicated. Part 1 of the OSF DCE DFS Administration Guide and Reference provides information about configuring root.dfs to support replication.
More: