Migration of LVM2-VMs: vzdump --stdout: can't use storage 'local' for backups - wrong content type

alturiak

New Member
Sep 11, 2017
4
0
1
42
Hey there,

I'm trying to migrate LVM2-based VMs from one standalone-host to another. As suggested here, I assumed it would be fairly easy to pipe the VMs through SSH. However, when I try to vzdump on my source host, vzdump seems to look for a local storage that can host backups:

21:45:01 [255] oldserver:~> vzdump 104 --stdout
can't use storage 'local' for backups - wrong content type

I did try variations like vzdump --stdout 1 104 and the like, to no avail.

Source Host is 4.4-18, Destination Host is 5.0-31.

Am I missing something obvious or does vzdump really need a local storage even when piping to stdout?
And, if so, can you provide a viable alternative to migrate the VMs in the given scenario? I simply lack the disk-space for a full backup of the largest VMs on the source host.

Thanks a lot in advance.

Best Regards
Markus
 
One way would be to connect a external storage (eg. nfs) and do the backup onto it. Or create a cluster out of those two servers and migrate the VMs then, after migration you can remove the old node from the cluster.
 
One way would be to connect a external storage (eg. nfs) and do the backup onto it. Or create a cluster out of those two servers and migrate the VMs then, after migration you can remove the old node from the cluster.

Thank you for your response.
Clustering the nodes is - as far as I understand - not possible, since the nodes are not on the same network (therefore, no multicast) and on different versions.

Unfortunately, the only systems I can access are the two hosts, but I should be able to work around the requirement for a storage, it's just more work as I need to migrate the VMs one by one and can't just pipe them all to the new host in one go.
 
You could still enable backups on the local storage for migration, as you are not writing to it.
 
  • Like
Reactions: alturiak