Re: Cluster Test

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Correct as John mentioned. We have setup Virtual Server 2005 Enterprise
Edition (because it cannot be done with Standard Edition) using the link
below.

Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node
Microsoft Windows Server 2003 Cluster
http://www.microsoft.com/technet/prodtechnol/virtualserver/deploy/cvs2005.ms
px

On Virtual Server 2005, I've setup (1) DC and (3) Nodes with 3 groups,
Cluster Group, Printer Spooler Group and User's Home Folder Group. Works
great for testing and getting the feel of a Cluster enviornment.

840192 Requirements for configuring clustering in Virtual Server 2005
http://support.microsoft.com/?id=840192

IMPORTANT NOTE:
Because Virtual Server 2005 does not support the failover from a virtual
machine on one host computer to a virtual machine that resides on a second
host computer, a server cluster that you configure in Virtual Server 2005
is best suited for testing and development purposes. Microsoft recommends
that you do not use this configuration in a production environment.

--
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>

-----Original Message-----
> From: "John Toner [MVP]" <jtoner@xxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: Cluster Test
> Date: Thu, 21 Apr 2005 17:22:46 -0400
>
> If you want to test out cluster, you might consider using Vmware or MS
> Virtual server to create a virtual environment on a single server. Also,
you
> could build a 2003 cluster using a "Majority Node Set" quorum device. This
> will give you the "look and feel" of a cluster without the functionality.
>
> Regards,
> John
>
> -----Original Message-----
> "ingenio" <ingenio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:68611C51-573E-4594-AEFB-44ABA4DE65DB@xxxxxxxxxxxxxxxx
> > Can I test the MCS using 2 clonic machine for the nodes, and a third
> machine
> > how system storage?
> > Or it is mandatory to have a SCSI bus?
> >
> > Sorry my english.
>
>
>

.



Relevant Pages

  • Re: Installation SQL Server 2k Cluster on Windows 2003 failed. Please help.
    ... Looks like the unattended installation on all cluster nodes succeeded and failed during the virtual resources creation step. ... Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering ... How to install a Microsoft SQL Server 2000 virtual server on a Microsoft Windows Server 2003 cluster ...
    (microsoft.public.sqlserver.clustering)
  • RE: minimal hardware for building testing failover clustering for SQL
    ... Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node Microsoft Windows Server 2003 Cluster ... This guide provides step-by-step instructions for using Virtual Server 2005 to create and configure a two-node server cluster. ...
    (microsoft.public.sqlserver.clustering)
  • RE: Clustering H.E.L.P.
    ... For training, demo, support purposes, one could setup a cluster using Virtual Server 2005. ... Using Microsoft Virtual Server 2005 to Create and Configure a Two-Node Microsoft Windows Server 2003 Cluster ...
    (microsoft.public.sqlserver.clustering)
  • Re: MSDTC Troubles, Do I Even Need It?
    ... After joining the cluster, as a test moving the Cluster group to the new node. ... see How to add nodes to an existing virtual server (Setup). ... On the Advanced Options screen, click Maintain a virtual server for failover clustering. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Default or named instances??
    ... I've setup the cluster and tried to install the second instance as default ... According to your explanation about the relationship between SQL instance ... and virtual server I would change the analogy to say I could treat the ...
    (microsoft.public.sqlserver.clustering)