Hi,
Normally, the reason a file is not downloaded from Replica A (presumably set in your user preferences?) is because the exact iteration of the file does not exist on Replica A and hence it has to be pulled from elsewhere.
For example, someone at a site with a different Replica B, or someone at the Master site, may have checked in a later iteration of the file to what is on Replica A. This latest file then might only exist on the Replica B (if it has not been Sync'd back to the Master) or on both the Master and Replica B (if it has been Sync'd). It is not until the next Replication schedule that includes a rule for this file, or until someone with Replica A set downloads the file that it actually gets transferred to Replica A for later use.
There are two distinct operations for Replica's -
- Syncing where data mastered on the Replica is copied back to the Master site - this runs by default every 3 hours, but can be tuned down to 1 hour with JConsole.
- Replication where Rules/Schedules control what data is sent out to the Replica's from the Master site - these can be predictive recently but are most often schduled (we do early morning & lunchtime)
Hence, I presume that you have created and run a replication rule & schedule to replicate the file you are testing to the Replica you are testing the download from?
It's possible to set a Replica's proximity to other replica's so that data for one replica is pulled from another Replica that is closer to it rather than the Master. ie you could have a Master site that Replicates to Replica A and then there is a further hop away from the Replica A to a Replica B. The data has to have Replication Rules & Schedules to ensure that data that is needed to be replicated to Replica B is available to replicate from Replica A, otherwise it will have to come from the Master site.
Rgds
Gary
