#Copy vm from one host to another install#
#Copy vm from one host to another free#
#Copy vm from one host to another windows#

The steps (after setting up the Crashplan app on each side) would work something like: It can also backup to multiple destinations (such as each 'spoke') Setup the backups to only include the folder where the templates will be stored on the HQ Server.

#Copy vm from one host to another install#

It does dedupe and block level differentials, so you could install it on one local server there at HQ as the 'seeder', and on each spoke server (in a VM I guess) as a 'receiver'.

#Copy vm from one host to another free#

It won't help with your initial seeding, but I wonder if using something like Crashplan's free product would help you with your templates. Here's a somewhat interesting idea for you.

Bonus: Learn something new, justify playing ServerFault at work.

Disadvantage: Awarding a bounty costs rep.

Advantage: Resumable, speed-throttled background transfer that only moves ~40 GiB of data that exists.

Better option suggested on Server Fault.

Disadvantage: Moving ~60 GiB of data that doesn't really exist.

Advantage: Speed-throttled and potentially resumable.

Copy the file between ESXi hosts via SCP.

Double Secret Probation Bonus: PowerShell Remoting makes it possible to do this in one single command.

Advantage: Resumable, background transfer.

#Copy vm from one host to another windows#

Copy the file between Windows guests using BITS.

Disadvantage: Everything else - not resumable, not background/speed-throttled, interface SUCKS.

Advantage: Moving only ~40 GiB, not ~100 GiB.

Copy the files between datastores through the vSphere client.

(Ideally one that has me only moving the 40 GiB of actual data, and in a resumable, 'background' or speed-throttled method.) The way I see it, I have three possible approaches, though I dearly hope I'm missing a better one that someone here can point me at. I am under the constraints that I have approximately 5 days to do so, and cannot interfere (noticeably) with 'normal network traffic.' How should I copy this 40 GiB of thin-provisioned data (that occupies 100 GiB of filesystem space) between my sites? As files on NTFS (or a Linux FS), they occupy ~100 GiB. They are stored in an NFS volume, that is a vSphere datastore, attached to the home office datacenter object within vSphere.Д®ach remote site has a corresponding vSphere datacenter object, containing a datastore object that's connected to the locally-attached storage on the ESXi host server physically located at the remote site.ДЄs these VM templates exist on the NFS volume, they occupy ~ 40 GiB (thin-provisioning). All traffic originating at any remote site routes back to the home office over a 'MPLS network' (which is really just a T1 connecting the remote site to the home office).ДЄt the home office, on the SAN, we have a number of VM templates that I have created to deploy VMs from. My current environment for $corp_overlords$ is set up in a hub-and-spoke model with a technologically well-endowed home office hub (SAN, bladecenter/bladesystem ESXi cluster, fiber internet connection, etc.) connected to a number of remote site spokes that are not so well off, and typically contain single ESXi host server and connect to the home office hub via a T1.