http://docs.splunk.com/Documentation/Splunk/6.2.3/Indexer/Automatearchiving
This had the info I was looking for. Your link got me there though. Thanks ChrisG!
Indexer clusters contain redundant copies of indexed data. If you archive that data using the techniques described above, you archive multiple copies of the data.
For example, if you have a cluster with a replication factor of 3, the cluster stores three copies of all its data across its set of peer nodes. If you set up each peer node to archive its own data when it rolls to frozen, you end up with three archived copies of the data. You cannot solve this problem by archiving just the data on a single node, since there's no certainty that a single node contains all the data in the cluster.
The solution to this would be to archive just one copy of each bucket on the cluster and discard the rest. However, in practice, it is quite a complex matter to do that. If you want guidance in archiving single copies of clustered data, contact Splunk Professional Services. They can help design a solution customized to the needs of your environment.
... View more