We found ovftool fails to deploy a vApp instance, within which 12VMs are to be created, from an ova file, while it succeeds if the ova file contains a slimmer version ovf file (VMs' no is decreased to 8). The host where ovftool runs is in the same LAN with VCenter server so network is probably not a problem. Besides, it also succeeds to deploy the package.ova file using VSphere Client GUI.

ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

The progress bar indicating complete percentage never shows up for the 12VM-version's deployment. The verbose log shows that the upload never starts. Has anybody encountered this issue? And you'll be appreciated if you can give us a hand. And we are willing to provide our ova file to troubleshooting this issue.

Background

We generate an OVA file which contains multiple VMs. Every VM specified in the ovf file refers to either a Linux vmdk or a Win vmdk within the OVA file. With two vmdk files contained in the ova file, the file size is almost 3G. We used the above command to deploy an vApp instance, but it always fail.

The following are what we have tried.

- The machine to run ovftool always keeps in the same LAN as VCenter server. This ensures network low latency.

- We tried ovftool both with its linux's version and windows's version. Deploying the ova containing 12VMs, always fail; deploying the slimmer version with 8VMs, it works;

- The difference between 12VM and 8VM ovafiles are very simple: both has two vmdk files, file-size are almost the same(~3G). It's just the latter ovf file choose to generate small number of homogenous VMs.

The verbose logs are attached below.

ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin

--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

ŠŠŠŠŠŠŠŠ.

-->

Opening VI target:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:15:55.791Z [7FCDED7D2740 verbose 'Default'] Hostsystem used

as deploy target: vim.HostSystem:host-16

Deploying to VI:

vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation

2014-01-17T08:16:24.172Z [7FCDED7D2740 verbose 'Default'] Using file size

as progress measure

2014-01-17T08:16:24.189Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.190Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.191Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.192Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.195Z [7FCDE4FB0700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE416F700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE412E700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.197Z [7FCDE40ED700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.198Z [7FCDE40AC700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDE406B700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:24.199Z [7FCDBFFFF700 verbose 'Default'] CURL: header

data removed

2014-01-17T08:16:42.512Z [7FCDBFF7D700 verbose

'HttpConnectionPool-000001'] [RemoveConnection] Connection removed; cnx:

<SSL(<io_obj p:0x00007fcde0014b00, h:-1, <TCP '0.0.0.0:0'>, <TCP

'10.146.25.129:443'>>)>; pooled: 0

work@boxbuilder:~$ lsof -i TCP

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

ovftool.b 31731 work 7u IPv4 574157 0t0 TCP

10.146.25.131:33750->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 9u IPv4 575678 0t0 TCP

10.146.25.131:33752->10.146.25.129:https (ESTABLISHED)

ovftool.b 31731 work 10u IPv4 574954 0t0 TCP

10.146.25.131:57555->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 11u IPv4 574159 0t0 TCP

10.146.25.131:57556->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 12u IPv4 576636 0t0 TCP

10.146.25.131:57557->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 13u IPv4 574955 0t0 TCP

10.146.25.131:57558->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 14u IPv4 574160 0t0 TCP

10.146.25.131:57559->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 15u IPv4 576637 0t0 TCP

10.146.25.131:57560->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

ovftool.b 31731 work 16u IPv4 574956 0t0 TCP

10.146.25.131:57561->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)

Hi,

Thanks in advance for any help that can be given with this, Have been looking at rolling out .ovf VM's as part of a automation project. What we are trying to do is roll out two servers to a specific datacentre, cluster, host and Resource pool.

Script below is what we are using, it works perfectly to roll out a VM but this will only be in the root of the Datacentre.

C:\Program Files\VMware\VMware OVF Tool>ovftool -tt=vi -st=ovf --lax -n=Test --datastore=VMWARE --network="VLAN" --powerOn "Full UNC path of .ovf" "vi://Domain%5cUSER:Password@vsphere/DATACENTRE/host/Development/FULL HOST NAME/"

But when I add in the switch for Resource and the required Resource pool as seen below:

C:\Program Files\VMware\VMware OVF Tool>ovftool -tt=vi -st=ovf --lax -n=Test --datastore=VMWARE --network="VLAN" --powerOn "Full UNC path of .ovf" "vi://Domain%5cUSER:Password@vsphere/DATACENTRE/host/Development/FULL HOST NAME/Resources/Dev"

It give the following error:

Opening OVF source: Full UNC path of .ovf.ovf

Opening VI target: "vi://Domain%5cUSER:Password@vsphere/DATACENTRE/host/Development/FULL HOST NAME/Resources/Dev"

Error: No target host found in cluster that supports the chosen network/datastore/virtual hardware combination.

Possible completions:

ESXHOST 01

ESXHOST 02

ESXHOST 03

using OVFtool 3.5 with VMWare 5.0

See attached image for layout of vCentre

any help would be much appreciated.

Hi all ...I'm not sure if this is the correct place to post this question and I'm hoping someone could plase advise me as to how to do this.

I created a nested ESXi 5.5b VM.The VM is not connected to a vCenter as yet and it may or may not be connected based on whether or not I want to join it to a vCenter or not.

I then set the vAPP options to enable for the VM settings.

I then set various advanced properties for the VM.

I now have a Python script (I named it test2.py) which collects the properties from an OVA during it's deployment , the script then uses the info collected from the properties and applies them in commands at the cli.

I use this info to alter things like the Hostname, DNS, IP and other info inside the VM.

This all works successfully.

I would like to have the script start/run-once at boot time after the vAPP is deployed.

How do I do this ? and where to I place the script ? so that is does not get deleted or destroyed when the ova gets created and then deployed.

Any help would be greatly appreciated.

Kind regards

Den

Hi all,

I have a "little" question. I have installed a new vCenter 5.5 in my farm and I would like to migrate all clusters/hosts to it. In my old vcenter there are a lot of vApps. How can migrate all without problems?

Thank you very much.

Matrix

Hi,

I am trying to deploy an. ova file using ovftool with the following command :

C:\Program Files (x86)\VMware\VMware OVF Tool>ovftool -ds=<datastore> --net:"VM Network
"=standard_trunk --net:"VM Network 2"=standard_trunk -n=g1 <<MYOVA.ova>> vi://username:password@<IPaddr>
Opening OVA source: vwlc.ova
The manifest validates
Opening VI target: vi://root@10.50.16.36:443/
Deploying to VI: vi://root@10.50.16.36:443/
Progress: 59%

Removing temporary objects and files

Transfer Failed

Error: Execution aborted

Error: Operation was canceled

Completed with errors

And it aborts with the above error.

Can anyone help me out.

I am facing an issue. I have an ova file of size 362 MB. I am using OVFTOOL to convert ova to vmx file. I get the below error during conversion,

Also tried with option --chunkSize=200mb, but with no luck. Same error as below.

Transfer Failed

Error: System error: (Unknown exception)

Completed with errors.

In Vmware workstation 8, i get the below error when i am trying to import the OVA file with the below steps,

a). From the File menu on the VMware Workstation 8 menu bar, select Open.

b).  Browse to the .ovf or .ova file and click Open and Import.

I get the below error.  Anyone who could help me with this?

Hello, I have been using VMWare for some time now, but new to this conversion tool and vCloud.


My current dilemma is getting a VMWare player VMX converted so I can upload it to vCloud. Seemed straightforward, but every time I convert it and then try to upload it to vCloud, I get 


a virtual system in the ovf file being uploaded requires unrecognized virtual hardware version


I have other platforms to move from as well- I hope this forum will get me where I need to be with those instances, but this error doesn't show when I search the forum. I assume that either I need a switch in there when running ovftool, or you simply can't convert a Player file into an OVF. I am testing the stand-alone convertor, stepping the output file down to VMX-9 to see if this will help.


...I notice there are a lot of questions about getting from one platform and format to another.


Is there no chart somewhere with all of this info in it? That is, FROM platform on X axis, TO platform on Y axis, Yes/no/details/link to more info/etc in cells as appropriate? I was not able to find one.

     Seems like we could use that... I have a very light team running the vCloud and they just aren't there for me with the conversion work I need to do- and that work is essentially all I need to do on the maintenance side of the fence. Plowing through all of the manuals and becoming an expert in what I need to do is also not an option...

Hi fellows,

                       I had deployed a virtual ESXi host on a physical ESXi and then I created an OVA file of that virtual host and then was trying to deploy the OVA after changing the IP, subnet mask and gateway properties of the OVA file. But when i used the probe mode to have a look at the class ID and other properties, I found them to be missing.

C:\Users\abhinav.srivastava>ovftool test1.ovf

OVF version:   1.0

VirtualApp:    false

Name:          vhost1

Download Size:  283.32 MB

Deployment Sizes:

  Flat disks:   25.00 GB

  Sparse disks: 325.44 MB

Networks:

  Name:        VM Network

  Description: The VM Network network

Virtual Machines:

  Name:               vhost1

  Operating System:   otherlinux64guest

  Virtual Hardware:

    Families:         vmx-08

    Number of CPUs:   2

    Cores per socket: 1

    Memory:           2.18 GB

    Disks:

      Index:          0

      Instance ID:    8

      Capacity:       25.00 GB

      Disk Types:     SCSI-lsilogic

    NICs:

      Adapter Type:   E1000

      Connection:     VM Network

So right now I am not able to change the OVA properties and deploy the virtual host. I need to do this as I want this step automated. Does anybody know why am I not able to see the properties of the OVA file. Am I going wrong somewhere. Kindly help!!

Thanks,

Abhinav

Greetings

We have developed a perl script in Linux that uses ovftools to deploy our VMs onto a vCenter installation.  We recently tried this on a new customers lab and ran into a weird error not seen before.  The issue is when ovftool is called to deploy the VM it starts fine and a see the VM created in vCenter but after a period of time I have seen a couple different errors:


One time the error was:

mtc@orchestrator-vm-pristine:~$ ovftool --noSSLVerify --net:'data=data' --net:'ipc=ipc' --net:'mgmt=mgmt' --datastore='datastore1 (4)' --name='vmme01-mgmt-1' --machineOutput "/usr/local/epc/data/working/b98d9334-c966-4ff8-a2d3-ab8bcff6a3d8/epc-os-mgmt-vm/epc-os-mgmt-vm.ovf" vi://Administrator%40vSphere.local:WaffleMan5000%21@10.30.0.130/MTS-MME-LAB/host/side-1/10.30.0.79
MANIFEST
+ <ManifestValidate valid="true"/>
PROGRESS
ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.abort</Type>
+ <LocalizedMsg>
+ Execution aborted
+ </LocalizedMsg>
+ </Error>
+ </Errors>
/usr/bin/ovftool: line 23: 2288 Segmentation fault (core dumped) "$OVFTOOL_BIN" "$@"
mtc@orchestrator-vm-pristine:~$ ovftool -v
VMware ovftool 3.5.0 (build-1274719)

After trying a couple different times I started seeing a different error, <Type> Lost connection </Type>.  This all works fine in other installations so there is something unique to this install.  Is there a document that describes the packet flow and setup for ovftools pushing the ovf/ova's out to the host?  Were are logs stored to be able to track down the issue?


 


Thanks


Eric Wolf


 

Hi all.  I'm trying to archive some no-longer-used VMs with ovftool, and I've managed to save half of them.  The ovftool output looks like:

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_250m /Volumes/Archive/VSH_250m.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_250m

Opening OVA target: /Volumes/Archive/VSH_250m.ova

Writing OVA package: /Volumes/Archive/VSH_250m.ova

Transfer Completed                    

Completed successfully


 


The other half of the machines fail with the mysterious vim.fault.FileNotFound without saying which file isn't found.  I've looked at the settings for both successful and unsuccessful VMs and cannot figure out what the difference is:


 

wpeters$ ovftool vi://root@zeus/Riverbed/VSH_markt /Volumes/Archive/VSH_markt.ova

Enter login information for source vi://zeus/

Username: root

Password: *********

Opening VI source: vi://root@zeus:443/Riverbed/VSH_markt

Error: vim.fault.FileNotFound

Completed with errors

Environment:

- ovftool 2.0.1 (build-260188)

-  ESXi 4.0.0 (244038)

-  ESXi 4.1.0 (260247)

I'm creating an OVA using ovftool from an appliance that's turned off.  It's installed on the ESX 4.1 machine.

When I create the appliance using a self-signed certificate, it deploys correctly on ESX 4.0.

However, the same appliance fails to deploy on the ESX 4.1 device.

I get the following error at 99%:

Failed to deploy OVF package: The request was aborted: The request was canceled.

Any ideas?

There is unfortunately a bug in OVF Tool 3.0.1 on Mac that causes OVF Tool not to work if the current directory is not the same as the installation directory! For example, if you have made a symbolic link to OVF Tool or have OVF Tool in the path, you will see the following error:

Running OVF Tool 3.0.1 on 32 bit CentOS 6 Linux 2.6.32-279.11.1.el6.i686 (download from VMWare site md5sum was checked ok)

Tool starts up fine and is in the process of exporting a VM from one ESXi 4.1 host to another ESXi 4.1 host . 

Tool then crashes with /usr/bin/ovftool: line 23:  7629 Segmentation fault      (core dumped) "$OVFTOOL_BIN" "$@"

HI,

I'm trying to create an OVF using ovftool 3.0.1. When I issue the ovftool command from the command line I get:

Error: cURL error: Couldn't connect to server
Completed with errors

I used the following command:

/usr/bin/ovftool vi://username:password@XX.XX.XX.XX/datacenter/vm/folder/vmname /destination

I can issue the command as above without the vmname to see if I can access Vsphere and to make sure I have a valid source locator.  The command is successful and returns a list of VMs I can use. When I add the VM name to the source locator path, I get the above error. The VM is pysically about 14GB in size (that is the space alloacted).

I can use the same command to another Vpshere server and I'm successful in creating the OVF. Which leads me to think that it might be a configuration issue with this Vsphere server?

What sorts of issues can lead to the above error?

Thanks,

Fernando

I am trying to deploy OVAs using ovftool 3.0.1 to an ESXi 5.1 host. When deploying VCSA 5.1.0b it works as expected with the following command:

I have confirmed that I can deploy the OVA manually. I have also confirmed the MD5SUM and tried the --disableVerification flag on ovftool. Any idea what I am missing?

Hi,

I am getting below error while depoying a OVF template. Please suggest.

Failed to Deploy:Unable to access file: server1.vmdk.
The process cannot access the file "fullpath of vmdkfile\server1.vmdk' because it is being used by another process.

All,

First of all, apologies if this is an inappropriate forum. I do not have a support contact for this issue. We are VMware customers, however our licenses are purchased through an academic reseller. Our concern is that this bug has crept into recent releases and perhaps gone unnoticed in QA. It's serious enough for us to consider moving to other hypervisor products.

I believe there may be a serious bug in OVFtool's disk read code. We observe that VMs are created OK after upload or import, but disk contents are zero-filled. No error conditions are reported at any time. It is only clear that the bug has been exercised, when an uploaded or imported VM fails to boot.

We have several research VMs with multiple LANs, which run FreeBSD 8.2 in VMware Fusion 5.0.2, MacOS X 10.8.2 Mountain Lion. I was also able to reproduce the bug with a fresh installation of vSphere ESXi 5.1 and ovftool 3.0.1. V

Using the separately packaged ovftool, I can export the VMs inside Fusion, by giving fully qualified paths to their VMX files. The bug appears to be in VMDK read. I exercised it in two use cases, Fusion OVA import and ESXi OVA upload, as follows:

1. If I import an affected OVA into Fusion from the GUI, Fusion will invoke its own copy of ovftool 3.0.1 to perform the import. VMs are created with a sane VMX file. VMDKs are created. However their contents are zero-filled, and the VMDK contents in the OVA have been ignored.
2. If I upload an affected OVA to ESXi, using ovftool and a vi:// target URL on the command line, the same bug is observed with ESXi. Again, the VMX is sane - we inspected this by SSHing into ESXi and manually reviewing the VMX on the VMFS data store with vi. The VMDK contents are zeroed on the VMFS datastore, and the VMDK contents in the OVA have been ignored.

ovftool seems, in some cases, to ignore the contents of the packaged VMDK files in OVAs, and those associated with VMX files from VMware products.

To date I have only been able to reproduce the issue with FreeBSD guests. The bug does not appear in all exported OVAs, however affected VM and OVA combinations will consistently demonstrate it.

• We first noticed this problem in October 2012, and have not been in a position to exercise it thoroughly until now.

• I can make an OVA available which demonstrates the issue. Please contact me privately to arrange. The files are typically 2GB in size.

Other observations:

• There is no problem with OVA generation. I have inspected the OVAs manually using tar, extracted the embedded VMDKs inside, converted them back to 2GB sparse format using vmware-vdiskmanager (or vmkfstools under ESXi), and loaded them into ESXi and Fusion respectively.

• Since ovftool was introduced, VMDKs must be uploaded manually using SFTP to avoid triggering the bug. The functionality in the vmware-vdiskmanager command which allows direct upload to ESXi servers has been removed.

• Casual inspection with DTrace under OS X reveals that ovftool seems to be reading the full OVA file contents. We initially thought there may been a problem with VMDK upload, however other guests have not been affected.

• The serialized format VMDK contents in the OVA are consistent with the original VMDKs. We verified this in one case with MD5 checksums. This requires denying all writes during the test.
• We also reproduced this bug with out-of-box, unmodified FreeBSD installations, as our research VMs use ZFS in GPT partition containers.

• We also noticed that Fusion's private copy of ovftool will break if ESXi specific options are specified in $HOME/.ovftool - although this is a separate issue from the main bug.
• No source code is supplied for ovftool, so users are not able to fix this issue themselves.

Workarounds:

• We load the OVA into Oracle VirtualBox, and re-export the OVA from there.
• This is undesirable for many reasons, the main one being that it loses all the network binding information, which is critical to our work.

thanks,

Bruce

Is it possible to include the advanced CPU settings for a VM when you build an OVF/OVA with ovftool?

My VM must have VT-x enabled (nested virtualization) and the default setting seem to be disabled.

Though --allowExtraConfig would do the trick but it doesn't help.

Any help would be much appreciated!

Hi VMWare experts,

I am having problem with automation script because the string passed in the ovftool command uses credential vsphere.local\userXYZ instead of just userXYZ

It appears that the backsplash in the 'vsphere.local\user' cause the command line to be misinterpreted, so the automation script that calls ovftool to deploy VMs kept failing.  It erred with "cURL error of ‘couldn’t resolve hostname" even though there is nothing wrong with any hosts or hostname resolution on the network.

On a Win-based vCenter I was able to reconfigure it so that instead of requiring login user format of 'vsphere.local\userXYZ', it will now accept user = 'userXYZ'. 

With that change, ovftool.exe command string is now progress correctly and VMs are deployed. 

I could reconfigure Window-based vCenter to not use just user = userXYZ (instead of vsphere.local\account), but I could not figure out how to get vCSA to stop requiring the format of vsphere.local\userXYZ.

The string segment in the long ovftool.exe command line looked like this …

This works:

"vi://userXYZ:password@tm-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi112.cisco.com"

This does not work:

"vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com"

Is there anyway to configure vCenter Virtual Appliance to use log in format of user = userXYZ instead of user = vsphere.local\userXYZ?   Or is there some way of reformatting the string so that OS can interpret it correctly even with backsplash '\' is used in the string?

Thank you

Charles

The complete ovftool.exe command is shown below:

"C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --acceptAllEulas --skipManifestCheck --diskMode=thin --name=linsys2-vm1 --deploymentOption=vm_typeA --datastore=EMC-LUN1 --net:"Network Adapter 1"="VLAN 410 - 172.27.14.0/24" --net:"Network Adapter 2"="VLAN 410 - 172.27.14.0/24" --vmFolder=   --prop:cisco_hostname.Proj=linsys2-vm1 --prop:cisco_ip_0.Proj=172.27.14.135 --prop:cisco_dnsDomain.Proj=cisco.com --prop:cisco_netmask_0.Proj=255.255.255.0 --prop:cisco_gateway_0.Proj=172.27.14.1 --prop:cisco_dns1_0.Proj=172.27.200.199 --prop:cisco_dns2_0.Proj=173.36.131.10 --prop:cisco_language.Proj=English v:\ova\projectX_1.0.0.ova "vi://vsphere.local\userXYZ:password@lin-vcenter55/DC2-SJ/host/Topology/csg-sj-esxi111.cisco.com"

Opening OVA source: v:\ova\projectX_1.0.0.ova

The manifest does not validate

Error: cURL error: Couldn't resolve host name

Completed with errors

Installation Done!

Hi,

I have about a dozen OVF's I'm importing into ESXi 5.5 via the Linux ovftool client. The VM's range from 5gb to 30gb and include VMDK files. I am still improrting the first one and it is taking a crazy long time. The CPU and Memory usage stays under 1% on the client, and getting up to 5% has taken me the better part of an hour. Network speeds don't seem to be an issue, I'm wired and can SCP files from the same source and destination at 30MB/s. Is there something I'm missing? please help