Volume Mounts vs Directory Junction

Hi there, I am bulding a 2008 R8 Fiel server as a VMware VM. the aggregate data being managed by this FS is failry large - about 5.5TB. It is a mix of Video, Photo, Music and other file data.
I need to break up the volumes in order to keep the VMDKs at a manageable size (< 1TB, so the DSs can stay at 4MB blocksize), yet i need to presetn the data - ideally - as a single share to the outside world - at least to the users, backup is a different story. All DSs will be iSCSI conected to an openfiler box.
I was wondering if there are opinions out there how to solve this best - with mounted volumes or directory junction points, or some other way, and what the pros and cons are......

Thanks for any input !
gerdwilhelmiAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kevinhsiehCommented:
I suggest breaking it up into separate drives and assign them each a different drive letter. Use a domain based DFS namespace to tie everything together.  This has the advantages of allowing you to move things around on the server, or even to different servers without changing the UNC path to the files. Is should also make it easier to transition to cloud storage.

If you did mount points you tie everything to that server name. It can also make backups a little bit harder.  I would even choose a standalone DFS namespace on the file server over mount points, but a standalone DFS namespace still ties you to that server name.

Have you considered putting this into the cloud? Thare are cloud gateways that have a local appliance that cache files locally for speedy access, but sut everything in the cloud for long term storage and inactive files.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gerdwilhelmiAuthor Commented:
Great points - thanks kevinhsieh. I thought DFS could only tie in shares from other servers, but I guess you can just map the UNC path to a local drive ? Does that work. If that is the case I agree that domain DFS would be the way.....
0
kevinhsiehCommented:
DFS just ties together UNC paths. In this case the DFS root would be on domain controllers, and everything would point to different shares on your single server, though you can also tie together your other file servers as well.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.