Copying vmdk file from a 3.0.2 server/SAN to new 3.5U4 Server/SAN

[willymaykett]

Hi everyone.

I am setting up a new ESX 3.5 U4 server and a new SAN storage connected via fibre switch.

I have copied over an vmdk file which is use as a sysprep'd W2k3 server base from the existing 3.0.2 server/datastore and successfully copied it, that is no errors etc.

I then tried to create a new VM on the ESX 3.5 server and when I browse the store, the vmdk file does not show up?

Is there anything special I need to do? If so, what problems will this have when I try and connect a new ESX3.5 server to my existing 3.0.2 datastore?

I do not have vCentre, etc, just ESX standard at the moment.

Thanks

[Gerrit_Lehr]

I highly recommend using the free vmware converter (http://www.vmware.com/products/converter/) for this task since it will do all the work for ypu and prevent you from such issues.

Kind Regards,

Gerrit Lehr

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

[LarsLiljeroth]

Hi

Can you see the file if you use the console or the datastore browser.?

Best regards

Lars Liljeroth

-

---

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[depping]

what are you using to browse the datastore?

I also recommend using vmware converter by the way... automation rules

Duncan

VMware Communities User Moderator | VCP | VCDX

-

---

Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[willymaykett]

Thanks eveyone so far.

Just to recap:

I have an existing ESX 3.0.2 server (only 1) and it is currently connected to a SAN. Some time back, I created a sysprep image that I use as a base for all my new VM's. I use the vmkfstools to import this vmdk file to the new VM. I then create the new VM ans select the imported file. All works great.

What I want to do now is to "copy" the existing sysprep vmdk file from the 3.0.2 server to my new ESX 3.5 server which is connected to my new SAN. I used FASTSCP to connect the the existing 3.0.2 server, and copied it to a Windows 2003 machine. I then used the File uploader in the new VI client and upload the file into the folder for the new VM on the 3.5 server. I can see it all ok via the Datastore browser, FASTSCP, etc, but it doesn't appear in the window when trying to attach the vmdk file to a new or existing VM.

Is the problem possibly related to the fact that I copied the file using FastSCP to Windows, and then up to the new ESX 3.5 server??

I currently don't have access to the enterprise version of converter, only the free one, which I understand limits access to ESX.

Any help appreciated :smileyblush:

[LarsLiljeroth]

Instead of using WinScp i would just do scp from host to host quick and easy.

From source server: scp /path_to_vmdk.vmdk username@servername:/path_to_new_location.vmdk

I used this method before converter. Or you can use the datastore browser in VC to move the file.


// Lars Liljeroth

-

---

*If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[willymaykett]

I think I fixed my problem.

Problem was two fold:

1. Firewall on the ESX was preveting fastscp from connecting properly. Made change to the firewall.

2. Downloaded and installed latest version of fastscp. Copied directly to the new server, worked nicely.

What I did notice, was that it copies it to the windows box first, then up to the server.