Adds a replication site for a read/write DCE LFS fileset
Synopsis
fts addsite -fileset {name | ID} -server machine -aggregate name [-maxsiteage interval]
[-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 site is to be added.
-server machine
Names the File Server machine on which the replica is to be stored. Specify the File Server machine using the machine's DCE path name, 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 on which the replica is to be stored. These identifiers are specified in
the first, second, and fourth fields of the entry for the aggregate in the dcelocal/var/dfs/dfstab file.
-maxsiteage interval
Specifies the maximum amount of time that the replica to be stored at the site can be out of date (MaxSiteAge). The Replication Server
attempts to keep the replica current within this amount of time. If this option is omitted, the DefaultSiteAge for the read/write site is used as the value for the MaxSiteAge.
This option must be specified if the DefaultSiteAge was not defined for the read/write fileset (if the -defaultsiteage option was omitted when the fts setrepinfo was used
to set the replication parameters for the read/write fileset).
Use this option only with Scheduled Replication. The MaxSiteAge of a replication site is ignored if Release Replication is used.
-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 addsite command defines a replication site for the read/write DCE LFS fileset specified with the -fileset option. A replication site is a
File Server machine and aggregate where a read-only replica of a read/write fileset is to be stored. The command also increments the number of fileset entries recorded as residing on the File Server
machine specified with the -server option in the Fileset Location Database (FLDB) entry for the server.
A fileset's replication sites are recorded in the FLDB entry for the fileset. If this is the first replication site defined for the fileset, the status flag for the read-only version of the fileset is changed to valid in anticipation of the creation of a read-only fileset at the site.
Enter this command once for each replication site to be defined for a read/write fileset. Before this command is issued, the fts setrepinfo command must be used to set the replication parameters for the read/write fileset and a server entry must exist in the FLDB for the File Server machine specified with the -server option.
If Release Replication is used with the fileset, the first site defined with this command must be on the same File Server machine as the read/write, source fileset. If it is on the same aggregate as the source fileset, it is created as a clone of the source. Because it is created as a clone fileset, which has the same structure as a backup fileset, it shares data with the read/write fileset; therefore, it requires potentially much less space than a full read-only fileset created on a different aggregate.
A File Server machine can house only a single read-only version of a given read/write fileset. The command fails if an attempt is made to define a second replication site for a given fileset on the same File Server machine. Also, the File Server machine that houses a replication site must reside in the same cell as the read/write fileset for which the replication site is defined.
The FLDB entry for a read/write fileset records the locations of the fileset's replication sites; the server machine on which a site is defined must have a server entry in the FLDB that records the entry for the read/write fileset.
The FLDB can record a maximum of 16 sites for all versions of a fileset combined, a site being a specific File Server machine and aggregate. The read/write version and backup version (if it exists) of a fileset share a single site definition. If you define a replication site for a fileset at the same site as its read/write and backup versions, you can then define 15 more replication sites for the fileset; this approach allows you to define up to 16 replication sites. If you do not place a replica of a fileset at the same site as its read/write and backup versions, you can define a maximum of 15 replication sites for the fileset.
The -maxsiteage option is used to define the MaxSiteAge for the site, which is the maximum amount of time the replica at the site can be out of date. The Replication Server always attempts to copy the latest version of the fileset to the site before the MaxSiteAge expires. Use the -maxsiteage option only if Scheduled Replication is used with the source fileset; the MaxSiteAge is ignored if Release Replication is used.
The DefaultSiteAge associated with the read/write fileset is used by default if the -maxsiteage option is omitted. The -maxsiteage option is required with the fts addsite command if the -defaultsiteage option was omitted when the fts setrepinfo command was used to define the replication parameters for the read/write fileset.
If Release Replication is used, the fts release command must be used to place a read-only replica at the replication site defined on the same File Server machine as the source fileset. The Replication Servers at the fileset's other replication sites then copy the replica to the sites on their respective machines. If Scheduled Replication is used, the Replication Servers at the replication sites automatically copy the source fileset to their sites. Immediate updates to sites using either type of replication can be forced with the fts update command.
Use the fts aggrinfo command to check the available space on an aggregate before adding it as a replication site. (Use the fts lsft command to check the size of the read/write fileset.) Use the fts rmsite command to remove a replication site and to instruct the Replication Server to remove the replica stored at the site. Use the fts lsreplicas command to determine the status of the read-only replica at a site.
Privilege Required
The issuer must be listed in the admin.fl files on all Fileset Database machines or must own the server entry for each machine on which a version of
the source fileset specified with the -fileset option resides.
Examples
The following command defines a read-only site for the fileset rs_aix32.bin. The site is defined as the aggregate whose device name is /dev/lv01 on
the File Server machine named fs3.
$ fts addsite rs_aix32.bin /.../abc.com/hosts/fs3 /dev/lv01
Related Information
Commands: fts lsreplicas(8dfs)
Files: dfstab(4dfs)