Problema Storage VMotion

Similar Questions

• problem of storage vmotion - requested storage vmotion would change at the same time

  Shalom everyone!

  How are you? hope, do

  I have the following configuration:

  LIC: 1 vCenter Server 4 Standard 2. company vSpehere 4 Plus 1-12 cores per processor * 8CPUs

  ESXi 4; 1 vCenter Server

  When I try to migrate virtual machines to a store of data to another it gives an error. But if I migrate a virtual computer (from storage to another) it looks ok:

  < the requested storage vmotion would simultaneously change storage location of the virtual machine and the host of execution; However, this is not supported on the host Source "production-host1" >

  < the requested storage vmotion would simultaneously change storage location of the virtual machine and the host of execution; However, this is not supported on the host Destonation "production-host2" >

  Thank you very much in tips!

  This image shows the vm on several hosts of source.

  -KjB

• 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

• 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 fails with the error below

  I'm trying to run a virtual machine's storage vMotion. It fails with the error below.

  This method is disabled by 'moref = 17705'

  #1 method - manually remove the entry from the VCDB.

  • Stop the Service of VC.
  • Connect to the SQL Instance.
  • Run the SQL for VCDB.
  • Select * from VPX_VM WHERE name LIKE '% VM_Name % '.
  • Note the ID of VM in column 1.
  • Validate the stale entry.

  Select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID".

  • Remove obsolete entries.

  delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = "vm - ID"

  • Start the VC service.
  • Try Storage vMotion.

  Method #2-si this does not work, save the *.vmx file once again which will fix the problem.

  Note: To do this, you will be required to server unavailability.

  • Power off the virtual computer.
  • VM unregistered inventory.
  • Navigate to the path of the data store and VMX re-register.
  • Start the virtual computer.
  • Try Storage vMotion.

• 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!

• Storage test 55 certification vmotion, storage vmotion fails with "Could not lock file" on the virtual machine during storage vmotion

  In my view, that it is a known problem in ESXi 5.5 Update 2 release notes, someone knows a solution yet? This is an excerpt from the release notes:

  • Attempts to perform live storage vMotion of virtual machines with RDM disks can fail
    Storage vMotion of virtual machines with RDM disks can fail and virtual machines can be considered in turned off of the State. Attempts to turn on the virtual machine fails with the following error:
    
    Cannot lock the file
    
    Workaround: No.

  VMware support for the record said that the patch will update 3, it is known as an intermittent problem. Finally, it happened to me on the 9th attempt.

• 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é

• Storage vMotion to vCenter

  I have a Windows 2008 VM for vCenter on my lab. I'm under ESXi 5.1.

  I would like to know if it is possible to storage vMotion this Windows 2008 VM to a different data store, without losing of damaging vCenter server.

  I use Express database on Windows 2008.

  Yes, if your vCenter is licensed for Storage vMotion you can do it without problem.

• 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.

• Storage vMotion - Shadow created VM!

  Hello

  I cancelled a task of storage for a virtual machine vMotion and now I have two virtual machines with the same name. I understand Storage vMotion creates a shadow VM as part of the migration.

  The cancellation has not been cleaned so I now a VM THAT under tension and work and a VM turned off with 0MB of data warehouses.

  Is it OK to goahead and remove this 'Shadow' VM?

  I look forward to hear from anyone with help.

  Thank you

  Peter.

  I guess, there is no problem.

  Just remove the inventory and then delete the folder.

• Senza thanks storage VMotion

  Hello to all

  Premetto che he mio e uno scrupolo più una domanda che in quanto credo, unfortunately, gia di know the risposta :-D

  veniamo al therefore: sto valutando the della functional di senza thanks introdotta nella versione 5.1 storage vmotion use;

  He problema e che i 2 cluster hanno a level di VCA different (stessa Intel architecture), quindi mi viene da Winegardner che he processo di validazione fallirebbe, my non ho trovato nessun esplicito re questa limitazione nella doc ufficiale di questa characteristic specifica.

  The mia speranza, ops domanda e secondo voi e possibile quindi?

  Saluti

  Ciao,.

  is non ho capito male, 2 cluster hai con lo stesso tipo di CPU Intel, pero con configurati 2 livelli VCA different. Perch is the sound CPU all equal?

  The VM you want migrare che da a cluster all'altro, risiede su uno No thanks dai storage 2.

  Ad ogni modo migrazione non Può avvenire has accesa VM, che lo storage sia thanks o meno, in quanto nel passaggio VM TR troverebbe ad andare a run known una che could avere delle istruzioni o diverse functional CPU. Abilitando the VCA in ogni caso, vai a mascherare o "castrare" in queste functional.

  The Unico modo che hai by migrare VM e da spenta.

  Ciao

  Francesco

• Storage vMotion-Direct between ESXi hosts

  Hi all

  It is my first time on the boards, I hope it's the right way to go on this subject.

  I have problems with Storage vMotion, it's not a set up us would use normally, rather than by necessity with the current scenario.

  We have a desktop which has 2 x 5.1 ESXi hosts. They do not have a budget for SAN with the installation of HBA, and it is only a single requirement. I have to migrate virtual machines from one to the other, but with no external storage. I wait with Storage vMotion directly from a local data store to another.

  I activated the software iSCSI on both ESXi hosts

  Created a vSwitch separated with a VMkernal on two physical hosts

  The two VMkernals are on a separate subnet * 172.16.1 and production vSwitch is 192.168.5. *.

  The NIC allocated for the 172.16.1 network. * is both connected to the same physical switch.

  I ping the VMkernal and the vmkping the VMkernal

  Scan for storage again and nothing shows up.

  I used software iSCSI before, for a long time so I'm probably rusty. Dynamic discovery is normally indicated in the SAN to pick up storage, and finds it just local storage on each host itself.

  In this scenario, I told the IP address of the ESX2 VMkernal on 172.16.1 ESX1. * since I have no external storage. I think it is, I'm wrong, but I don't know what else to do to recover local data warehouses.

  Any ideas to try would be very appreciated.

  Thank you

  Sorted by using 5.1 feature Shared-Nothing vMotion

• Storage vMotion possible with ESXi Std Edt or not?

  Hi all

  We have two implementations of VMware with ESXi Standard edition licenses installed on the two site. A site has vCenter Server Foundation edition while the other has vCenter Server Standard Edition.

  The problem is that the site with vCenter Std and vSphere 5 Std doenst allow storage vMotion (see image below)

  

  While, on the other hand, site 5 Stnd vSphere with vCenter Foundation allows storage Vmotion (see image below)

  

  How is it so that vSphere Stndard this edtion of different characteristics in different places?

  I had recorded the call and found the solution... VSphere 5.0 and 5.1 gives really different set of features with the same Std license vSphere.   Take a look at the link for options available with vSphere 5.0 and 51 below.

  1 compare vSphere 5.0 editions

  Compare the editions of vSphere VMware for Cloud Computing, server and data center virtualization

  VSphere editions 2 - compare 5.1

  Compare VMware vSphere editions: managed Virtualization & amp; Cloud Computing

  For a test, I used the same Standard edition server with 5.1 key to it has worked well with Storage vMotion Option available :-)

• Cannot Storage Vmotion between EMC Celerra NFS and NFS VNX

  Recently we have improved our infrastructure VMware 3.5 to 5.0. Managed to migrate all virtual machines to the Esxi5.0 without any problems. More recently, we bought new storage EMC VNX 5300, set up and configured the NFS storage for the early. All the warehouses of new data related to blades and all storage pools, old and new can be found under vCenter.

  Problem we have is that we can not Storage vMotion virtual machines of the old Celerra NFS for new NFS VNX stores. It comes back with the error "cannot access file VM VNX {datastore} filename '. We got a similar message appears when you try to create a new virtual machine or import an OVF on VNX new data warehouses.

  We have the license of the company, with Dell M600 blades with EMC storage as mentioned above.

  Pointers would be appreciated

  Kem

  Thanks for your contributions, but I solved it. A bit of a 'schoolboy error', but although I had added to the VMKernel IP in the host root and read-write in the NFS export properties, I also need to add the IP address of the hosts/blades. Storage vMotion successfully in new stores VNX. THX Kem