I do have it set to incremental but I do believe my fix might be an easy one. We have repositories all over the world and I noticed the replication order followed the order of repositories in the sitelst. The issue I'm really having is with a site on the west coast that is low on the list. This means that all the clients from that site come here for most of their work day and never really use the repository since it's disabled due to replication process.
Is it safe to say that I can change the order at which these repositores get replicated by moveing those US repository higher on the list? I noticed there was a DB\SiteList.XML and a DB\SiteMgr.xml. Would i need to edit both of these?
Hmm, I wonder if there is a way to update repositories in parallel? Instead of a single replication task that updates all repositories one after another, perhaps create multiple repository replication tasks all set to run at the same time that each update a smaller number of repositories?
The repository list does automatically get updated in parallel - for about 6 at a time per processor - regarding the "two versions" of the DAT files - I believe those are for differnet engine versions so if you've upgraded all your clients to the 5300 engine then I think it should reduce to one file.
If you search the KB, you can find info about updating from the V2 source repositories, which will only load the new format DAT files, thereby reducing the size of the DAT by roughly half. You can only do this if you have products that can use the V2 DAT. One link to some info about the V2 DAT is here:
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.