multiple fileStore implementation?

[aweber1nj]

Besides the CachingStore and ReplicatedStore models, which basically define one overall store and manage copying the content, is there a way to define multiple fileStores to the repo such that content in a previously defined store is still accessible when you add a second?

For example, say you've got a business rule where a volume can't exceed 500GB (due to backup/restore time constraints or something).  Can you incrementally add additional volumes as newly named stores as needed?  I'm not clear on how you would configure these stores in parallel.

Would you add additional elements within the store-element of the contentService bean?  How would Alfresco know which store to request the content from?

Thanks,
AJ

[mrogers]

Alfresco enterprise has policy driven storage.   I think you could use that.

[mrogers]

Or you could use some sort of disk management software which maps drives and folders.

[aweber1nj]

OK, so if I install Alfresco 4.0, test out the basics to ensure it's working properly.  I store a few pieces of content, etc.

Then I want to test CachingStore to see if it meets my needs – or even if I'm then installing it in production after "initial repo checkout" – what happens to all the content in the default fileStore once I've basically replaced the fileStore bean with the Caching Store?

It suddenly becomes inaccessible?  If you want to use CachingStore or CloudStorage, you have to configure it before you startup the repository for the first time, otherwise you're likely to lose content (technically you'd know where it is, but it would be inaccessible)?

How do we work that?

-AJ