From: Roland <devzero@web.de>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] move virtual disk with snapshots
Date: Mon, 3 Aug 2020 09:45:49 +0200 [thread overview]
Message-ID: <f2d1126e-8629-1821-0dd0-b72ae304c74f@web.de> (raw)
In-Reply-To: <1596438669.ta6wgocjkh.astroid@nora.none>
thank you!
Am 03.08.20 um 09:15 schrieb Fabian Grünbichler:
> On July 31, 2020 8:46 am, Roland wrote:
>> hello,
>>
>> can someone explain, why it's not possible in proxmox to move a VMs
>> virtual disk with snapshots to a different datastore/dir - not even when
>> offline?
> because it only works from one storage type to the same storage type and
> even then requires custom code for each storage type for a rarely used
> operation.
>
>> we need to fix some zfs dataset/dir naming/structure and can't as we
>> would loose all our snapshots when moving VMs around...
> if it's all ZFS, simply zfs send/recv a baseline (can be done while VMs
> are running), then poweroff and send the delta since the baseline, sed
> the storage name inside the config including all snapshots, start the VM
> again. with a bit of careful checking of involved VM configs before
> starting, the whole process can be automated if you want.
>
> similar procedures, possibly with more downtime if no incremental
> sync option exists, apply to other storage types as well.
>
> as always, test with a test VM/setup first, and do backups before just
> in case.
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
prev parent reply other threads:[~2020-08-03 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 6:46 Roland
2020-08-03 7:15 ` Fabian Grünbichler
2020-08-03 7:45 ` Roland [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2d1126e-8629-1821-0dd0-b72ae304c74f@web.de \
--to=devzero@web.de \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.