I have heard that Sharepoint could be the answer to a loosely managed, fast growing file share. I was asked to try and find a solution for a file share which currently houses millions of files, and terabytes of data using Sharepoint. I see a number of huge challenges with this exercise if we use Sharepoint, and causing many questions.Â
Should we import the documents into the database, should we use RBS, should the files stay on the file share and just import metadata or references? How would that happen? What type of storage, how would you set up the content databases? Would you use multiple drives? How will this effect backups? Also what is the best way to migrate 10s of millions of files?Â
We would probably want to eliminate duplicates, keep versions, and store meta-data for easy searching.
Does anyone have any experience, ideas or suggestions regarding this type of process being managed in Sharepoint? Are there any third party applications that make sense? Has anyone actually done something like this before.
Thanks in advance for your help.Â
Vikki McCormick
Hi Vikki,
It’s a difficult question to answer based on your story. My experience with replacing SharePoint for a fileshare (it’s for from an user perspective):
– Do not just import a fileshare into SharePoint
– Use META data; duhhh
– Buy a tool. I used Metalogix a lot for importing a lot of files into SharePoint
– Online? Think about the uploadtime. You can’t just upload TB’s in an afternoon
– I always call it: “What’s in it for me?”. The question needs an answer for every user, why SharePoint is better dan a fileshare… Possiblities: remote access / trashcan / working together in documents / search etc etc
– RBS; think about backup scenario’s.(it’s more difficult) I have used RBS only with big files like video’s
– Plan contentdatabases and site collections structure (broken rights etc)
– Create a great search experience for the user (with refinement)
– Navigation
It’s ‘just’ an other way of work for you users with a great impact!
