Storage vmotion, leaving something behind

Similar Questions

• Storage VMotion, leaving the additional disks when they are

  I want to move a virtual machine but, let one of the additional attached disks where it is.

  When you use the interactive for svmotion, at this stage, «if you want to stay with the VM disks then skip this step...» You want to place the disks individually. I say Yes and identify the additional path on the vmdk disk.

  He then asks the destination...

  1. I think that if I enter the current data (source) to the destination store, this additional disc will just stay where he is. Is this correct?

  2. I also want to make sure that when svmotion sees that I chose the data source as a destination store, it leaves just here. Specifically, I want to make sure that it is not yet really moving the disc but in the same data store. It is a big drive and I don't have enough space on the data store if she done something like this.

  The answer lies in the help file for svmotion one thing I noticed, is that the syntax is correct, except that single quotes should be in double quotes ".» Other than that, the command line below will do exactly as you want, and that's essentially what you thought. Files will not overwrite themselves, then it will not try to copy the same disc in the same data store.

  Move the storage for a virtual machine on new_datastore, but let the disc 1

  and 2 in old_datastore:

  SVMotion - datacenter = "My DC" - vm = "[old_datastore] myvm/myvm.vmx:"

  new_datastore' - discs = "[old_datastore] myvm/myvm_1.vmdk:"

  "old_datastore, myvm/myvm_2.vmdk: old_datastore '.

  -KjB

  VMware vExpert

  Post edited by: kjb007: trying to fix the formatting.

• Storage vmotion very slow

  Storage vmotions run very slowly. The virtual machine that has a 60 GB HARD drive. I tried different storage and still the same result. I have even upgraded to a network of 10 GB with the same results. I opened an evidence of support and the engineer told me vmotion will not use the link in full speed but it seems quite slow for the numbers I get. I hope I have provided enough information below for assistance. I hope that it is something I am doing wrong...

  Hosts:

  3 x ESXi host. Two are updated to version 6.0 1 and a version 5.5.

  Dell PowerEdge R610

  Xeon E5540 - 8 x 2.53GHz

  48 GB OF RAM

  10 GB for storage and vmotion traffic

  4 x 1 Gb NIC for vm traffic interconnection

  All storage is on the shared storage. The only local thing is the operating system

  VMware EVC mode for the production of Intel's Nehalem.

  Storage

  Supermicro NAS 2 to 4 x 4 RAID 10 storage pools

  Integrated 10 GB NIC

  QNAP TS - 469U - PR to 4 x 4 RAID 5 NAS

  2 x 1 GB NIC aggregated link

  Network

  All 3 hosts and NAS are connected with a Netgear dedicated 10 GB switch (low-end model).

  Using a standard vswitch

  Problem

  1 ESXi host has a computer virtual stored on storage on NAS Supermicro 1 pool. When a storage vmotion is running on a virtual machine that has a 60 GB VMDK, it takes a long time to complete. He started at 09:36, and is now 61% fine at 10:58.

  2. the network of 10 GB is where the vmotion traffic is allowed.

  3. If I use a link to 10 GB or a 1 GB link, I get the same speed.

  4. I have disabled all VM at a time given for the trial and who has not helped either.

  5. I tried a QNAP so storage vmotion, and I get the same speed.

  I use connection CAT6A cables. I have fine tuned for storage, and it seems to work better now. Seems to be linked to "writing - sync" as ESXi.

• Storage vmotion esxi 5.5 to 6.0 does not not for some vm

  In a test cluster with 2 nodes with no storage storage shared (local only), host vmotion 5.5 to 6.0 host does not work.

  before the upgrade, I moved all the vm to a host.

  Then I upgraded to 6.0 host and tried to move all the VMS to the host 6.0 updated (moving host + storage).

  20 VM, 5 have been moved to the new host.

  Everyone always get error below.

  The VM Client are all the vm version 10 (but some of them improved 8 or 9).

  ClientOS Windows 2008, 2012 r2 and linux. Some with vmx3, some with e1000.

  The machines can be moved when turned off.

  After the off-vmotion, storage vmotion from 6 to 5.5 and return of 5.5 to 6 works again.

  < code >

  Failed to copy one or more of the disks in the virtual machine. See the journal of the virtual machine for more details.

  Impossible to implement disks on the destination host computer.

  vMotion-Migration [-1408040447:1427943699552189] konnte nicht den Stream-Keepalive read: Connection closed by remote host, probably due to timeout

  Beim Warten auf Daten Fehlgeschlagen. Fehler 195887167. Connection closed by remote host, probably due to delay.

  < code >

  VM - log:

  < code >

  2015-04 - T 02, 03: 01:34.299Z | VMX | I120: VMXVmdb_SetMigrationHostLogState: transits State hostlog of immigration to migrate "at source" mid 1427943699552189

  2015-04 - T 02, 03: 01:34.307Z | VMX | I120: MigratePlatformInitMigration: file DiskOp set to /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1-diskOp.tmp

  2015-04 - T 02, 03: 01:34.311Z | VMX | A115: ConfigDB: parameter migration.vmxDisabled = 'TRUE '.

  2015-04 - T 02, 03: 01:34.326Z | VMX | I120: MigrateWaitForData: waiting for data.

  2015-04 - T 02, 03: 01:34.326Z | VMX | I120: MigrateSetState: transition of State 8 to 9.

  2015-04 - T 02, 03: 01:34.467Z | VMX | I120: MigrateRPC_RetrieveMessages: was informed of a new message to the user, but cannot process messages from State 4.  Leaving the message in queue.

  2015-04 - T 02, 03: 01:34.467Z | VMX | I120: MigrateSetState: transition of State 9 to 10.

  2015-04 - T 02, 03: 01:34.468Z | VMX | I120: MigrateShouldPrepareDestination: remote host does not support an explicit step to prepare migration destination.

  2015-04 - T 02, 03: 01:34.469Z | VMX | I120: MigrateBusMemPrealloc: BusMem complete pre-allocating.

  2015-04 - T 02, 03: 01:34.469Z | Worker #0 | I120: SVMotion_RemoteInitRPC: completed.

  2015-04 - T 02, 03: 01:34.471Z | Worker #0 | W110: SVMotion_DiskSetupRPC: related disc expected but not found for the file: /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1-ctk.vmdk

  2015-04 - T 02, 03: 01:34.471Z | Worker #0 | W110: MigrateRPCHandleRPCWork: callback RPC DiskSetup returned UN-successful State 4. RPC fault.

  2015-04 - T 02, 03: 01:34.493Z | VMX | I120: VMXVmdb_SetMigrationHostLogState: hostlog transits of State to fail to migrate 'from' 1427943699552189 environment

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: MigrateSetStateFinished: type = 2 new State = 12

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: MigrateSetState: transition of State 10 to 12.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: Migrate: list cached migration error message:

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: [msg.migrate.waitdata.platform] failed waiting for data.  Error bad003f. Connection closed by remote host, probably due to delay.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: migration of vMotion [vob.vmotion.stream.keepalive.read.fail] [ac130201:1427943699552189] failed to read streams keepalive: Connection closed by remote host, probably due to timeout

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: Migrate: cleaning of the migration status.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: SVMotion_Cleanup: cleaning of XvMotion State.

  2015-04 - T 02, 03: 01:34.502Z | VMX | I120: Closing all disks in the virtual machine.

  2015-04 - T 02, 03: 01:34.504Z | VMX | I120: Migrate: Final status, who reported the force.

  2015-04 - T 02, 03: 01:34.504Z | VMX | I120: MigrateSetState: transition of the State 12-0.

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: Migrate: Final status, which reported VMDB.

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: Migrate Module switch has failed.

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: VMX_PowerOn: ModuleTable_PowerOn = 0

  2015-04 - T 02, 03: 01:34.505Z | VMX | I120: SVMotion_PowerOff: does not not Storage vMotion. Nothing to do

  2015-04 - T 02, 03: 01:34.507Z | VMX | A115: ConfigDB: parameter replay.filename = «»

  2015-04 - T 02, 03: 01:34.507Z | VMX | I120: Vix: [291569 mainDispatch.c:1188]: VMAutomationPowerOff: power off the power.

  2015-04 - T 02, 03: 01:34.507Z | VMX | W110: /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1.vmx: cannot remove a link symbolic/var/run/vmware/root_0/1427943694053879_291569/configFile: no such file or directory

  2015-04 - T 02, 03: 01:34.507Z | VMX | I120: WORKER: asyncOps = 4 maxActiveOps = 1 maxPending = 0 maxCompleted = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Past vmx/execState/val of poweredOff

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 0 additionalError = 0

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4331]: error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): unknown error

  2015-04 - T 02, 03: 01:34.529Z | VMX | I120: Vix: [291569 mainDispatch.c:4292]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  < code >

  Any idea to solve this problem? Maybe it's a bug with vsphere 6.0

  Given that some machines were functioning and vmotion later in both directions from 6.0 to 5.5 works, I think that is no configuration error.

  Hello

  It seems that there could be a bug or that guests have difficulties to negotiate the transfer of drive on a network. VMotions storage are carried out via the management network (limitation of hard due to the codification)-are you sure that management networks are not overloaded or that they operate at the desired speed? This also happens with machines that have actually disabled followed block? It seems that this could be a problem.

  In addition, you use the 'old' client or Web client? It is possible that some features in vSphere 6.0 may have been omitted in the old thick client.

  Below are the errors:

  2015-04 - T 02, 03: 01:34.468Z | VMX | I120: MigrateShouldPrepareDestination: remote host does not support an explicit step to prepare migration destination.

  2015-04 - T 02, 03: 01:34.471Z | Worker #0 | W110: SVMotion_DiskSetupRPC: related disc expected but not found for the file: /vmfs/volumes/526d0605-8317b046-f37e-0025906cd27e/test1/test1-ctk.vmdk

  Thanks for the answers in advance and good luck!

• Where can I download Storage vMotion Plugin?

  Hello guys,.

  I'm looking to download Storage vMotion Plugin in vmware.com but I can't find...

  I have the vCenter Server version 5.1 Build 1235232... Is there something I missed?

  Thanks in advance for your answer

  Best regards

  
  

  Storage vMotion to migrate a virtual machine to another data store.  VMotion allows you to migrate a virtual machine to another host.  If you want to migrate a virtual machine to another host and store data at the same time, the virtual machine must be stopped.

  Also, please do not forget to mark answers useful and accurate.

  Thank you

• flying over the vmdk files after storage vmotion

  People,

  I finished a few vmotions storage and I see that there are some vmdk files left belonging to a virtual machine by flying over in the source data store.

  Storage vmotion however was very good. Time last modified files are several months old.

  If the vmdk files are old players was dismantled some time back?

  There are also a few - zdump.000 left side files in source data warehouses. should you be worried about those?

  Rahul-

  Although I suppose the files are orphans, I always double-check for use before deleting. Virtual disk file (hard) can be changed only in case Active snapshots exist for them. What you can do is run RVTools, to see if these files appear as 'Zombies' and if so, I would say you first create a subdirectory and move the "orphans" files above and - if everything continues to work as expected - delete at a later date. Alternatively you can check the vmware.log of the virtual machine file to see if the files appear here.

  Zdump files are created if something unexpected occurs. However, it is difficult to say what the brought to be created and if they are old and have any problems, you can delete just them.

  André

• County of vMotion and Storage vMotion over the last 24 hours

  I am under the below a line to count the number of vMotion and Storage vMotion, which happened in the past 24 hours in the middle and it not give me the required result, but when I combine them in the script that I use to collect additional information, it's just returns 0 (zero) as the County.

  Rely on Storage vMotion and vMotion

  Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) |

  Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.relocate" - or $_.Info.DescriptionId - eq "StorageResourceManager.applyRecommendation"} |

  Measure-object | Select-Object - ExpandProperty County

  Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) |

  Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.migrate"} |

  Measure-object | Select-Object - ExpandProperty County

  Combined script

  Get-Cluster |

  {ForEach-Object

  $Cluster = $_

  $VMHost = $Cluster | Get-VMHost

  $CpuUsageMhz = $VMHost | Measure-object-property CpuUsageMhz-sum | Select-Object - ExpandProperty sum

  $CpuTotalMhz = $VMHost | Measure-object-property CpuTotalMhz-sum | Select-Object - ExpandProperty sum

  $MemoryUsageGB = $VMHost | Measure-object-property MemoryUsageGB-sum | Select-Object - ExpandProperty sum

  $MemoryTotalGB = $VMHost | Measure-object-property MemoryTotalGB-sum | Select-Object - ExpandProperty sum

  $Cluster | Select-Object - property @{Name = "ClusterName"; Expression = {$_.} Name}},

  @{Name = 'vSphere HA'; Expression = {$_.} HAEnabled}},

  @{Name = 'Analysis HA-Host'; Expression = {$_.} ExtensionData.Configuration.DasConfig.HostMonitoring}},

  @{Name = 'HA-Failover capacity'; Expression = {$_.} ExtensionData.Summary.CurrentFailoverLevel}},

  @{Name = 'HA-Admission Control'; Expression = {$_.} HAAdmissionControlEnabled}},

  @{Name = 'Configuration problem'; Expression = {[string]: join (",", ($_.))} ExtensionData.ConfigIssue | {{(Select-ExpandProperty FullFormattedMessage))}}.

  @{Name = 'vSphere DRS'; Expression = {$_.} DrsEnabled}},

  @{Name = "The DRS automation level"; Expression = {$_.} DrsAutomationLevel}},

  @{Name = "Use of the CPU (Mhz)"; Expression is {$CpuUsageMhz}},

  @{Name = "Cpu (Mhz) Total"; Expression is {$CpuTotalMhz}},

  @{Name = 'Cpu use (%) » ; {Expression = {[Math]: Round(100*$CpuUsageMhz/$CpuTotalMhz)}},

  @{Name = "use (GB) of memory"; Expression is {$MemoryUsageGB}},

  @{Name = "Total (GB) of memory"; Expression is {$MemoryTotalGB}},

  @{Name = 'use of memory (%) » ; {Expression = {[Math]: Round(100*$MemoryUsageGB/$MemoryTotalGB)}},

  @{Name = 'VMS NB'; Expression = {$_ |} Get - VM | Measure-object | {{Select-Object - ExpandProperty County}},

  @{Name = 'Virtual machines without VMXNET3 NB'; Expression = {$_ |} Get - VM | Get-NetworkAdapter | WHERE-object {$_.} Type - not "Vmxnet3"} | Measure-object | {{Select-Object - ExpandProperty County}},

  @{Name = 'VMotions NB'; Expression = {$_ |} Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) | Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.migrate"} | Measure-object | {{Select-Object - ExpandProperty County}},

  @{Name = 'SvMotions NB'; Expression = {$_ |} Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) | Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.relocate" - or $_.Info.DescriptionId - eq "StorageResourceManager.applyRecommendation"} | Measure-object | {{Select-Object - ExpandProperty County}}

  } |

  Export-Csv "C:\Script\Clusters.csv" - NoTypeInformation - UseCulture

  Could you please someone check the script above and let me know if there is something wrong

  Thank you!!

  But wait a minute, you mean that the "Num vMotions" and "Num of SvMotions" properties have a value of 0?

  This is normal, since you ask for events for the entity of the group, while you should do it for all the virtual machines in the cluster.

  Try the attached version.

• Rules of affinity that automatically triggers the Storage vMotion

  Hi all

  Is it possible to set up a rule of affinity or something similar that automatically triggers a Storage vMotion, if a virtual machine is a vMotion on another host.

  For example, suppose we have 2 sites, 1 ESXi host at each site.

  If the DRS triggers a vMotion for a virtual machine on site A to site B, I want to automatically change the data at site B store. So vSphere must trigger Storage vMotion to the data on site B store.

  Is this possible?

  Thanks for the replies

  Dario

  It is not possible out of the box.

  You would need to script a PowerCLI logic or another language that monitors events or periodically checks the location of the execution of virtual machines and their data store location, trigger svMotions if necessary.

• script storage vmotion which move the config files too?

  Hello

  I have a VMWare admin for a long time but I am very new to the PowerCLI and script. I could find, modify and use scripts that do a simple storage vmotion: all disks go to a data store - but also one that can move independently - disk hard drive 1 to the data store X, hard disk 2 to the data store Y. However, I can't figure out how to recover the configuration files as well. I just got the book "VMWare vSphere PowerCLI reference", which confirmed my fears that you can't call these configuration files (and Exchange files, etc.) as a single parameter as you can hard drives. You use the SDK, that I have even fewer know that the CLI of power!

  I keep my BONES (disc 1) files and configuration files in 'BONES' labeled data warehouses, so whenever I move a Hard Disk 1, I want to keep the configuration files, swap files, newspapers etc. with the OS disk file and move them to another "OS" datastore. No matter who else set up like this and already is figuring out how to automate this type of move? I know that I can move the entire VM to a data store, then move the hard drives 2 and above, but it's a waste of time and I have no OS LUN that are too big.

  Thanks in advance for any help you can give!

  Thanks for buying the book, I hope that you may find useful.

  Yes, you are right, there is no single cmdlet that lets you move only the configuration files.

  You can do this with the RelocateVM_Task method in the SDK however.

  Such a script, in its simplest form, will look something like this.

  $vm = Get-VM MyVM
  $configDS =Get-Datastore -Name "MyDS1" $hdDS = Get-Datastore -Name "MyDS2"
  
  $spec = New-Object VMware.Vim.VirtualMachineRelocateSpec $spec.Datastore = $configDS.Extensiondata.MoRef
  Get-HardDisk -VM $vm | %{
      $hdSpec = New-Object VMware.Vim.VirtualMachineRelocateSpecDiskLocator    $hdSpec.Datastore = $hdDs.ExtensionData.MoRef
      $hdSpec.diskId = $_.Extensiondata.Key
      $spec.Disk += $hdSpec}
  $vm.ExtensionData.RelocateVM($spec,"defaultPriority")
  

  You specify the destination of the files "config" in the line of $configDS.

  Hard disks will be migrated to the data store that the script gets in $hdDS.

  If you want to only move the configuration files, you specify the same data store to which they are already for hard disks.

  $vm = Get-VM MyVM
  $configDS =Get-Datastore -Name "MyDS3" $hdDS = Get-Datastore -Name "MyDS2"...
  

• After Storage vMotion my VMDK is thin, even after the selection of thickness

  Hello

  I'm looking to convert the thick disks via svMotion.  I try to avoid interruptions of service on the virtual machine.  We have no space to achieve the svmotion in another data store.  So I thought that I move it to local storage on the host and then again to the NAS.

  I have svMotioned the virtual machine from a NAS device to the storage local to the host, verified size put into service and it was thick with success.

  So, I then tried to bring him back to the NAS and selected thickness, and as soon as it was over the disc was thin again.

  Why my storage vMotion finish and leave my discs to thin format?  Any ideas on what gives here?

  Sorry if this has been answered elsewhere, I searched and have not found a lot of thickness.  Does not appear that many use this format in good standing.  We are a large company and do not actively monitor the use of the disc - we use the thick option to avoid any downtime due to space problems.

  Thanks for any idea!

  The format of the virtual disk on a NAS storage is dictated by the NAS. Take a look at the configuration guide http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf (page 101)

  André

• Storage vmotion the VMS residing on a store of data to another data store

  I need Storage vmotion all virtual machines residing on a data store to another store of data within the same cluster. All virtual computers have a vmdk... someone has a script or something similar...

  Also, you should be able to:

  Get-Datastore "OldDatastore" | Get-VM | Foreach { Move-VM -Datastore (Get-Datastore "NewDatastore") }
  

  If you found this information useful, please consider the allocation of points for correct or helpful.

  Alan Renouf

  http://Virtu-al.NET

• Storage vMotion GUI in the roadmap - individual placement of discs?

  I use storage vMotion the remote CLI much and I use almost exclusively the function to simply move some disks and leave some wherever they are. I saw the video demo of the user interface provided and it seemed to make a gesture of any disk group, just like the non-Plug-in support for Virtual Center did. Does anyone have knowledge of defining targett if different volumes of individual disk in the new GUI?

  Yes, click on the Advanced button. Then you can choose the target for each disc.

• Storage vmotion with several virtual disks

  I have a couple of virtual machines with virtual disks on them.  I have a need to pass one of the virtual disks in a different lun while leaving others in the current location.  I would like to move this disk without impact on our users, which means that I like to keep the operational machine.  I did several Vmotions storage with great success.  I want to know is if there is a way to use Storage Vmotion and tell him to move only a single virtual disk on a multi VM disk.

  Does anyone know if there is a way to do this?

  Thank you!

  Download and install the RCLI.

  Run the sVMotion intereactive mode.  This will guide you through the process with the ability to move the individual disks.

  command line must start with

  SVMotion - interactive

  If you feel this or any other answer was 'useful' or 'proper' Please consider awarding points

• Storage vMotion with Syncrep on Equallogic San

  Hello

  We recently bought 2 San Equallogic (PS6510ES) and turned on synchronous replication between them.

  We use ESXi 5.5 and followed the best practices guide to disable TCP ack and 60 logintimeout value.

  Everything seems to work fine until we tried Storage vMotion/migration and cloning VMS on the San.

  When we did the migration of 2 volumes on the EQL SAN storage (the target volume has active syncrep), the target volume will be out-of-sync and then the storage vMotion will hang sometimes.

  The worst is when such a problem has occurred, all other volumes on the EQL constantly to respond also. All volumes will not respond until we rebooted the corresponding ESXi host (NOTE: simple shut down/power outside the host won't help.) The San EQL will only return to normal after a reboot of the ESXi host).

  If we pause / off the syncrep before Storage vMotion, the problem will not happen.

  Is this normal or not?

  In addition, whenever the problem occurred, the latency of writing the corresponding volume will be dry and we will receive alerts similar to the following:

  connection iSCSI target ' xx.xx.xx.xx:3260, iqn.2001 - 05.com.equallogic:xxxxx - test-volume ' initiator 'xx.xx.xx.xx:xxxxx, eqlinitiatorsyncrep' failed for the following reason:

  Initiator, disconnected from the target when connecting.

  Thanks in advance.

  Hi Joerg,

  What is a #SR? I opened a record of support to 24 June and still waiting for Dell to contact me.

  Ryan

• question of vMotion and storage vMotion

  I have everything set, UCS 5108, ESXi host, VMs, I don't have a SAN connection yet... My question is if I can enable vMotion? Let's say I have a cluster in vCenter, within this group, I have attached two ESXi host, win2008 VM in an ESXi and running, I can migrate (using vMotion) as win2008 VM to an another ESXi without connection SAN?

  How storage vMotion to an ESXi host hardrive to an another ESXi host hardrive? Is this possible?

  Note: I have not connection SAN in this configuration

  One of the requirements for vMotion is shared storage that would allow visibility between source and destination ESXi hosts. (SAN, iSCSI or NFS).

  http://www.VMware.com/PDF/vSphere4/R41/vsp_41_dc_admin_guide.PDF

  pages 210 to 215

  You can use OpenFiler as an iSCSI for lab tests SAN

  http://www.Openfiler.com/community/download/

  Thank you

  Zouheir