惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Help Net Security
腾讯CDC
爱范儿
爱范儿
Google DeepMind News
Google DeepMind News
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
Engineering at Meta
Engineering at Meta
GbyAI
GbyAI
量子位
F
Fortinet All Blogs
G
Google Developers Blog
T
The Blog of Author Tim Ferriss
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
T
Tailwind CSS Blog
J
Java Code Geeks
S
SegmentFault 最新的问题
D
Docker
博客园 - 司徒正美
The GitHub Blog
The GitHub Blog
Jina AI
Jina AI
M
MIT News - Artificial intelligence
博客园 - 【当耐特】

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Copy a vm from one proxmox server to another over the int...
invalid@exam · 2026-06-06 · via Proxmox Support Forum

I thought this would be easy but its turning into a complicated mess.

What I would like to do is simply copy a vm from one proxmox server to another. Yet I do not seem to be able to do that in any simple easy way using the GUI.

The setup I’m trying to do this with:

I have a proxmox server running on a dedicated server I pay for with an IP address of say 12.13.14.15 this has several vm machines running on it.

However, it’s on an older server and costs more than the new server I’ve found hosted by a different company so I’ve brought this second server of a similar setup but with the IP address of say 15.14.13.12

The problem I seem to be having is that one of the virtual machines on the old server has 12TB of data on it and both servers only have 16TB of storage available to them.

In trying to copy from one server to another I’ve found that there is no way to just make a direct connection to both servers that allows me to COPY the vm with 12TB of data on it to the new server.

Either it is a migration which is not an option as I still want the original server to have a copy of the data on it till I’ve successful got the new server working or any backup option I could try wants to make a copy of the 12TB on the original server or elsewhere and then copy that backup across to the new server which is also not an option as I don’t have the space for it.

I just want to be able to, for want of a better explanation, sftp into the new server from the old and give it access to the new servers storage area and click on a COPY button on the old server that allows me to select the new server as a new storage option to copy the vm to and it transfers it over the internet to the new server.

Instead all I’ve found online to do something like this with was proxmox backup server which seems to basically require me to have a whole other third server with 16TB of storage free, which I do not have, to back up the old server to and then transfer that to the new server.

The other option I found was to use a cluster which for the briefest of moments I thought would work and did something close to what I wanted in terms of connecting the two servers together but it only gave me the option to migrate which is more of a cut and paste process and not a viable option as I need it to copy the vm. I tried selecting the clone option but it wouldn’t allow me to select the storage area of the new server when I did that.

And then I nearly lost access to the data on the old server when I tried to remove the new server from the cluster as then the old server wouldn’t do anything without the new server being connected and the only way I could get it working again was to use ‘pvecm expected 1’.

This is what’s made me come here seeking wisdom and to ask if there is a way I can do what want in a simple, straight forward way?

An example of which would be like how proxmox can connect to an ESXI server and import a copy of its vm’s from it to a proxmox server. When I changed over from ESXI to proxmox making a copy of the ESXI vm’s on to the proxmox server was simple, straight forward and easy. I thought this would be even easier to do when going from proxmox to proxmox but that doesn’t seem to be the case.

Have I missed something or is what I want to do just not possible with the limitation of storage space and server setup that I have?

UdoB

Distinguished Member

The other option I found was to use a cluster

No, that's definitely the wrong tool for your task.

If you want to use a supported method with a GUI you may look at https://pdm.proxmox.com/docs/ - you can connect multiple PVE installations with this.

As I am not using that one, I can only guess: PDM should be able to clone/copy a VM from one site to the other. And I am not sure if that would require an interim full copy of the 12 TB..., sorry. Go and test it with a small test-VM.

Again: this is just my first thought, not tested!

(Personally I would go for ssh/sshfs or similar, but that requires some detailed knowledge regarding the underlying file systems / block devices etc.)

How is the storage set up? If it is zfs at both sides you should be able to do a simple zfs send > zfs receive to copy from one machine to the other. If you have different storage types at both ends it could be a little harder, and at that point it would probably be easier to backup from one and restore to the other. That would require that you fix the problem of not having backups, but you should be fixing that anyway as soon as you can.

Another way is to just pipe a dd read call through tar through ssh from one to the other end where it untar's and dd writes all in a single call, this will minimize bandwidth and also achieve what you're after. I'm pretty sure I had an old backup script that did this 25 odd years ago.

Echoing UdoB, setup a PDM VM and connect both PVE servers to it. Under the Remotes in the left pane, click on source server and in the middle pane you should see a little paper-airplane icon ( the icons in order are power, start, airplane, up-right arrow )

The paper-airplane icon is Migrate. You have the option to delete the source or not, in your case I would not delete ( uncheck it )

I would change the target VMID to the current ID + 1000. NOTE that the underlying storage must be the same, lvm-thin to lvm-thin or ZFS to ZFS.

Thanks for all the replies.

Finally got around to installing Proxmox Datacenter Manager on the new server and trying out the migrate option while un-checking the delete check box.

This did indeed do what I wanted it to do with two little niggling issues along the way.

The first was when adding a new remote and the certificate used for validation. I used the right fingerprint for the remote server but when it got to the endpoint screen it kept giving me a connection error. Turns out all I needed to do was delete one of the two entries as it seemed to make a up a second fingerprint or something itself automatically which causes the connection to fail.

Getting over that issue I then found the paper airplane Icon to migrate a vm over to the new server and unchecked the option to delete the vm on the old server as part of the migration process.

This, I was pleased to find, worked like I wanted it to with just one other small niggling problem which was when the vm wasn’t deleted on the old server it then gained a paper airplane symbol on it and said it was locked and migrated so it could not be started.

Quick google search helped me understand how to unlock it again using this command in the nodes gui shell on the old server that had the now locked vm:

qm unlock 199

This unlocks whatever vm ID is put at the end, which for me was 199. Which was surprisingly straightforward to do and worked. This was a relief as the moment the use of shell was mentioned my stomach started churning and I feared I was going to be spending the next couple of hours trying to unlock it using a thousand shell commands. So that was good.

So once again, thanks for the help everyone. I just wish this could all be done in the native GUI of Proxmox itself rather than needing to make a separate VM to run the datacenter manager.

Last edited: