Re: Cpu speed and core recommendations for this 2003 server? Virtualization of parts ?

On Dec 1, 9:28 pm, Leythos <v...@xxxxxxxxxxx> wrote:
In article <63e4b289-c7fe-43e7-8bbc-4b2572756654
@e6g2000prf.googlegroups.com>, markm...@xxxxxxx says...





On Dec 1, 7:05 pm, Leythos <v...@xxxxxxxxxxx> wrote:
In article <e48f7f98-dffc-4b1d-acee-
1e316c071...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, markm...@xxxxxxx says...

How does all this change if i look to virtualize each role.. i'm
leaning more towards virtualizing each role.

A database, unless you want to kill performance, needs a proper drive
setup.

I do have one mirror for the OS.. the data was on raid5.. for
virtualization.. i figured i'd create another mirror.. if i had 5
virutal servers running.. i'd run 3 on the raid 5 and 2 on the mirror
set...

In terms of databases and VS.. what is typically done here.. is it ok
to have a sql server inside a virtual machine.. also.. on the virtual
servers.. is it typically setup the way a real server would be.. ie:
c drive for OS.. another D for data.. then an E say for logs.. or does
this even matter in the virtual sense..

Personally I see no benefit to VS, it's an extra waste of resources, has
it's own set of problems, and if the machine can handle all the
instances of SQL as VS then you might as well just not VS and set them
up on the server alone. You are going to have to learn how to manage the
memory between them.


I like the idea of having one "role" encapsulated in a VS
environment.. it can be easily ported to another server or backed up
all in its own piece.. so if there is any issues with that host's
hardware, it can be moved instantly almost.


You could run the entire thing on a single drive if you wanted to, but
that would not be good by any means/measure.

Databases belong on a single array, alone.

Transaction logs should be on another array, but you could put them on
the OS drive if only the OS resides on it.

Your users data/files/profiles belong on another array.

When you say this.. are you referring to the virtual drives..ie:
create virtual server.. then create a C, D, E drive inside it (c=OS,
D= Databases, E=logs).. or are you saying create one virtual
harddrive, store that "image" on one array, then create another
virtual harddrive, store that vhd on yet another array and so on?

Cheers
.

Relevant Pages

  • Re: Virtualizing Terminal Server 2003
    ... bit physical vs multiple 32 bit physicals it's not so simple, ... Microsoft MVP - Terminal Server ... are benefits to virtualizing so it's a matter of what's important. ...
    (microsoft.public.windows.terminal_services)
  • Re: Experiences with x64 and quadcore scalability.
    ... Virtualizing does provide options as license costs are not that large. ... I say about predicted stability of that specific server. ... guest virtual machines running 32bit OS for your terminal servers. ...
    (microsoft.public.windows.terminal_services)
  • Re: In place upgrade.. side by side.. or brand new install ontop of 2003 SMS?
    ... just pointers to the msi files stored on our file server (same ... I answered running all these databases on one box in your different ... memory would you need to allocate for just those 3 on one box (1gb ... They can sure be virtualized but all on one box might be a bit much, You could start by virtualizing just 2 and see how that goes. ...
    (microsoft.public.sms.admin)
  • Re: SBS 2008 and CRM 4.0 or general suggestions
    ... If you check the Dynamics CRM site, you can see that CRM Workgroup will run on Windows 2008 and will run on SQL Server Workgroup edition or higher. ... But SBS premium editions both come with a second server license and there is no reason why you can't run CRM on that server. ... Personally I don't recommend virtualizing SBS unless you have a business need to. ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtualizing Terminal Server 2003
    ... Some of you have real world example of max users per server ... Microsoft MVP - Terminal Services ... bit physical vs multiple 32 bit physicals it's not so simple, ... are benefits to virtualizing so it's a matter of what's important. ...
    (microsoft.public.windows.terminal_services)