Bill Webb | The Logger to HDS sync process is between a single Logger and a single HDS, and is exclusive of the Logger sync process between duplexed Loggers. There is a separate process (replication - rpl or hrpl now, I think) that controls the synchronization of data between a Logger and HDS. So the standard setup for a duplexed Logger and HDS setup is that you have Logger A and HDS "A" set up to replicate, and then Logger B and HDS "B" to replicate. The HDSs know nothing of each other, and have no synchronization between them. This means the situation you describe is entirely possible, that is: both Loggers in "synch" and one HDS in synch, but the other HDS out of synch. It simply means the historical replication between the HDS and the Logger it is synching to has failed somehow. As for the order of replication of the tables, I used to know that, but I think it is pretty simple in theory (like alphabetical by table name), but I also believe it cycles through each table in this order in smaller time chunks until it is fully replicated, then it performs differential synchs using the same method. - Bill |
| Please sign in to flag this as inappropriate. |