RGB said: > There are probably ways to cut this down in an emergency (a serious > exploit, for example, that needs to be corked in 36 hours or > less at the > client level). Have the primary site push/initiate the rsync to the T1, and the T1 initiate the rsync to T2 in an emergency. T3's are on their own to fetch from T2's. That should have an incredible boost in how quickly packages get to the T3's and then to the end node. Of course if the T1's & T2's are set up properly, would it really hurt that much to do an rsync pull up the chain every hour or two? Assuming that the deltas are pretty small, that should be a pretty low overhead transaction, no?
