Alright, sounds like you have quite the server list. Since you are using Virtual LANs grouping will be easy to change if you ever needed/wanted to...This can make the grouping fun. :-)
As far as suggestions for groups I am more comfortable separating by functions. This way I can scale my preventative maintenance and security to cater to each VLAN. For example I might have a setup like this:
VLAN1 ? Network Users with Static IP (User Desktops)
VLAN2 ? Network Users with Dynamic IP (Laptop and Wireless Users)
VLAN3 ? Internal User Services (WINS/DHCP/Exchange/File-Sharing-Servers)
VLAN4 ? Back-up Network (Backup Servers from VLAN3)
VLAN5 ? Externally Accessible Servers or Maybe DMZ (WWW/POP3/DNS)
VLAN6 ? Public Internet Outbound (Routers to Internet)
Naturally you can group your stuff based on what you have but this is a setup that comes to mind. What I like about this is that I can tweak my access between VLANs ?just in case? something gets compromised. For example, if a user laptop is broken into from the outside then only allowing VLAN3 to VLAN4 would protect your Back-up Servers at a bare minimum. Obviously you could do a ton of methods to protect VLANs from other VLANs in case of a compromised system.
Now if youare running IPX, Appletalk, and/or TCP/IP then would consider separating these as well as best you can to keep the chatter on the saem broadcast domain.
Keep in mind that the more LANs that you create the more that you have to administer. I currently have Network that I am trying to fix because there is literally only 2 Servers per VLAN making the Admin work a nightmare. To add a device it means adding a new VLAN, Subnet, etc?
Thanks,
-Jim