Centera Collections\Staging

The Size of the storage for the staging of the Collections does not need to be vast.

In my environment I have them on the same drive as my Indexes just in a different directory. Depending on what you are archiving i see no need for the space to be more that a GB. I have never seen my collections grow to more than a 200MB.

The only reason why this would grow is that if there was an issue writing to the centera because once the collection reaches 100 files or 10MB at that point it is sent to Centera to be stored.

thanks for the help, guys.  Is there a link to that whitepaper??  I couldnt find it.

I have another question regarding the Centera.  I am working on a solution where we'll be migrating 1TB worth of journaled mail data to Centera stroage, and then enabling mailbox archiving.  I understand that our storage footprint should theoretically never be larger than our journaled mail, as mailbox/journalling have the same retention periods and should be single instanced (using same Centera pool).

I was considering creating 2 separate vault stores/partitions, but does it makes sense to create separate vault stores/partitions for these tasks??  Is there any performance issues surrounding using a single Centera partition?? 

I cannot understand why the other post was marked as the solution! Unless a Gb is several days email, and every company has the same amount of data archived over several days. The information I supplied wa direct from a whitepaper. I have posted this to try and ensure others asking the same question realize this. The reason to allow for several days worth is to build in some fault tolerance if there is any issue with collections.