Best possible scenario for Windows 2012 file server.

hi there,<o:p></o:p>

we have few windows 2003 file servers here. each file server has hundreds of shares , of shares must online during working day. @ moment not using file server clustering or dfs technology. windows patches must done @ night or during weekend. <o:p></o:p>

we looking on replacing our “old” windows 2003 file servers new windows 2012 servers. new project have purchase 2 brand new hp servers (hp proliant dl360 gen8). both servers connected san iscsi connection. <o:p></o:p>

we haven’t played windows server 2012 yet need professional advice on building best possible scenario our future file server.<o:p></o:p>

here proposed options far.<o:p></o:p>

option one<o:p></o:p>

we going install windows server 2012 on both hp servers. each server create 1 or more luns on our san. shares moved old win2003 servers onto new ones. logon script modified new location path drive mappings. <o:p></o:p>

from can see, option pretty same had. still no fault tolerance , no high availability shares. security patches needs done @ night…, again.<o:p></o:p>

option two<o:p></o:p>

two node file server cluster setup. now, can patch , restart server during working day. maybe creating 2 node file server cluster going on kill here… maybe need @ dfs option… no sure if dfs better solutions windows 2012. and, memory dfs solution require double space?  basically both file servers have replicas of files , folders

option three<o:p></o:p>

windows 2012 server core hyper-v role installed on both servers. create 2 node hyper-v cluster 1 or more cluster shared volumes (csv) on san. on hyper-v cluster can create 2-4 virtual windows 2012 servers. now, need decide option choose our file servers. option 1 or 2 proposed option list.

thanks in advance.

you haven't given load information it's not possible give performance based answer - if a.n.random person came me , said have 10tb share general users, i'd tell them spin vm serve that's default answer new server roles these days - on other hand, if of users downloading 10tb every hour, might different answer.

not keeping 2 copies seems key you, can run csvs describe: use cluster shared volumes in windows server 2012 failover cluster - they're beefed in 2012.

you can add dfs namespaces without dfs-replication make future expansions / additions / changes transparent end users. (technet guide)

or put of these together, useful (though older) guide available: here

Windows Server  >  Windows Server 2012 General