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
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