Best Practices for a 2011 SBS Implementation
Posted on 2012-08-23
Im coming in late on a project to implement and migrate a Windows 2011 SBS environment. Customer currently has 2008 SBS with Exchange and SQL in place. Ive read up on the migration process, but Im on the fence on what to do with the server Ive been given.
Its an HP Proliant ML110 G7 with 16 GB of RAM and a mirrored set of 1 TB hard drives. Customers current usage of hard drive space doesnt even break 200GB, even with the OS / Programs, so I dont feel horrible about storage space, but Im not thrilled with the lack of spindles.
Im considering using the 2008 R2 std license included with the premium to load and use the Hyper V role on a base server, and then load one or two servers as virtuals. Presently, they run everything on their one server and have no complaints. If I split it up, it might be easier to move hardware later, but it would also require additional RAM overhead (for the guest server OS) than it would take if I put it all in one virtual box. Documentation tends to suggest that the Premium (with SQL 2008) is expected to be loaded on a separate machine. Thoughts, insights, ridicule on what I should do to make the best of this? They have 15 users, and will probably max out at 20. On the plus side, they do appear to have bought the CALS and licenses...
Also, theres no backup software purchased at the moment. Im considering the built in backup to keep costs low for them, coupled with USB hard drives - but Ive never used that in environments with SQL and Exchange. Does it work well?