VM file server... splitting up data

[gshaw]

Going to be moving our main file server into the VM infrastructure at some point soon which will give us a bit more flexibility about how we store the data. With that in mind was wondering if it might be worth splitting the files out over 2 separate VMs...

 

- static data (shared drives, user home areas etc)

- user profiles and any other frequently changing data

 

Logic being I can then tier the VMs over time if required for faster user logons etc. Could even split the user home folders away from the shared drives although not sure if that's overkill

 

Anyone done similar once going virtual?

[ChrisH]

One thing I will say is use a DFS name space so then you can move your data around, to whatever server you want and all you need to do is update the target and not change server names etc in other configurations/scripts.

[saundersmatt]

One thing I will say is use a DFS name space so then you can move your data around, to whatever server you want and all you need to do is update the target and not change server names etc in other configurations/scripts.

 

I'd echo this sentiment, but with one small caveat: Don't do it if you have any OS X clients.

 

We have multiple file server VMs, with the view point that if one needs a reboot it takes less resources out of action, and smaller VMs are easier(quicker) to move around the cluster than bigger ones.

 

Matt

[gshaw]

Had thought about this a few times in the past, maybe time to make the jump...

 

I'm guessing a good idea would be to add the namespace server role across a few of the file servers for resiliency, just skimming a few articles to get an idea of the deployment steps at the moment

[Ashm]

I've gone with Home drives on one file server VM and all shared drives on another VM.