How to import an OVA file from VMFS5 datastore into an NFS datastore?
Points of My Scenario:
1. I am admin of vSphere 5.5 and 6.5 environments - both separate
2. The 5.5 environment uses VMFS5 datastores while the 6.5 environment uses NFS3 datastores
3. I exported a 5.5 VM as an OVA file, then attempted to import it in the 6.5/NFS environment.
4. It repeatedly failed to import indicating some incompatibility.
QUESTION: How do I export & import a VM from VMFS5 datastore to an NFS datastore?
You can only Export/Import an OVF from a Workstation from the Web Client.
Have you tried Exporting again, and importing again, the export could be corrupted or not compatible.
Do not use Export OVF/Import OVF, use VMware Converter, and create a V2V
The recommended method is to use VMware Converter.
Have you tried Exporting again, and importing again, the export could be corrupted or not compatible.
Do not use Export OVF/Import OVF, use VMware Converter, and create a V2V
The recommended method is to use VMware Converter.
ASKER
1. Ok, I will use VMware Converter as a last resort - due to very high latency between the v5.5 and v6.5 sites.
2. I have successfully exported/imported OVA from/to v5.5 (using C# client) many times - but source & destination were always VMFS5
3. I hope the OVA is corrupted: I will re-try the export and validate it before sending it for import into v6.5.
2. I have successfully exported/imported OVA from/to v5.5 (using C# client) many times - but source & destination were always VMFS5
3. I hope the OVA is corrupted: I will re-try the export and validate it before sending it for import into v6.5.
It does not make any difference what the datastore is, OVF is completely independant. OVF/OVA is a rubbish method of Export/Import.
VMware Converter can convert to a Workstation disk, and then convert that to ESXi 6.5.
VMware Converter can convert to a Workstation disk, and then convert that to ESXi 6.5.
ASKER
VMware Converter is giving the same error.
did you install VMware Converter on the VM to be converted ?
ASKER
It turns out that my new NFS datastore is not writable. I cannot even create a folder on it using the datastore browser!
(I have tried writing to it from two hosts - unsuccessfully)
Do you have any idea what may be causing this?
(I have tried writing to it from two hosts - unsuccessfully)
Do you have any idea what may be causing this?
Permissions are not setup correctly for the NFS Export.
What is providing the NFS Export?
If you let me know what is providing the NFS Export, may I can provide some guidance on how you set it up.
Maybe no root squash, map as root, maybe IP Address not added to export etc
You state it's 6.5, are there no VMs currently on this NFS3 datastore ?
can you create a new VM ?
What is providing the NFS Export?
If you let me know what is providing the NFS Export, may I can provide some guidance on how you set it up.
Maybe no root squash, map as root, maybe IP Address not added to export etc
You state it's 6.5, are there no VMs currently on this NFS3 datastore ?
can you create a new VM ?
ASKER
Awesome question Andrew. Here are some answers:
1. No VMs are on the NFS storage: NFS was newly set up, using NetApp storage
2. ESXi hosts are included in the export (NetApp-side config)
3. VMs at this site are on local disks (I know, I know: that's a serious felony - please don't call the cops!!!)
1. No VMs are on the NFS storage: NFS was newly set up, using NetApp storage
2. ESXi hosts are included in the export (NetApp-side config)
3. VMs at this site are on local disks (I know, I know: that's a serious felony - please don't call the cops!!!)
ASKER
For the record, point #3 above is just a joke (note to the wider-viewing public audience)...Lol!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many thanks for the pursuit, Andrew. I found the problem: the permissions set on the volume in NetApp were insufficient. Once I fixed the permission, things worked.
Thank you very much for troubleshooting with me.
Thank you very much for troubleshooting with me.
ASKER
Failed - Error caused by file /vmfs/volumes/d039945f-9c2af82b/VM-NAME
Key: haTask-ha-root-pool-vim.ResourcePool.importVApp-112073706