We are looking at the possibility of migrating 2TB+ worth of data from our network driving into SharePoint for a department site. For this question I'm assuming all data is valid and has the ability to be assigned to a custom content type and be given basic metadata.
If we did this, we would need to split the data between multiple site collections / content databases but ideally the user experience would be fairly seamless. Key functionality: - Users will be collaborating on about 5% of the content at any one time but we don’t currently have a way of determining what would be considered collaborative content and what would be classified as a record. Technically we do but I don’t believe the business is willing to do that on a document by document basis.
- Users can browse to their content
- Users can search for their content
- As more content is added we will need to add additional content databases. Existing content may need to be moved to those content databases but the experience should stay constant. I.e., I’m trying to avoid the scenario of documents used to be in SiteA/DocLib1 but now you have to go to SiteB/DocLib1.
What concepts / whitepapers should be researched in order to evaluate this?