Clonezilla.

[Ger van Dijck]

Hi Fedora ,

Thanks to George N. Withe 111 , Bob Marcom, Erik P. Olsen and Klaus 
Peter Schrage.

I did install rpmshere-release with dnf : Runs fine.

I did install clonezilla-2.3.1-1.noarch.rpm with dnf and got following 
message :Nothing provides drbl-partimage >=0.6.7 needed by clonezilla 
-2.3.1-1 noarch.

Nothing provides mkswap-uuid needed by 
clonezilla-2.3.1-1.noarch.

So , What now ?

Kind regards,

Ger van Dijck.

[Chris Murphy]

On Sat, Jul 3, 2021 at 10:18 AM Ger van Dijck  wrote:
> Hi Fedora ,
>
> Thanks to George N. Withe 111 , Bob Marcom, Erik P. Olsen and Klaus
> Peter Schrage.
>
> I did install rpmshere-release with dnf : Runs fine.
>
> I did install clonezilla-2.3.1-1.noarch.rpm with dnf and got following
> message :Nothing provides drbl-partimage >=0.6.7 needed by clonezilla
> -2.3.1-1 noarch.
>              Nothing provides mkswap-uuid needed by
>
> clonezilla-2.3.1-1.noarch.
>
> So , What now ?

Hmm, I'm not finding clonezilla in Fedora repositories, or in RPM Fusion.

And at https://clonezilla.org/downloads.php I'm not finding it
packaged for rhel/centos/fedora.

And 2.7.2 is current at clonezilla.org, so I'm not sure about the
provenance of clonezilla-2.3.1-1.noarch.rpm but I suspect it's a stale
package given the version.

I'm not sure what to recommend without knowing the use case. For
generic use case, sync or backup, I'd use something either rsync or
borg based. I tend to consider block based backups (dd, ddrescue,
dd_rescue) pretty much for scraping, i.e. for emergencies and recovery
operations where you must have an identical copy. That's usually not
what you want for a backup.

Btrfs is compatible with the above options but adds some unique
capabilities of its own:

* snapshot send+receive
Makes an essentially identical copy of a snapshot. There are
advantages (immediately accessible just by mounting the file system;
full checksumming; simpler incrementals management) if you use Btrfs
for the destination file system, but it is possible to use 'btrfs send
-f' to create a file on any file system. But that file must be
"received" on a Btrfs file system to navigate it.

* seed+sprout
Setting the "seed" flag on a Btrfs file system makes it read-only.
Mount it, and 'btrfs device add' a 2nd device, followed by 'btrfs
device remove' the 1st device, and it will kick off replication at a
block group level. The copy is identical in every meaningful way, but
the new destination device can be any size. Of course, it needs to be
at least as large as the data usage on the seed. [1]

[Dave Stevens]

On Sat, 3 Jul 2021 16:04:41 -0600
Chris Murphy  wrote:
> I'm not sure what to recommend without knowing the use case.

Me too. I recently wanted to clone a bootable 32GB usb stick and what
worked easily for me once I found it was

1) dd if=/dev/sdb1 of=MyUSBClone.iso

2) etcher with the iso as input and the new stick (also 32GB) as output

Tada!

Didn't take long, simple and worked beautifully

Dave

[Michael D. Setzer II]

On 3 Jul 2021 at 15:35, Dave Stevens wrote:

Date sent:      	Sat, 3 Jul 2021 15:35:02 -0700
From:           	Dave Stevens 
To:             	[e-mail]
Subject:        	Re: Clonezilla.
Send reply to:  	Community support for Fedora 
users
> On Sat, 3 Jul 2021 16:04:41 -0600
> Chris Murphy  wrote:
> > I'm not sure what to recommend without knowing the use case.
>
> Me too. I recently wanted to clone a bootable 32GB usb stick and what
> worked easily for me once I found it was
>
> dd if=/dev/sdb1 of=MyUSBClone.iso
>
> etcher with the iso as input and the new stick (also 32GB) as output

Can't speak for Clonezilla, but have been 
maintaining the G4L diskimage project on 
sourceforge since 2004. It's primary operation uses 
dd to make and restore images, but also does 
compression.

Not sure how long you process took, but usually 
using bs=1M can make a difference.

Also, the image file created will be the size of the 
original.

Long ago had done a clean install of Fedora Core 3 
on an 80 GB drive. Did an image with compression, 
and it created a 12G image. Then cleared the 
unused space, and redid image and it was just 2.5G.

G4L is basicly a dialog front-end to create the dd 
commands to do images.

An example:
(dd bs=1M 
if=/mnt/local$localpath$localimagename 
2>/dev/null |lzop -d -c - |jetcat-mod -f 5000 -p 
$writesize 2>$progout |dd bs=1M of=$localrest 
2>/dev/null) &

Produces a progress bar screen to show relative 
progress. Also, has options that allow putting 
images onto ftp  or other servers..

Good Luck on things.
> Tada!
>
> Didn't take long, simple and worked beautifully
>
> Dave
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure