SRM 5.1 & NetApp - VM with RDM and MSCS

Similar Questions

• SRM with RDM, PRO using DR using iSCSI and FCoE

  Hello team, I plan a MRS. for a client, hoping to get your advice. the site of production using vcenter5.0, netapp3210, SRM5, esx5.0. FCoE for RDM for MS SQL server access. but DR site has only iscsi license, no FCOE, no card of the CNA. Will be RS stil works with RDM disks for data from MS SQL MON? advice please, thank you!

  Welcome to the community - there must be no descendants with presentation of RDMs fomr an iSCSI SAN-

• RS 5 with netapp SRA, FCOE site iSCSI with RDM

  Hi team, could someone please help to veify if it works in this scenario.

  We have PROD site running vmware vcenter 5.0, esxi5.0, SRM 5.0, Netapp 3210 ONTAP8.1 version file server. The VMs are windows Server2008, MS SQL2008 as major DB. Virtual RDM database files. Only FCOE for this site. AD is a physical Server 2003. The rest are virtual machines

  We offer you to have SRM for DR site deployment. The DR site is synchronized with netapp SRA snapmirrror, controlled by the console SRM5.0. Recovery site has no FCOE, only iSCSI and NFS license availble. Always RDM but using iScsi. vCenter 5.0, 5.0, netapp ONTAP8.1 2040 esxi.

  My questions are:

  1. If VMware SRM support DR failover for this case with the different protocol, PROD is FCoE, iscsi DR

  2. If the SRM supports failover with RDM in our case

  3. If the AD DR Server site need to be installed as a new best practices, or we will have to use SRM to switch production announced on website of Dr. What is recommended.

  4. If the physical AD can be kept as the common way and always taken SRM supported

  5. to the recovery site, which is the best practice? To use NFS to store data and iSCSI for iscsi? Or store data and RDM using iSCSI LUNS to simplify?

  
  

  Thank you!
  

  1. Yes
  2. Yes
  3. I would recommend if possible having a domain controller AD, already running on the DR site - it may be a virtual machine
  4. Yes, the PROD site domain controller can be physical
  5. I'd keep all compatible iSCSI so so -.

• Replicate the VMS with FTP and VM with virtual disk shared by: SRM with vSphre replication

  I have a VM and FT is configured on it. Now I can reproduce the virtual machine with SRM with replication of vSphere. I have not configured array based replication. Similarly, I have two DB VMs cluster, but they share a virtual disk between them. Can I replicate these VMs DB with vSphere replication?

  Your valuable contribution is much appreciated.

  I got the answer, for the virtual machine with FT and shared virtual disk replication, to do SRM with array based replication. vSphere replication cannot replicate virtual machine with FT or shared disk.

• VMware 5.1 with compatibility virtual RDM and Microsoft SQL Cluster mode

  Hello

  I am a bit confused by the VMWare documentation and hope someone can point me in the right direction.

  I want to know if it is possible and supported to create a cluster of SQL 2008 R2 2 nodes (Server 2008 R2 SP2 are VM) on a 2 node cluster VMWare 5.1 with the use of Virtual RDM compatibility?

  When you read the PDF on vsphere5.1 on the link below on page 9, there's a indicating note 'NOTE Clusters on multiple physical computers with no-pass-through RDM is supported only for Windows Server 2003 clusters. It is not supported for clustering with Windows Server 2008. »

  http://pubs.VMware.com/vSphere-51/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-51-Setup-MSCS.PDF

  So that means that I want "a 2-node cluster sql 2008 R2 server" is not supported?

  But I also found this link below and in the table of the column on the Cluster SQL line RDM is said 'yes' with a 2.

  VMware KB: Microsoft Clustering on VMware vSphere: guidelines for supported configurations

  Means 2/redirects-> for more information on shared disk configurations, refer to the Disk Configurations section in this article.

  -> Disk configurations

  • RDM: Configuration using a shared Quorum for storage or data must be on Fiber Channel (FC) based on RDM (physical cluster across boxes "CAB" mode, virtual mode for cluster in a box "IPC") in vSphere 5.1 and previous versions. RDM on storage other than CF (iSCSI and FCoE) are supported only in vSphere 5.5. However, in earlier versions, FCoE is supported in very specific configurations. For more information, see Microsoft clustering solutions table above note 4 .

  What follow-up note4->

  1. In vSphere 5.5, native FCoE is supported. In vSphere 5.1 update 1 and 5.0 Update 3, two cluster configuration of the node with Cisco NAC (VIC-1240/1280) cards and driver version 1.5.0.8 is compatible with Windows 2008 R2 SP1 64-bit guest operating system. For more information, see the VMware hardware compatibility guide:
     • Cisco UCS VIC1240
     • Cisco UCS VIC1280

  This means that it is suuported, I "m confused.

  Hi Bypy,

  Two windows 2008 R2 SQL virtual cluster nodes with RDM is supported only for the IPC or Cluster In a Box that is to say if the two virtual machines reside on the same host ESXi. The same configuration is not supported for the cabin or Cluster across boxes (virtual machines running on different hosts ESXi).

  The CAB, you go for the physical RDM mode.

  According to this link, http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959

  SQL Cluster using windows 2008 R2 is supported for both physical and virtual mode RDM. Between physical and virtual mode depends on whether you want the CAB or IPC respectively.

  I hope this helps.

  See you soon,.

  Arun

• Help with converter and RDM

  Hello.

  I need to convert a virtual machine that has a disc RDM.

  That's what I did.

  First convert the machine with stand virtual converter only, but excluding disc RDM.

  Then, when the new VM is ready I just add the RDM disk, but windows does not detect it.

  After that I have rescand disks but nothing happens.

  I added the new drive virtual and physical also.

  Why the STRP operating system does not detect the new disk?

  Thank you...

  Yhe comments should see the disc RDM (both physical and virtual).

  Make sure that your have remove old drivers comments (for example the HBA driver) and you have installed the latest VMware tools.

  Then, add the RDM and rescan the drive.

  André

• Protection of virtual machines with RDM

  I read through some of the old discussions on replicate and protect RDM and I have not read any good news yet.

  I have a volume on a cluster v6080 reproducing with snapmirror to a cluster of fas6080. I checked that the LUNS are replicated and are mapped to the recovery site esx hosts. I have re-scanned on both sides and checked that the LUNS are presented through the Victoria Cross on both sides. I have a machine virtual with a 3 LUN RDM and VMFS LUNs (RDM were created with SnapDrive one 6.0). When I go to set up protection for the VM, VMFS LUNs status is "replicated" for the location of recovery, but 3 RDM show as "not configured". My only 2 options are to detach (which won't allow me to recovery these RDM) or to browse a data store on the recovering site and locate a hard, .dsk or .raw which does not exist because the replicated LUNS are read-only. Right?

  What Miss me? Anyone had success reproducing and failover RDMs attached to a virtual machine?

  Looking forward to your answers. Thank you.

  Eddie

  Eddie,

  I have problem with HP storage RDM similar hada. I made a new analysis (twice, as usual) in the configuration of SRM-online picture and then frames that worked for me.

  Best regards, Peter van den Bosch

  Useful? Give me a few points

• VMotion VM with RDM failure

  I am facing a problem that I can not vmotion/migrate a VM with RDM. Other virtual machines with the RDM can vmotion, but I have a problem with a virtual machine. The error is:

  Incompatible device

  specified for the device backup

  "33."

  Copy the configuration of the Virtual Machine

  Check the compatibility mode and check the bottom of the article for more information.

  VMware KB: Difference between RDMs physical compatibility and virtual RDM compatibility

• MSSQL server VM cluster should be in the same host or different hosts with RDM

  Could someone me on how to place the code SQL cluster s VM with RDMs in ESXi hosts for advice.

  What is the best practice to place the SQL VM s in ESXi hosts.

  Affinity or an anti-affinite...?

  Appreciated your valuable answers.

  Depends entirely on the use case.

  • 2 MS SQL nodes on the same host to see the availability of the software
  • 2 nodes on different hosts to see the availability of the equipment

  I'd say MS Clusters on the same host (at the time of HA and vSMP FT) are redundant VMware features and represent an increase in management fees. The MS cluster on hosts provide something in addition to what VMware vSphere alone can provide!

• Poor with RDM only when added to the CAB MSCS cluster performance

  Hey guys, thanks for taking a peek at this question... I'm looking for some ideas.

  I have 2 virtual machines running Windows 2008R2.  They put MSCS in place and works as a taxi (cluster across boxes).  I use a 7500 VNX, fiber channel and RDM physical drives.  Is on an 8 node ESXI 5.1 v1117900 implemented.  Functionally, everything works fine.

  The problem is that the performance is very poor on only the RDM that have been added to the MSCS cluster.  I can take the same drive, remove the cluster, run IOmeter and it's fast.  I add to the cluster, MSCS, leaving in storage, and it is 1/15th the IOPS performance / s.  Remove the drive of MSCS and it goes back to when you run as usual.

  I tried different controllers SCSI (LSI Logic SAS vs Paravirtual) and it doesn't seem to make a difference.  I have physical MSCS clusters that do not seem to present this kind of performance problem, so I wonder if it was not something goofy with the MSCS on the configuration of virtual machines.

  I've already implemented in this article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1016106

  I saw this poor bus rescan the performance issue until I put the RDM perpetually booked, but it was not a problem since I implemented the fix.

  For any help or suggestion is appreciated...

  Thank you

  -dave

  Recently, I upgraded my esxi from 5.0 to 5.1 environment and have a bunch of systems with RDM. I had a problem as well. What I found, was that during the upgrade it changed all the policies of path to the LUN and rdm, it's the turn of robin. This causes a huge performance issue in my environment. I changed all the paths to MRU and it solved the problem.

• Request for clarification - physical RDM and vMotion - in case of issue of the review

  Hello

  I'm getting closer to my VCP-410 exam. There are a few things that annoys me on the documents against the experience of real life.  If I have a question in this area, I would like to know what way to go!

  The books that I use for study, as well as the official material state that you can not vMotion invited with a physical training RDM mode, yet a VMware KB 1005241 says the opposite, and I have a production VM with several RDMs physical (for taking snapshots SAN) who fortunately vMotions around my ESXi 4.1 cluster when DRS requires it.

  What is going on?

  Richard

  I'm not aware that there is a restriction for vMotion with RDMs in any version 4.x. In any case, I suggest that read you a few messages from jonhall. He is a developer of technical Certification at VMware and posted some useful certification as facts Re: Will VCP400 review include 4.1 points?.

  André

• Storage vMotion - WITH RDM? - Or will they ignored most of the time?

  Hi all - I have a storage vMotion, 5 hosts in the cluster - five or 6 virtual machines with RDM are pinned to specific hosts for the love of the DRS, but I want to go where the readers of the OS, then to VMDK is one San to another. If the virtual machine has a C:\ drive on the data store, all the other disks on the virtual computer is through physical RDM. ALL I need to move is the c:\(VMDK) in the process of storage vmotion.

  Time without are connected and work today to the ESX host in the cluster, all hosts are sized to see the RDM.

  My question is, when we go to perform the storage vMotion, how to avoid such failure? the RDM are my concern in the past, I think I remember a machine do not migrate when he had attached RDMs.

  any comments or thoughts would be really useful.

  Nick

  You can also move the ROW pointers with the data store 'change' - Assistant. Just be sure to select "same as source" for the format of the target disk. If you choose thick or thin, the RDM will be transformed into a VMDK, but with "same format" simply the ROW pointer is moved to the new data store.

  -Andreas

• Machines MSCS with RDM, how to change the data store?

  
  Hello world

  I'm having a problem of displacement of 2 machines with RDM disks.
  We have 2 guests ESxi 4.1 with virtualcenter, but no license for vmotion.

  This 2 machines is building a MSCS Cluster (Microsoft) (file server) with multiple disks (5) RDM,
  for a total area of 8.9 TB. Of course, for use with MS cluster, the WDR is with physical compatibility.

  The problem is that the local vmdk (and also rdm.vmdk files) for these 2 machines are on the local data store (a machine for each host) and I need to move them to the shared storage. But if I power off of a computer and trying to change with the ROW data store attached, I get an error because the VMFS of the commune dastore (block size = 1 MB) does not support these large files (up to 2 TB).

  I read a lot of articles
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1031041
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1026256
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1002511
  and a few other discussions of communities.

  In accordance with article
  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1005241

  I tried to turn off the machine, remove the RDM, migrate to another data store, and then reconnect the RDM.
  There is a big problem with the last point, because I don't know how readd the RDM manually (vmfsktools?).
  I want to add an existing drive, but he was in local storage, and I don't want more no reference to the file in the local storage...
  According to the documentation of vmware for MSCS, the second node of the cluster disks can be added simply to add a drive existing and selecting the
  existing node. If it is no problem of shared storage, but the host cannot read local storage to another host...

  Any suggestion to migrate a computer virtual with RDM shared storage room? Thank you

  E' possibile disabilitare he LUN filtering per vedere UN RDM gia awarded:

  http://www.yellow-bricks.com/2010/08/11/storage-filters/

  Option da diabilitare temporaneamente in vCenter config.vpxd.filter.rdmFilter

  Andrea

• Need advice. Move VM with RDM connections.

  I'm moving A VM with RDM of ESXi 3.5 5 relationships (free Version) using Veeam FASTSCP for vSphere 4.1. I copied the VMX and VMDK files for the C drive only to the new data store in vSphere.  I then tried to add RDM connections for the virtual machine in vSphere.  I get an error on the MAX # of virtual disks supported have been exceeded.

  Notes:

  1. After copying the file on the new cluster, RDM readers VMX appears as a normal virtual disk. x 5 (even though I never copied them on)
     
  2. Normally, I add the connections of RDM and remove these virtual disks 'Phantom' original and everything is fine.
     
  3. Storms, this addition is a total of 10 virtual disks, which puts me over the limit.
     
  4. Y at - it an easier way to move this virtual machine to the new cluster.
     
  5. Any help is appreciated.
     
  6. SAN (axiom of the 500-32 to Terminal)
     
  7. Cluster = 3-Dell Poweredge R710 Intel Xeon x 5690 @ 3.47 Ghz 96 GB of memory for each...
     

  Check this http://kb.vmware.com/kb/1005241 Ko

  might be useful

• virtual RDM and instant

  Hello

  I'm trying to better understand the operation of snapshots when you have a VM with RDM disks in virtual mode.

  If you take a snapshot of a virtual machine, and then write to a disc RDM in virtual mode, when you go back, this write request get reversed on the SAN because the RDM vmdk file is replaced?

  Thank you

  Rudi

  The disk i/o after the snapshot is always written directly to the LUN at some point and when you return, the disk i/o is reversed.  Is this correct? Or the disk i/o after a snapshot is written to the file pointer only?

  This isn't how it works. Think of a RDM in virtual compatibility mode as a normal virtual disk. As long as there in no snapshot on this disc RDM, all I/O is done on the RDM itself. Once a snapshot is created, any changes are written to a virtual disk on VMFS datastore to a delta file. If you make the snapshot, the changes are merged into the RDM. If you go back to the snapshot, the changes recorded in the delta file will be ignored.

  André