From: "Tomas Dalebjörk" <firstname.lastname@example.org> To: LVM general discussion and development <email@example.com> Cc: Zdenek Kabelac <firstname.lastname@example.org> Subject: Re: [linux-lvm] how to convert a disk containing a snapshot to a snapshot lv? Date: Tue, 28 Dec 2021 07:40:45 +0100 [thread overview] Message-ID: <315E5303-D491-4487-BAD4email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Yes, it is an incremental backup based of the cow device no worries about the backup, that works fine, and now by just creating a lv snapshot on it, works too sent you an example before eg # extend vg with new bu disk vgextend xxx newdisk # create lv structure on disk lvcreate -s -L wholedisksize -n s1 xxx/lv newdisk # merge has to be started offline? lvchange -a n xxx/lv # start merge lvconvert -merge -b xxx/s1 # online the lv lvchange -a y xxx/s1 The backup is provisioned through the disk, and makes the data available immediately But, I guess I can skip some steps? Restoring data in just a matter of minutes, regardless of size, or will say, making the data available anywhere in just a few minutes, regardless of size Also working with writes, without destroying the backup are there a way to get a signal when a merge has completed? or do I have to implement a monitor dmsetup xxx or lvs to check when merge has completed Reference Tomas Sent from my iPhone > On 28 Dec 2021, at 06:32, Stuart D Gathman <email@example.com> wrote: > > >> >> If you want to give it a try, just create a snapshot on a specific device >> And change all the blocks on the origin, there you are, you now have a cow >> device containing all data needed. >> How to move this snapshot device to another server, reattach it to an empty >> lv volume as a snapshot. >> lvconvert -s, command requires an argument of an existing snapshot volume >> name. >> But there is no snapshot on the new server, so it can't re-attach the >> volume. >> So what procedures should be invoked to create just the detached references >> in LVM, so that the lvconver -s command can work? > > Just copy the snapshot to another server, by whatever method you would > use to copy the COW and Data volumes (I prefer partclone for supported > filesystems). No need for lvconvert. You are trying WAY WAY too hard. > Are you by any chance trying to create an incremental backup system > based on lvm snapshot COW? If so, say so. > > _______________________________________________ > linux-lvm mailing list > firstname.lastname@example.org > https://listman.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > _______________________________________________ linux-lvm mailing list email@example.com https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2021-12-28 6:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-19 16:43 Tomas Dalebjörk 2021-12-20 14:51 ` Phillip Susi 2021-12-21 13:46 ` Zdenek Kabelac 2021-12-21 14:44 ` Tomas Dalebjörk 2021-12-21 15:30 ` Zdenek Kabelac 2021-12-21 16:12 ` Tomas Dalebjörk 2021-12-22 10:40 ` Zdenek Kabelac 2021-12-28 5:04 ` Stuart D Gathman 2021-12-28 6:40 ` Tomas Dalebjörk [this message] 2021-12-29 13:35 ` Stuart D Gathman 2021-12-21 19:23 ` Phillip Susi
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=315E5303-D491-4487-BAD4firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [linux-lvm] how to convert a disk containing a snapshot to a snapshot lv?' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).