Replies: 3 comments 2 replies
-
Depending on whether the partitions are mounted and only contain files, I either use |
Beta Was this translation helpful? Give feedback.
0 replies
-
Nice idea with 'dd'. I wonder if there is a way to copy over a partition
image file just the changed blocks, so that I could use snapshots for the
disk image with a minimal overhead.
[update] It looks like I can 'dd' the partition's device to a temporary file and
then 'rsync --inplace' to the destination image :)
[update] Sorry for the conversation with myself, but it looks like rsync --inplace
will still rewrite full file:
$ rsync -av --inplace /var/tmp/uefi-backup.img /archive/replica/boot/
$ zfs list -t snapshot archive/replica/boot
NAME USED AVAIL REFER MOUNTPOINT
***@***.*** 107M - 107M -
***@***.*** 127M - 128M -
Back to the drawing table or just screw this and accept wasted 100M space.
Is there a tool which will reliably rewrite just changed bytes on the
destination?
|
Beta Was this translation helpful? Give feedback.
2 replies
-
It looks like I can 'dd' the partition's device to a temporary file and
then 'rsync --inplace' to the destination image :)
On Wed, Aug 31, 2022 at 11:29 AM Ivan Volosyuk ***@***.***>
wrote:
… Nice idea with 'dd'. I wonder if there is a way to copy over a partition
image file just the changed blocks, so that I could use snapshots for the
disk image with a minimal overhead.
On Tue, Aug 30, 2022 at 10:01 PM Markus Ueberall ***@***.***>
wrote:
> Depending on whether the partitions are mounted and only contain files, I
> either use tar or dd along with gpg to encrypt and archive their
> contents as far as zfs send is not an option. IMHO, being able to
> restore the contents of these partitions using a recent backup in case of
> need is easier/faster than to recreate them. (Also, the resulting archives
> don't need much space at all.)
>
> —
> Reply to this email directly, view it on GitHub
> <#13786 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABXQ6HJ3IFKHRZH47YFZWFDV3XZXZANCNFSM57B2CCBQ>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a working Ubuntu 22.04 installation on a RAIDed encrypted ZFS file system. The procedure I followed can be downloaded from:
https://www.mediafire.com/file/2w8mdb96tbzslub/Ubuntu_22.04_Root_on_ZFS_Encryption.odt/file
This procedure is a customized version of rlaager's at:
https://openzfs.github.io/openzfs-docs/Getting%20Started/Ubuntu/Ubuntu%2022.04%20Root%20on%20ZFS.html
Before I migrate this installation to Pop!_OS I want to be able to easily restore the system to what it was before the Pop!_OS installation attempt. This is necessary because my prior experience is that this installation is a risky thing to do, and it can make the computer unbootable. The Ubuntu installation procedure requires a lot of time, and effort, that I seek to protect.
The snapshot procedure I am about to do is:
My concern now is about how to backup the UEFI, and BIOS, partitions. What is the best way to do that? How necessary is it to back up these two parttiions to protect against damage a failed Pop!_OS installation attempt might do?
Beta Was this translation helpful? Give feedback.
All reactions