Link to home
Start Free TrialLog in
Avatar of ITPro44
ITPro44Flag for United States of America

asked on

File Server Storage Planning

I am planning a large file server and I would like your advice and suggestions.  We currently have 4TB of data and I anticipate, based on growth history, we will grow to 25TB within the next 5 years. I am planning our storage infrastructure for this.  Our files are 95% .jpg files and 5% word documents, excel docs and other misc. documents.  We have 2 servers.  One in building A and one in Building B (DR Site) that are connected via GB LAN.  The plan is to replicate the data from serverA to ServerB using DFSR.  This will provide high availability in the event of a failure on ServerA.  We also have a 3rd server in buildingB that is a DPM2010 server which will backup this data.

I am trying to decide between to options and would like to know your input and advise.

Option 1:  Split our data into 4 volumes and then grow those volumes over time by adding storage and spanning each disk as necessary.

Option 2:  Put all data on the same volume and grow that one volume over time by adding storage and spanning the disk.

 Taking into account our scenario, which decision do you recommend and why?
Avatar of Matt V
Matt V
Flag of Canada image

Disk volumes generally have performance issues (if not compatibility issues) around 2TB.  I would suggest you examine how much of your data is accessed on a regular basis and consider tiered storage where you would put "in use" files (determined by last access date) on the faster media, and migrate the older files to slower cheaper storage in whichever array will work.
You may wish to consult with HP/Dell/IBM (whomever you are using for storage) on this type of setup.
You would defiantely see better performance on the files that are frequently accessed.  
Avatar of ITPro44

ASKER

thanks Matt, that is a good suggestion.  At this point in time our hardware has been purchased and we are invested in the current infrastructure described above.  I think this will be something we consider next time this project rolls around.

You mentioned that volumes have performance and possibly compatibility issues around 2TB.  Can you expand on your knowledge of this?
ASKER CERTIFIED SOLUTION
Avatar of Matt V
Matt V
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ITPro44

ASKER

I do not plan to boot from this partition is will be for data only.  Have you, or is there anyone else who has had experience with 20TB+ volumes that can provide me with some guidance or best practices for configuring and managing large volumes?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ITPro44

ASKER

:)  What is your reasoning for storing it in 2TB chunks?
Vmware limitation on storage luns.
Avatar of ITPro44

ASKER

gotcha.  Do you span your volumes or use something like DFS?
Currently we do not have any volumes larger than 1.5TB, so we have been lukcy.  Ask me next year though and I might have a different answer.
Avatar of ITPro44

ASKER

Thanks for your help.