The following topics describe how to
· Use Release Replication to replicate a fileset. You issue the fts release command to release a new replica of a fileset on the same File Server machine as the read/write version of the fileset. The Replication Servers at the fileset's other replication sites then update the replicas at their respective sites to match the replica on the read/write fileset's machine.
· Use Scheduled Replication to replicate a fileset. Although Scheduled Replication is automatically performed according to the replication parameters you define, you can use the fts update command to request an immediate update of all replicas of a fileset or of only the replica at a given site. The Replication Servers at the specified replication sites immediately begin to update their respective replicas to match the version of the read/write fileset that exists at the time the command issued. The Replication Servers ignore the MinRepDelay parameter associated with the fileset.
Using the fts release or fts update command does not guarantee immediate access to data in the new version of a 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.
Moreover, the fts release and fts update commands direct the Replication Servers at a fileset's replication sites to begin updating the replicas stored at their sites. The Replication Servers begin updating the replication sites in parallel. (This does not mean, however, that all replicas will complete their updates at the same time.)
Replicas are updated even if shared byte-range locks exist against data within the replica. Shared byte-range locks are granted by DFS to provide compatibility with applications that require them. However, such locks are not honored by DFS during the replica update process.
To attempt to gain immediate access to data in the new version of a replica, issue the cm flush or cm flushfileset command to flush the old data from the cache. These commands force the Cache Manager to discard and, as necessary, replace data it has cached from the replica. Until all replicas have been updated, you cannot directly force the Cache Manager to access data from the new version of the replica.
The operations described in the following topics assume that the preparatory steps described in Preparing for Replication have all been performed.
More:
Using Release Replication to Create Read-Only Filesets
Using Scheduled Replication to Create Read-Only Filesets