As long as the boot partition is on a mirrored RAID1 you can leave master/msdb/model there.

The biggest issue I see with your construct is that you have backups going to the same server. That is a HUGE no-no unless you have some other mitigating factor in play.

The tempdb/tempdblog question is a bit more difficult. I see clients where tempdb is massively overused for a variety of reasons and then isolating tempdblog with other logs could be helpful OR it overwhelm the log partition you have and cause slowness across other databases. Another issue with logging is that you WANT to have pure sequential writes there, but if you put 100 databases on the server that are all active to some degree you no longer get sequential activity on the disk - the heads are bouncing all over the place. Not good either.

There are SOOO many things that come into play with the provisioning and CONFIGURING of a new server and SOOO many ways I see clients mess it up!! :crying: