1 2 Previous Next 18 Replies Latest reply on Nov 20, 2007 3:09 AM by dmaster Go to original post
      • 15. Re: Copy .vmdk files from Fibre to Fibre instead of using Ethernet on ESX Server 2
        Texiwill Guru
        vExpertUser Moderators

        Hello,

         

        Use of 'cp' or 'mv' does not use the ethernet, you login to the service console and do the following:

         

        cd /vmfs/

        cp -r VMName.vmdk /vmfs/volumes/VMname

         

        There is absolutely no network involved besides the ESX server and the fibre network already there. However this is not a 'fast' option as ESX throttles all copies/writes to the FC down to something painfully slow. If I change the 'cp' to 'scp' then there is also no network involved as no host was mentioned.

         

        Yet if you do not have an ESX server on both SANs then this is also impossible.

         

        Other options,

         

        Mirror inside the SAN Fabric LUN to LUN on the ESX v3 SAN. This assumes they at least talk to each other on the same fabric.

        Make a backup of the running VM to tape then restore the VM on ESX v3 import and launch.

         

        Without the ability to do dMotion, vMotion or having an ESX server on both fabrics you have to do the migration by hand somehow. You need to move the data.

         

        Best regards,

        Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

        1 person found this helpful
        • 16. Re: Copy .vmdk files from Fibre to Fibre instead of using Ethernet on ESX Server 2
          dmaster Expert
          vExpertVMware Employees

           

          Hello Texiwill..

           

           

           

           

           

          thanx for the help.. i was not aware of the fact "That ESX throttles all copes/writes to the FC down to something painfully when using 'cp'or 'mv' on the service console".

           

           

          i will test thursday a migration with vmkfstools .. i will post the results.. if that results in a very good speed.. i have my answer..

           

           

          i didn't check it because the cold migration through virtual center took awfully long..

           

           

           

           

           

          regards,

           

           

          Dennis

           

           

          • 17. Re: Copy .vmdk files from Fibre to Fibre instead of using Ethernet on ESX Server 2
            Texiwill Guru
            vExpertUser Moderators

            Hello,

             

            If you did a Cold Migration from HostA to HostA and only changed the Storage location of the VMs then you in effect did the same as a cp or use vmkfstools. If you however went from HostA to HostB then you went over the wire.... I suggest trying the first option. If you do try from the CLI, you will not need to use vmkfstools. A straight 'cp' from VMFS to VMFS is sufficient.

             

            Best regards,

            Edward L. Haletky, author of the forthcoming 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', publishing January 2008, (c) 2008 Pearson Education. Available on Rough Cuts at http://safari.informit.com/9780132302074

            • 18. Re: Copy .vmdk files from Fibre to Fibre instead of using Ethernet on ESX Server 2
              dmaster Expert
              vExpertVMware Employees

              Hello Texiwill,

               

              I did a couple of tests..

               

              using the "cp" command from datastore on DMX 2000 to datastore on shared LUN (DMX 2000 / DMX 3) took me 25 minutes for 9GB

              using Virtual Center 2 with cold migrate this took me also 25 minutes

              using vmkfstools on CLI this took me 15 minutes..

               

              but this still this is not the proper speed..

               

              when i do a dmotion (cold migration) from the datastore with the shared LUN (DMX2000 / DMX 3) to the final datastore on DMX 3..

              from the ESX 2 host to the ESX 3 host it took me only 5 minutes.. how is this possible ?

               

              regards,

               

              Dennis Derks

              1 2 Previous Next