No limit on file sizes - a decent Windows desktop app with (optional) auto-download feature (this to me is the most important feature) - ability to control/edit all sent items (add/delete files, change expiry date etc) - notification when item is downloaded - decent and flexible pricing (price is set in 1 TB increments, which means you can add or remove storage at will) - good storage management features (search/filter etc) After a careful market research, we found its features meet most of our needs, incomparable to similarly priced services. We tend to use other services (WeTransfer/Google Drive) for smaller packages or ones that don't really require authentication, but for most uses FileMail is our best option. If you'd like more details drop me a PM or email.We use this service on an almost daily basis for various needs involving external parties (festivals, post houses, distributors etc), often times for 100-200 GB sized. We currently have four 8 way servers hosting 70 VM's looking after the above and a lot more. One of our SQL DB's has 500 current users but the largest looks after all 1600 users as it supports our intranet content. Applications range from Exchange through to intranet and 10 SQL DB's. We currently have 1600+ users using our VMware farm. We have an environment slightly larger in user terms. Hosting for this many users and about 3TB of data? Would it be wise to go virtual on file, mail andĪre there people who have virtualised a file cluster Including file, mail and database services for this Would need to house this kind of virtual environment, I am curious to what kind of physical hardware we After consolidation we will haveĪll the users within one forest and one exchange Currently we have aboutġ000+ users running on difirent locations andĭiferent domains. We are currently looking into virtualizing an entire But in general 4 way processors with lots of ram give you the best bang for your buck. the capacity planning tool allows you to do virtual modeling of your environment so you can do cost vs benifit analysis on the servers you are looking at. Using both of these together ensures that your virtual environment is fault tolerant and able to grow as necessary.Īs for physical hardware. N+1 means what ever amount of servers you think you need, add 1. Look for servers that make good candidates for virtualization and play with the modeling.Įxchange, DCs, web server, file server, and ancillary services make excellent candidates because the processors do nothing and its all about the network most of the time.Ī good idea to keep in mind is that you want to plan to keep your VMware hosts at about 50-60% utilized and use the n+1 configuration. The best thing for you to do is go get a tool like capacity planner and examine your network. And even that they are going to start working towards virtualizing. The only servers that are not on VMware is their SQL cluster and that is because it is truelly and astoundingly massive. And shortly they are moving the remaining non-vmware servers onto VMware. So we split the cluster up so i can spread the usage accross my VMWare farm.Ī very large client of mine is hosting 22,000 users on VMWare. We used to have a file server cluster which was one server dealing with admin/student home and admin/student shared. If you are worried about performance you can do what we did. We can easily get more VM's per box without issue. Hardware wise we have 7 DL585's with only about 70 VM's. The proxy is actually faster in a VM for some reason. They are all virtual to virtual clusters and work great. We also have an array or windows vm's biggest usage would be our clustered proxy and clustered SQL servers. Performace wise you can not tell when the building is crampacked or empty. We are a college so we are what we would class as been a almost empty building. But when we run things on the VM's you cant tell the difference. 400 concurrent users on our admin home file serverĢ76 concurrent users on our student home file serverĥ53 concurrent users on our shared file serverĪll of the above are physical to virtual clusters and we try and keep things on the physical servers to make sure we are getting the best performance possible.
0 kommentar(er)
