great svMotion RDM

Similar Questions

• SVMotion rdm for vmdk

  When I try to svmotion a virtual machine with physical rdm attached to it, I want to convert VMDK but I do not see the option. I fact svmotioned the vmx and vmdk Os file. Also moved the map of rdm file. How convert vmdk?

  Remove it, he as a virutal rdm readd and then you can to a vmdk svmotion

  VMware converter should work too

  Here's how to convert your phsical one rdm rdm virutal if you need:

  http://sparrowangelstechnology.blogspot.com/2012/09/convert-your-physical-RDM-RDMP-to.html

  Here's how to convert your virutal rdm a vmdk using sotrage vmotion:

  http://sparrowangelstechnology.blogspot.com/2012/09/SVMotion-RDM-to-VMDK-virtual-disk.html

• Storage Vmotion - 1 of 2 data warehouses

  Hello

  I have a server with its main disk to A data store and an additional drive for the data on the data store B.  I have created a new data store C and want to do an only the data disk B storage vMotion.  Is this possible? If so, how?

  Thank you
  REDA

  When you do the svmotion and move on to part 2 where you select storage,.

  Advanced call

  now, select only the 2nd data store.

  the default value for the diskA be will remain the same

  If you need a walkthrough visual is the same thing just that the row in the link is your diskB

  http://sparrowangelstechnology.blogspot.com/2012/09/SVMotion-RDM-to-VMDK-virtual-disk.html

• ESXi 5.5 local RDM is greater than 2 TB

  I recently added a set of 3 TB WD red SATA disks to an ESXi 5.5u2 host and set up their physical compatibility as cards attached to a guest Windows Server 2012 gross. These discs appeared as having a capacity of 512 b and the space unallocated on 16EB:

  

  The first cards were created using vmkfstools as follows:

  vmkfstools - z /vmfs/devices/disks/vml.0100000000202020202057442d574d43315430333739323233574443205744 WD_RED_1.vmdk

  vmkfstools - z /vmfs/devices/disks/vml.0100000000202020202057442d574d43315430343235393733574443205744 WD_RED_2.vmdk

  vmkfstools - z /vmfs/devices/disks/vml.0100000000202020202057442d574343344e484b3637433346574443205744 WD_RED_3.vmdk

  If I take out discs, connect them to a physical host while I'm able to put a GPT disks and add a volume using Windows storage spaces. Once more attached to the ESXi host they work very well, although records show the same space of capacity / free.

  Looking around, I see that others have encountered this problem, without any resolution:

  https://communities.VMware.com/thread/468799

  https://communities.VMware.com/message/2329909

  https://communities.VMware.com/thread/466442

  Disk emulate a 512b sector size and I was wondering if this is likely to be part of my problem? I was wondering if anyone else has encountered this problem or could use directly attached cards raw device with greater than 2 TB disks?

  This problem has been resolved in the upgrade to ESXi6.

  The disks were already in GPT format and unfortunately version 10 of material did not help

• Pointer of RDM / vmfs block size?

  We run ESX 4.0 on Dell R710s connect to a network SAN IBM N-Series on CF.

  This week we had a major outage due to a server RedHat MySQL fall.

  Off firstly the server wouldn't boot past virtual POST-sachant a RDM disk I have it deleted from the configuration. The server would then boot to OS, but every time that the ROW was reconnected it would either fall or unbootable.

  I remembered we had farily recently expanded space on this server and the RDM was now 300 GB in size. However the space used was only 85% on the lun (255GB). Then I remembered the limits of block size. The server was sitting on a partition vmfs with a block size of 1 MB (256GB max). So I removed the RDM and svMotion had the server in a data store that have a block size of 2MB, reconnected the RDM and the server starts very well. After a consistency check DB we were back running.

  This survey of fault, I went to read the document of maximum rates of the white paper

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

  to be honest - had some vague information on RDM

  and then I found VMware KB

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1029697

  surprising to me, which clearly states the pointer RDM files are affected by the block vmfs sizes.

  However, there is a difference of opinion in this thread

  http://communities.VMware.com/message/1507498

  And look further in my own environment, we have several production server running with connected RDM which are excessive in size until the limits of said block size.

  I need clarity defined on it because as he sits down we could have several production machines in an unstable state, or I'm just left with no explanation for the disc lock, we witnessed and a power outage that caused a substantial loss of business.

  concerning
  wolfsonmicro

  Post edited by: wolfsonmicro Click accidental - it is always a request without response

  My understanding is that the LUN cannot be greater than the maximum size supported by the data store on that of RDM file pointer is created.  Pointer RDM file does not need to be stored on the same data store, Setup or other files vmdk files, for example you could have moved the file pointer RDM from a store of data with a larger block and left the vmx file and the data store other files vmdk with a block of 1 MB.

  Are you sure that files of pointer RDM for running virtual machines, you have on data with blocksizes warehouses NOT supporting the LUN size they point?

• Limitations of architecture with replication of VM with physical RDM Mode

  What are the Limitations of Architecture with replication of VM connected with physical RDM Mode in vsphere replication. Why VMware does not support this?

  I will add some colors to the response of GS. A particular interest with regard to the physical path RDM (pRDM) works, summarize these two chips of the article:

  • Physical mode specifies minimal virtualization SCSI of the mapped device, allowing greater flexibility for SAN management software.
  • VMkernel passes all SCSI commands to the device, with one exception - the REPORT LUNS command is virtualized, so that the VMkernel can isolate the LUN to the virtual machine owner. Otherwise, all the physical characteristics of the underlying hardware are exposed.

  There is an integrated in vSphere vSphere (RV) replication agent that has several functions. In particular, she keeps track of the Scriptures to the virtual machine. When a replication cycle occurs, the changed data is replicated to the target location. The VR agent should be able to 'see' These Scriptures to follow. Given that the physical mode all SCSI commands directly to the device, the VR agent is unable to follow these changes for replication.

• .vmx file did not move after svmotion

  Hello

  I've been svmotion'ing a MSCS VM with RDM today (the RDM migrated separately from the side SAN) and after the migration, I figured out that the virtual machine installs with only the vmdk files. .Vmx files, log files, and other necessary files have been left out in the source data store. I moved two or three other virtual machines with RDM a similar setup and they moved very well. The only difference was this virtual machine is, he had an ISO mounted and connected. Would it have caused a problem?

  How move the .vmx and other files now? The must close the virtual machine and move the files manually using browser data store?

  Rahul-

  That's my understanding of it, if you run 5.X, you can migrate online and use the advanced option.

  But here's another good article migration RDM and a question for users of RDM. | VMware vSphere Blog - VMware Blogs this article goes into details migration scenarios and outcomes that result.

  It is simple process, as you have done with other virtual machines, just make sure that nothing is attached to the virtual machine, although this should not affect svmotion.  Start with the svmotion to datasore another standard, if the configuration files are still not migrated, then use the Advanced setting to verify the migration of the configuration files , simply use the advanced option.

  VFK

• RDM to delete and recreate the mapping of RDM file and fix

  Hello

  I wrote the following script, but it works fine except it does not create the mapping of RDM file.

  If I comment out the following lines, it works fine.

  $fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

  $spec.deviceChange [0] .fileOperation = "crΘer".

  Here is the code below

  Replace-VM-RDM function {}

  Param ($scsiid, $rdmname, $vmname, $filename)

  < #.

  Convert SCSI address in Vmware format

  # >

  $scsicontroller = $null

  $scsiid_split = $null

  $scsiid_split = $scsiid.split(":")

  $scsicontroller =($scsiid_split[0])

  # SCSI VMware in the GUI controller ID is a number greater than the real controller id

  $scsicontroller = [int] $scsicontroller + 1

  # Vmware waiting conntroller with 4-character id

  $scsicontroller =($scsicontroller.) (ToString()) + "000".

  $scsicontroller

  # SCSI LOGICAL UNIT NUMBER

  $scsilun = $null

  # VMware SCSI LUN ID in the GUI is a higher number than the id real lun

  $scsilun = [int]($scsiid_split[1]) #+ 1

  ###

  $vm = get-VM-name '$vmname ' | Get-View

  IF (!) (($filename))) {}

  $RDMFile = $rdmname.split("") [0] + "_RDM.vmdk"

  $filename = (($vm.)) (Config.Files.VmPathName). Replace("$vmname.vmx","$RDMFile"))

  }

  $esx is get-view $vm. Runtime.Host

  < #.

  Download CanonicalName RDM Lun

  # >

  $rdmCanonicalName = $null

  $rdmCanonicalName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). CanonicalName)

  $rdmDevicePath = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

  foreach ($dev in $vm. Config.Hardware.Device) {}

  If (($dev.)) GetType()). {Name - eq "VirtualDisk")}

  If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or)

  ($dev.Backing.CompatibilityMode-eq "virtualMode")) {}

  If (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {}

  # Remove the hard drive

  $hd = get-disk hard $vm.name | where {$_.} Filename - eq $dev. Backing.FileName}

  $hd | Remove-hard drive - confirm: $false

  Write-Host "file name:" $dev.backing.fileName "

  Write-Host "Disk Mode:" $dev.backing.diskMode

  $dev.backing.deviceName

  $dev.backing.lunUuid

  $DevKey = $dev.key

  $CapacityInKB = $ dev. CapacityInKB

  $fileMgr = get-View (view Get ServiceInstance). Content.fileManager

  $datacenter = (get-View (Get - VM $VMname |)) Get-Datacenter) USER.USER) .get_MoRef)

  foreach ($disk in $vm. LayoutEx.Disk) {}

  if($Disk.) Key - eq $dev. Key) {}

  foreach ($chain in $disk. {String)

  foreach ($file in $chain.) FileKey) {}

  $name = $vm. LayoutEx.File [$file]. Name

  $fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

  }

  }

  continue

  }

  }

  }

  }

  Else if (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {Write-Host "Selected SCSI address [$scsiid] is not a RDM"}

  }

  }

  #$hd1 = New-disk hard - VM $vmname - DeviceName $rdmDevicePath - DiskType RawPhysical # this line works

  $spec = $null

  $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

  $spec.deviceChange = @)

  $spec.deviceChange += new-Object VMware.Vim.VirtualDeviceConfigSpec

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

  $spec.devicechange [0].device.capacityInKB = $CapacityInKB

  $spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

  $spec.deviceChange [0].device.backing.fileName = $filename

  $spec.deviceChange [0].device.backing.compatibilityMode = "physicalMode".

  $spec.deviceChange [0].device.backing.diskMode = «»

  $spec.deviceChange [0].device.backing.lunUuid = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). UUID)

  $spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

  $spec.deviceChange [0].device.connectable.startConnected = $true

  $spec.deviceChange [0].device.connectable.allowGuestControl = $false

  $spec.deviceChange [0].device.connectable.connected = $true

  # Take the next unused volume for HD key

  $spec.deviceChange [0].device.key = $DevKey + 1

  # 7 SCSIID UnitNUmber is reserved for the controller - then go to 8.

  If ($scsilun - eq 6) {$scsilun = $scsilun + 1}

  # Take the next unit for the HD number

  $spec.deviceChange [0].device.unitnumber = $scsilun

  # Key device for the SCSI controller

  $spec.deviceChange [0].device.controllerKey = $scsicontroller

  # Create vmdk file

  $spec.deviceChange [0] .fileOperation = "crΘer".

  $spec.deviceChange [0] .operation = 'Add '.

  $vm = get - View (Get - VM $VMname) USER.USER

  $vm. ReconfigVM_Task ($spec)

  }

  Replace-VM-RDM $vmname $scsiid $rdmname $filename

  I am working, it just need to reorganization and then the Devicename was wrong.

  Here's the script working.

  Replace-VM-RDM function {}

  Param ($scsiid, $rdmname, $vmname, $filename)

  <>

  Convert SCSI address in Vmware format

  #>

  $scsicontroller = $null

  $scsiid_split = $null

  $scsiid_split = $scsiid.split(":")

  $scsicontroller =($scsiid_split[0])

  # SCSI VMware in the GUI controller ID is a number greater than the real controller id

  $scsicontroller = [int] $scsicontroller + 1

  # Vmware waiting conntroller with 4-character id

  $scsicontroller =($scsicontroller.) (ToString()) + "000".

  $scsicontroller

  # SCSI LOGICAL UNIT NUMBER

  $scsilun = $null

  # VMware SCSI LUN ID in the GUI is a higher number than the id real lun

  $scsilun = [int]($scsiid_split[1]) #+ 1

  ###

  $vm = get-VM-name '$vmname ' | Get-View

  IF (!) (($filename))) {}

  $RDMFile = $rdmname.split("") [0] + "_RDM.vmdk"

  $filename = (($vm.)) (Config.Files.VmPathName). Replace("$vmname.vmx","$RDMFile"))

  }

  $esx is get-view $vm. Runtime.Host

  <>

  Download CanonicalName RDM Lun

  #>

  $rdmCanonicalName = $null

  $rdmCanonicalName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). CanonicalName)

  $rdmDevicePath = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

  foreach ($dev in $vm. Config.Hardware.Device) {}

  If (($dev.)) GetType()). {Name - eq "VirtualDisk")}

  If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or)

  ($dev.Backing.CompatibilityMode-eq "virtualMode")) {}

  If (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {}

  # Remove the hard drive

  $hd = get-disk hard $vm.name | where {$_.} Filename - eq $dev. Backing.FileName}

  $hd | Remove-hard drive - confirm: $false - DeletePermanently

  Write-Host "file name:" $dev.backing.fileName "

  Write-Host "Disk Mode:" $dev.backing.diskMode

  $dev.backing.deviceName

  $dev.backing.lunUuid

  $DevKey = $dev.key

  $CapacityInKB = $ dev. CapacityInKB

  <#$fileMgr =="" get-view="" (get-view="">

  $datacenter = (get-View (Get - VM $VMname |)) Get-Datacenter) USER.USER) .get_MoRef)

  foreach ($disk in $vm. LayoutEx.Disk) {}

  if($Disk.) Key - eq $dev. Key) {}

  foreach ($chain in $disk. {String)

  foreach ($file in $chain.) FileKey) {}

  $name = $vm. LayoutEx.File [$file]. Name

  $fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

  }

  }

  continue

  }

  }#>

  }

  }

  Else if (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {Write-Host "Selected SCSI address [$scsiid] is not a RDM"}

  }

  }

  #$hd1 = New-disk hard - VM $vmname - DeviceName $rdmDevicePath - DiskType RawPhysical # this line works

  $spec = $null

  $spec = new-Object VMware.Vim.VirtualMachineConfigSpec

  $spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

  # Create vmdk file

  $spec.deviceChange [0] .fileOperation = "crΘer".

  $spec.deviceChange [0] .operation = 'Add '.

  $spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

  $spec.deviceChange [0] .operation = 'Add '.

  $spec.deviceChange [0] .fileOperation = "crΘer".

  $spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

  $spec.deviceChange [0].device.key = - 100

  $spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

  $spec.deviceChange [0].device.backing.fileName = "$filename".

  $spec.deviceChange [0].device.backing.deviceName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

  $spec.deviceChange [0].device.backing.compatibilityMode = "physicalMode".

  $spec.deviceChange [0].device.backing.diskMode = «»

  $spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

  $spec.deviceChange [0].device.connectable.startConnected = $true

  $spec.deviceChange [0].device.connectable.allowGuestControl = $false

  $spec.deviceChange [0].device.connectable.connected = $true

  # Key device for the SCSI controller

  $spec.deviceChange [0].device.controllerKey = [int] $scsicontroller

  # 7 SCSIID UnitNUmber is reserved for the controller - then go to 8.

  If ($scsilun - eq 6) {$scsilun = $scsilun + 1}

  # Take the next unit for the HD number

  $spec.deviceChange [0].device.unitnumber = [int] $scsilun

  $spec.deviceChange [0].device.capacityInKB = [int] $CapacityInKB

  $vm = get - View (Get - VM $VMname) USER.USER

  $vm. ReconfigVM ($spec)

  }

  Replace-VM-RDM $vmname $scsiid $rdmname $filename

• Virtual RDM

  Hi I'm studying for my vcp 5 review I was wondering if someone could give an example of why you should use rdm in virtual mode instead of just using vmdk disks? I see no advantage

  Any advice would be great too someone at - it advice good review

  I can't think of a use case for RDM mode virtual, other than a Custer-in-a-Box (MSCS) or an existing LUN that cannot be converted for whatever reasons, but must be instantaneous. RDM had on VMFS performance benefits in the past and which could have been a case of use, but with current versions, this advantage has disappeared.

  André

• PowerCLI, Multipathing change: fixed RDM and VMFS of Round Robin

  With the new improvements in vSphere native mulit pathing (NMP) in 5.1, I tried to change my LUN to use repetition alternated according to EMC with my flare VNX practices code.

  However, I also have MSCS clusters that don't support a fixed mode according to the http://kb.vmware.com/kb/1037959.

  Later, I want to get all my VMFS volumes and set them to Round Robin and let all of my RDMs set to fixed.

  I'm hoping to dynamically so that I can leave it with the admin here to run whenever he wants, but I'm fighting to achieve.

  What I've tried so far.

  I can get all my LUNS with these commands.

  $esxcli= Get-EsxCli

  $Allmyluns = Get - esxcli.storage.nmp.device.list () | Where {$_ .device - like 'naa.*'}

  I can get all my RDM with this command

  $RDMS = get - vm | Get-hard drive | where {$_.} SCSIcanonicalname - like 'naa.* ' | Select SCSIcanonicalname

  I can put the method once I have the storage in this way

  $esxcli= Get-EsxCli

  Foreach ($lun in $allmyluns({

  $esxcli.nmp.device.setpolicy($null, $_.Name,"VMW_PSP_RR")

  }

  I have also thought about writing a csv or text file with the first command and trying to remove the entries with the second command but that is a bit past me, and I may be trying to over-complicate things unnecessarily.

  
  

  But what I can’t do is work out how to get a list whenever I want that has all the VMFS LUNS but not any of the RDM LUNS. So I can dynamically feed this into a script which updates VMFS pathing to Round Robin.

  
  

  Any help, input or ideas would be greatly appreciated

  This should help you all VMFS LUNS.

  Get-Datastore | where {$_.Type -eq "VMFS"} | %{  $_.ExtensionData.Info.Vmfs.Extent | %{    $_.DiskName  }}
  

• RDM SQL 2012 Cluster VMs on separate host

  Greetings,

  I'm looking to use RDM for a SQL Cluster in 2012 and go though the process of adding storage the second node shared, I'm a bit confused.

  I'm referencing Document from VMware, "Setup for Failover Clustering and Microsoft Cluster Service". I'm following the steps under "Clustering of virtual machines between physical hosts.  So, I advanced and added my LUNS that are on shared in the ROW to the first node storage.  The next step is to add the hard drive the second node, but this process requires me to select "use an existing drive" and select records that represent the ROW that are stored in the data store where host1 exist.  The document indicates, "select physics like compatibility mode, and then click Next.  The only option I get is, choose the Mode: persistent, Nonpersistent, or None.  I don't have an option to specify the disk as is physical or not.  I did when I created the RDM for the first host.

  Also add the disks as RDM should I stored with the virtual machine (which is on the shared storage) or should I create a separate data store and specify the data store that is on the same shared storage.  Since each of the RDM are separate LUN on the shared storage, I think I'm curious to know if its better to choose the option to store in a different data store, then with node 1.

  Any clarification on this is greatly appreciated.

  See you soon

  I suppose you want to create SQL 2012 Cluster of virtual machines on physical hosts. Please see the steps below.

  I think that there is a typographical error in documents that you won't get the same " physical compatibility mode" option again The disc is already created with a physical as on VM - 1 compatibility mode. Now you have to go with the "select Mode: persistent ' on vm - 2. Once you are done with VM - 2, VM - 2 right click, select the hard disk and observe the compatibility mode is selected physics only.

  RDM disks can be stored on the same data store shared where virtual machines are created or separate shared data warehouses. As your wish where you want to keep. One thing must remember two data stores must be shared with the two physical hosts.

  Thank you

  Atul

• Replicated LUNs, and RDM

  Hello

  We have 2 nodes and 2/place in the same place. Storage 1 is replicated to the storage 2. initially on 1 storage we have created 4 LUNs and added as RDMS to 2 knots. If first storage is off or disconnected, need to add replicated 2 LUNS to 2 2 storage nodes. If the system works on storage 1 LUN then 100 and 101 figures, 2 storage and LUN numbers 110 and 111. We need to do this using powerCLI.

  Any help would be greatly appreciated.

  LUCD, I read your amazing solutions/responses, would you please help me? Thank you.

  My mistake, I use VIProperties for ScsiLunand Monday is here.

  You can use the formula instead

  New-VIProperty-name Monday ObjectType - ScsiLun-Value {}
  Param ($LUN)

  [int] (Select-String ": L(?\d+)$ ' ')
  -InputObject $lun. RuntimeName). Matches [0]. Groups ["Monday"]. Value
  } - Force

• Political multi-channel Fixed and enter preffered paths balance for a set of RDM Lun

  Hi all

  I was hoping that someone with some experience PowerCLI might help me with the following problem.

  Short version:

  I need to adapt this script http://vmjunkie.wordpress.com/2009/01/29/balancing-lun-paths-on-your-esx-hosts-with-powershell/ to accept the entry of a canonical name text file...

  Long version:

  We have a number of LUNS of RDM used by Microsoft the Failover Clusters, in accordance with the recommendation from the storage provider (Dell), we need to define all teas LUN to have a multi-path of FIXED policy and want to balance these on both paths.

  I can get the canonical name for each LUN RDM using this script;

  Get-VM-Location"Cluster Name" | Get-HardDisk -DiskType "RawPhysical","RawVirtual"| SelectParent,Name,DiskType,ScsiCanonicalName

  (Of http://www.definit.co.uk/2013/03/powercli-script-to-set-rdm-luns-to-perennially-reserved-fixes-slow-boot-of-esxi-5-1-with-mscs-rdms/#more-1526( )

  I then manually identify the LUNS that have to be changed since the text output.  So, basically, I have a text file containing the canonical each of the RDM LUN name I need to change to fixed.

  LUNS.txt

  NAA.6000d31000331e0000000000000000c0

  NAA.6000d31000331e0000000000000000c1

  NAA.6000d31000331e0000000000000000c2

  NAA.6000d31000331e0000000000000000c3

  NAA.6000d31000331e0000000000000000c4

  NAA.6000d31000331e0000000000000000c5

  I can't run this command to set the Fixed multichannel strategy because I need the PreferredPath variable.

  Get-vmhost 'host name ' | Get-scsilun 'naa.6000d31000331e0000000000000000c0 ' | game-scsilun - multipathpolicy 'Fixed '.

  
  

  "If the MultipathPolicy parameter is set to 'Fixed', you must specify the parameter of PreferredPath."

  I can then get the paths by using this command:

  Get-vmhost 'host name ' | Get-scsilun 'naa.6000d31000331e0000000000000000c0 ' | Get-scsilunpath

  Favorite SanID state name
  ----       -----                                    -----      ---------
  FC.2000... False Active 50:00:D3:10:00:33:1e:19
  FC.2000... False Active 50:00:D3:10:00:33:1e:1 has

  Basically, I need to adapt this script (from here http://vmjunkie.wordpress.com/2009/01/29/balancing-lun-paths-on-your-esx-hosts-with-powershell/) at the entrance to a text file of canonical names.

  # Cluster-wide LUN Path Load Balancing Script

  # Written by Justin Emerson, http://vmjunkie.wordpress.com

  # Idea originally from a PERL script I saw here:

  #    http://www.yellow-bricks.com/2008/04/01/load-balancing-activeactive-sans/

  # This script requires the VI Toolkit version 1.5

  # NOTE: This script assumes that every LUN has the same number of paths.

  #       If you have multiple storage arrays, and they have different numbers of paths,

  #       I make no guarentees that this will work!

  # If you have an improvement to this script, please feel free to leave a comment on my blog!

  Write-Host"This script will modify the policy of all your shared LUNs on all ESX Servers"-ForegroundColorCyan

  Write-Host"in a Cluster to Fixed and select a preferred path in a round-robin fashion."-ForegroundColorCyan

  if ($args.Length -eq0) {$clusterName= Read-Host"Please enter the Cluster name"} else {$clusterName= $args[0]}

  $VMHosts= Get-Cluster$clusterName| Get-VMHost

  # Run through this loop for each host in the cluster

  foreach($VMHostin $VMHosts)

  {

      # Keep only disks of luntype "disk" to avoid any storageArrayController devices.

      # Filter to only objects where the ConsoleDeviceName starts with vml to avoid any DAS disks.

      # Note: I have tested both HP EVA and Xiotech storage and SAN LUNs always appear this way.

      # Please check if this is the same on your storage before running.

      $luns= $VMHost|get-scsilun-luntypedisk|

      where-object{$_.ConsoleDeviceName -like"/vmfs/devices/disks/vml*"}|Sort-ObjectCanonicalName

      $firstLUNPaths= Get-ScsiLunPath$luns[0]

      $numPaths= $firstLUNPaths.Length

      $count= 0

      foreach($lunin $luns)

      {

          if ($count-ge$numPaths) { $count= 0 }

          $paths= Get-ScsiLunPath-ScsiLun$lun

          $lun|Set-ScsiLun-MultipathPolicyFixed -PreferredPath$paths[$count]

          $count+= 1

          # Sleep for 30 seconds as I've heard some arrays dont like doing this too fast.

          Start-Sleep-Seconds30

      }

  }

  Any help would be greatly appreciated.

  See you soon,.

  Patrick

  Do you have something like this in mind?

  $esxName = "MyEsx" $lunFile = "./luns.txt"
  $lunNames = Get-Content $lunFile $VMHost = Get-VMHost -Name $esxName
  # Find the LUN with the least number of paths
  $leastLUNPaths = Get-ScsiLun -VmHost $VMHost -LunType disk | Sort-Object -Descending -Property {
    Get-ScsiLunPath -ScsiLun $_ | Measure-Object | Select -ExpandProperty Count} | Select -First 1 | Get-ScsiLunPath
  $numPaths = $leastLUNPaths.Length
  $count = 0 foreach ($lunName in $lunNames)
  {
    $lun = Get-ScsiLun $lunName -VmHost $VMHost  if ($count -ge $numPaths) { $count = 0 }
    $paths = Get-ScsiLunPath -ScsiLun $lun  $lun|Set-ScsiLun -MultipathPolicy Fixed -PreferredPath $paths[$count]
    $count += 1  # Sleep for 30 seconds as I've heard some arrays dont like doing this too fast.
    Start-Sleep -Seconds 30}
  

• Folder access Erro - RDM

  When I am trying to move a folder that contains a few - rdmp.vmdk file. I am getting error below.

  'Move the file ABCD-00406e-DR3-T2-1234 cannot access the file (name and path of the file).

  The file is in the format "-rdmp.vmdk". There are a few other files in this folder with the same extension. But all is moved to a different location than a specific file with the name ' 09 - rdmp.vmdk "is to give up the error.

  The size of all the files of the vocation is 2 MB in this folder.

  When I say "moved", I mean I went to the store of data-> traveled it-> and on top, there is an option to move files between the data store. I'm trying to move files using this option and NO SVMotion.

  The virtual machine has been svmotioned to the data store different today morning. These rdm files are not mapped to the virtual machine.

  Please suggest.

  the RDMP.vmdk files are pointers to the RDM LUN, in addition to the VM ad RDM disks. These files will always continue in the virtual machine folder, even after the withdrawal of the ROW of the virtual machine.

  You can safely remove it if it gives any error when copying the file to the virtual machine. You can add the ROW to the virtual machine with the LUN after a migration file successfully.

• Do &gt; 2 TB physical RDM NEED Directpath IO?

  I've been struggling with this for over a week now so I could really use some advice.

  5.1 ESXi

  I need to install three hard drives 3 to and give them direct access to a virtual computer running FreeNAS (or other) for a ZFS ZRAID configuration to store data.

  From my research, it looks like a physical RDM is my best solution. I want that the BONES of the VM to exert direct and complete control to readers with title bit VM intervention as possible. Reason being, I want readers to be able to be exchanged in a physical server to spare if necessary to recover the data.

  I am able to do a physical RDM using the command line and I'm able to add them in a virtual machine. Once attached, they do not work in the operating system. The operating system can see the disks, but may not use it.

  I am unable to make the virtual RDM because obviously, readers are more 2 TB - 512 k.

  Where can I activate? Do I NEED to have material supporting Directpath IO to use the large RDM? I can't confirm this, but it's the only thing else that I can think of. New versions of ESXi should support up to 64 TB with the RDM...

  My hardware does not support Directpath IO so I can't spend it just a map of entire storage with the disks attached. But I can buy a new motherboard supporting the pull-out decision if that's the answer. Also, for the physics of the RDM will I need to pass to the virtual machine a whole controller (card) or can I just use the physical RDM as on the use of the SATA connectors on board?

  Any advice would be greatly appreciated. ;-)

  What type of storage do you use? ISCSI or FC?

  You certainly don't need direct i/o path for a raw device mapping physics > 2 TB (-512). So that you can safe money

  What's that it is mentioned in vmkernel.log when you join the RDM?