The FLDB entry for a read/write fileset records the following replication information for the fileset:
· The ID number of the fileset's read-only version
· The fileset's replication type and parameters
· The definitions for the fileset's replication sites
All read-only copies of a read/write fileset share the same fileset ID number in the FLDB. The number, which is reserved when the read/write fileset is created, is one greater than the ID number of the read/write fileset. The fileset ID number of a read-only fileset's source fileset is referred to as the replica's parent ID number.
When a read/write fileset is first created, the status flag for the read-only version in the fileset's FLDB entry is set to invalid. When the fts addsite command is used to define the fileset's first replication site, the status flag for the read-only version is changed to valid. The change is made because it is assumed that replicas of the fileset will be placed at the replication sites shortly after the sites are defined.
With respect to filesets, a site is a specific File Server machine and aggregate on which the fileset resides. The FLDB can record a maximum of 16 sites for all versions of a fileset combined. A fileset's read/write version and backup version (if it exists) 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 additional replication sites for the fileset; this approach allows you to define up to 16 replication sites. If you choose not to 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. You should define a replication site for any fileset, especially one that uses Release Replication, at the same site as its read/write fileset.