2008 clustering

Similar Questions

• SQL 2008 Clustering on VM workstation 8

  Dear all,

  I am trying to configure SQL 2008 clustering on VM workstation 8. Until now what I did I would describe you below.

  (1) install Windows 2008 R2 64-bit VM001

  (2) install Windows 2008 R2 64-bit VM002

  After the creation of the above VM, I packed two HDD a VM001 follow the steps.

  • I created two discs Quorum drive, then a drive information.
    

  Then select each drive and delete in material management thing.

  Now I sail in the directories where my Virtual Machines is kept and VM001, open the .vmx file in Notepad. and add lines folloing the end of the file.

  #*******************************************

  #*******************************************

  # Shared disk to Config Info:

  diskLib.dataCacheMaxSize = '0 '.

  diskLib.dataCacheMaxReadAheadSize = '0 '.

  diskLib.dataCacheMinReadAheadSize = '0 '.

  diskLib.dataCachePageSize = "4096".

  diskLib.maxUnsyncedWrites = '0 '.

  Disk.Locking = "FALSE".

  SCSI1. Present = 'TRUE '.

  SCSI1.virtualDev = "free".

  SCSI1.sharedBus = "virtual".

  SCSI1:1.present = 'TRUE '.

  SCSI1:1.filename = "M:\Shared disks\Quorum.vmdk".

  SCSI1:1.redo = «»

  SCSI1:1.mode = "independent-persistent."

  SCSI1:1.DeviceType = 'disk '.

  SCSI1:1.virtualDev = "free".

  SCSI1:2.present = 'TRUE '.

  SCSI1:2.filename = "M:\Shared disks\Resource.vmdk".

  SCSI1:2.virtualDev = "free".

  SCSI1:2.redo = «»

  SCSI1:2.mode = "independent-persistent."

  SCSI1:2.DeviceType = 'disk '.

  #*******************************************

  #*******************************************

  When I added above lines, two virtual machines (VM001 and VM002) were closing in.

  Then I did following steps.

  • Start VM001.
    
  • Right-click on desktop of | Manage the. Navigate to the disk management node.
    
  • Make sure that both drives are Of Basic Volumes.
    
  • Quickly put in the form and bind them to the letters lead for example; Q and R (quorum and resources).
    
  • Then start VM002
    
  • From the node Management disk in the Management Console, you should see both drives.
    
  • I just 'change' their drive letters.
  
  
• Give them the same drive letters you gave them for VM001.


• Stop the server.
  

Now can someone please guide me the steps to set up the SHARING STORAGE and configuration on the addition of CLUSTERING in WINDOWS 2008 R2 64 BIT. EA

Thank you

Adeel Imtiaz

Windows 2008 clustering requires the support of SCSI-3 persistent reservation on drives that is not provided by VMware "shared SCSI bus" configurations or one of the 'open source' iSCSI targets The best way to get W2K8 go clustering is to use something like target RocketDivision StarWind iSCSI (http://www.rocketdivision.com/) to offer 'shared' storage, then use the W2K8-built-in iSCSI initiator to connect to cluster storage...

Cheers, your Udin

• Windows Server 2008 clustering

  I'm testing Windows Server 2008 shared help cluster on an IBM SAN ds4500 storage. Two RAW LUNS are used as storage shared on both Windows 2008 servers. When I run a test of validation in the context of implementing a cluster I ger errors on validation of the disc. So no disks are found which are suitable for the Server 2008 clustering. The error in the log is:

  "LSI adapter, Ultra320 SCSI 2000 series, bus type w/1020/1030 fake disk doesn't support clustering. Disk partition style is MBR. Partition of disk type is BASIC. »

  If I add the same two LUN RAW for Windows Server 2003 clustering they are valid drives presnted to set the cluster.

  VMware esx 3.5 update 2 has a support for setting up clustering 2008?

  Thank you

  R

  Hello

  You need two things win2k8 MSCS support

  (1) SCSI-3 persistent reservation

  (2) virtual SAS device

  These two are not yet supported on 3.5.

  Thank you

  Samir

• Server 2008 Clustering in ESX 3.5 Update 3

  I see it in the release notes for update 3 that Server 2008 clustering is not yet supported. We have a development environment that we would like to build clusters 2008 for test purposes (no production). In addition, our dev farm is boot-from-SAN. Did somebody get 2008 clustering to work?

  As an alternative, VMware Server would work for this? We try to avoid the cost of physical boxes and storage shared for clustering testing 2008. Yet once, it will not be a production workload. Thanks in advance.

  They're waiting for you, Gordon... in the test Chamber...

  I got a 64 bit 2008 Enterprise cluster successfully on 3 update configured, with iSCSI volumes connected Microsoft like shared disk (only players to start the virtual machines are on VMFS, also on a SAN-based data store). Have had no issues at all, even when rapid vMotioning of VMs cluster node (which are given 8 GB of RAM a piece) during periods of IO reasonably heavy.

  Hope that helps! Please, help me by marking my response as "useful" or "correct", if you feel it is useful!

  -Amit

• ESXi 4.0 supports Windows Server 2008 Clustering?

  Hello

  Does anyone know if the Clustering Windows 2008 Server (MSCS) is officially supported in ESXi 4.0?  If this isn't the case, someone has suggestions on how to configure it to a production environment by using third-party tools?

  Thank you

  Andrew

  Yes.

  http://www.VMware.com/PDF/vSphere4/R40/vsp_40_mscs.PDF

• Clustering Windows Server 2008 and the STORport driver

  Hi all

  I recently read on the documentation for "Setup for Microsoft Clustering and Microsoft Cluster Service".  It says to use the LSI Logic STORport drivers with Windows Server 2008 clustering, instead of SCSIport drivers. I can't find the STORport drivers anywhere.  I can't find this on the LSI Logic's Web site.

  TIA

  -Rick

  See the site of LSI:

  http://www.LSI.com/storage_home/products_home/host_bus_adapters/scsi_hbas/lsi20320r/index.html

  André

• DHCP - Windows 2000 - > Windows 2008

  I have two Windows 2000 servers with their own glasses, I want to build two 2008 clustered servers using the 80/20 rule and migrate the scopes on manually, no matter what advice?  If this is not the right place let me know.

  Hello
   
  Your question of Windows 7 is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the public on the TechNet site. Please post your question in the TechNet forum.
   
  http://social.technet.Microsoft.com/forums/en/category/WindowsServer/

• Consolidation of support for Windows Server 2008

  In the statement of support for vSphere for Server 2008 clustering, he mentions that the two nodes of 2008 should not belong to a cluster HA/DRS.  We currently have our cluster designed to accommodate all guests (HA/DRS active) in the data center.  Excluding the HA/DRS features for VMs individual cluster node, will support us?

  TIA

  -Rick

  The documentation is that if you have virtual machines in a cluster HA/DRS then you don't are not supported.  You will need to disable these functions on the entire cluster for real assistance.  That said, I have this configuration and have been able to call VMware to support without problem.  This does not mean that you will have the same experience, but my guess is that they would support you if necessary.

  You can also see fault-tolerant VMware (FT), but you must understand the differences between MSCS and FT.  If you're upgrading clustering an application such as Exchange, I wouldn't use FT and would use rather MSCS.  Everything depends on what you're trying to accomplish and what fits best. Also remember that FT does not provide protection at the hardware level, so a lack of application level would be replicated on two virtual machines.

• ESX 3.5 and windows server 2008

  It appears, from what I can find this server running 2008 clustered is not yet supported by vmware.  From the update 4 is this always the case?  Also is there still no support for scsi-3 reservations?  Of course, this means I have to use an ISCSI target for win2k8 clustering.

  Hello

  It appears, from what I can find this server running 2008 clustered is not yet supported by vmware.  From the update 4 is this always the case?  Also is there still no support for scsi-3 reservations?  Of course, this means I have to use an ISCSI target for win2k8 clustering.

  There is no support for clustering Win2K8 correct.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009
  ====
  Author of the book ' VMWare ESX Server in the enterprise: planning and securing virtualization servers, Copyright 2008 Pearson Education.
  Blue gears and SearchVMware Pro items - top of page links of security virtualization - Security Virtualization Round Table Podcast

• VM SCSI configurations

  I'm under ESXi 4 Update 2 vSPhere.

  Is there an advantage to LSI Logic SAS on parallel for my Windows Server 2003/2008 servers?  Or maybe even the paravirtualized controller?

  The VM Administrator's Guide is not really say crap on the use of one over the other as performance is concerned, with the exception of the paravritualized one, but I don't know what are the consequences if I use it in addition to not being able to use it as a boot device...

  LSI SAS was initially introduced only to support Windows 2008 clusters, so I guess that you would not get the performance of switching LSI SAS gains. Paravirtualized you will give additional performance, but only on heavy load and it is not supported for the startup disk.

  ---

  MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

  http://blog.vadmin.ru

• in all of the pool with w2008 area

  Hello there - some windows in our organisation team people want to create a cluster of w2008 impression, but we at ESX 3.5 update 4 and the latest documentation I see for MSCS provides the following:

  «VMware virtual machines currently emulate only SCSI2 reservations and do not support applications using persistent reservations SCSI3.»

  Guess what - SCSI3 is a requirement of clustering w2008...  Does anyone know a way around this?  If a driver is available, please include links to download and or any specific instructions, that I should be aware of so I can rationally this recap.  Thank you!!  Looking forward to what everyone has to say.

  g

  To make Windows 2008 clustering with ESX, you must run ESX 4.0 as the SCSI driver support SCSI3.  This is true when shared volumes are presented directly to each ESX host.

  If you use the shared iSCSI storage, the other option is to present records shared through the initiator Microsoft iSCSI directly to virtual machines.  This bypasses the limitation on Windows 2008 clustering on ESX 3.x.  I used this configuration several times successfully, even for highly applications such as Exchange.  I have seen the argument both ways as to whether or not this particular configuration is supported, but I had to call support both VMware and Microsoft for issues with the cluster and the two have no problem supporting me.

  I hope this helps.  Beyond using the intellectual property according to the storage inside virtual machines, I'm not sure another way to circumvent Win2k8 clustering on ESX 3.x.

• ESX Multipathing change... What is the effect.

  Hello

  We have esx 3.5 for the moment and we expect change VCS code of our HP EVA from 3.x to 4.x, because we have this windows 2008 clustering Raw Device Mapings suport to the San.

  I know that currently the VCS code runs as active/passive for multiple access paths and new tracks from VCS 4.x as active/active. Anyone know if this is going to be a problem by changing to active/active with ESX 3.5

  Thank you

  ESX supports A/A and A / P so it will work.

  Kind regards

  Gerrit Lehr

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '.

• Microsoft Cluster in a virtual environment

  Is it possible to run a Windows 2008 Failover Cluster in a virtual environment using ESX 3.5?

  Kind regards

  Daniel9999

  The Windows 2008 Clusters are only supported with vSphere.

  But if you have an iSCSI storage, you can use a solution 'unsupported' (but functional) using iSCSI initiator inside Windows 2008 SMV to point to a few LUNS shared.

  More info on:

  Software clustering in a VMware environment

  André

• 256 GB drive limit - what is the purpose?

  First of all, I think that for free (and paid) of VMWare are remarkable, and I read to a larger partition:

  http://communities.VMware.com/thread/157876

  My question is, why is there a limit of 256GB vmfs?  They do not realize the disks themselves up to 2 TB EACH days?  I don't want to lose 8MB each time I have to write a 2 k text file!  I also want one bigger than the table of 2 TB (seriously, 2 TB is MAX LIMIT POSSIBLE? Why did do that?) ... This isn't exactly make me want to start buying more products VMWare if I can't do even a few mounts simple drive because the table is too large.

  Anyone know if there is a plan to make VMWare a use value or the purchase by adding the ability to use large capacity disks?

  Thank you

  Yes, a VMFS volume with a block size of 1 MB does limit the size of an individual file in the data store to 256 GB.  But is it really this limitation?  Many applications just so much space.  Of course, there are file servers and other types of data sets that may require more disk (databases, of imagery, GIS, etc.), but in my experience, those who seem to be the exception rather than the rule.

  If more space is needed, increase the block size of the VMFS in time format is a trivial process.  Expand a VMFS datastore beyond 2 TB is also a trivial process (the 2 TB LUN address limit is due to the implementation and use of the SCSI-2 command set).  This may require a larger size of block in a first time - to address a full 64 to VMFS data store (LUN 32x2TB), a block size of 8 MB is required.  A block size of 1 MB is that of ~ 16TB in a VMFS data store.  As has been mentioned, sub-block allocation (one of the neatest features of VMFS, if you ask me) is automatic for smaller files, so space is not lost at the level that you may believe.

  As mentioned elsewhere, drive more than 2 TB is directly accessible by the client if necessary through NPIV or iSCSI in the comments.

  At some point in the future, VMware could start using the full set of SCSI-3 controls, which will allow many more large LUN to be processed by the VMkernel.  vSphere provides the SCSI-3 limited controls, specifically for Windows Server 2008 clustering, but does not implement the SCSI-3 device addressing scheme.  As for all the statements 'which is to come', there is no working crystal ball, and more great address feature can perhaps never - we'll all just wait and see.  I'm just speculating at this point.

  How many virtual machines not really need a lot of disk space?  I am convinced that there is a little, but is it really that big of a deal for most of them?

• Need help with implementing NLB on top of MSCS 2008 R2 to achieve active-active clusters

  Hi all

  I just configured Active-passive cluster (default when creating 2-node MSCS) successfully in my Windows Server 2008 R2, which currently hosts my custom web application, I also tried Telnet on port using MSCS FQDN and it works, as well as each respective node with the same port name both work successfully.

  However, in order to create active nodes for my custom web application, I have to configure NETWORK load balancing, so I wonder if anyone here can guide me in the best practice to install and implement NLB for asset MSCS cluster VMware?

  Any help would be greatly appreciated.

  Thank you.

  Multicast configuration may have a problem with some switches (like e.g. Cisco).

  Check in the documentation of the seller switches to see how not multicast filter and if there is a specific configuration for NBL in multicast mode.

  André