[opensuse] Latest Drive Image Recommendations (other than dd)
All, Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions). What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at. (If I was just doing a clean install, I'd just use a new drive :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-01-14 at 01:35 -0600, David C. Rankin wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
(If I was just doing a clean install, I'd just use a new drive :)
Plain dd :-) Actually, I'd use dd_rescue, or rather, dd_rhelp. If you want something fancier, then clonezilla, which uses its own boot image. But unless you need or wish something specific, use dd_rhelp, which is just a script to call dd that works arounds errors With dd, you can mount the image and see the files directly. Clonezilla can use compression, and will skip unused sectors, so that it uses less space. It might be faster. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpbIAwACgkQtTMYHG2NR9XgCwCfbXlpnWqE9iOmVBXEfwIIkNIq 5uEAnA5YfMbexmubNVzW2UzjTPdNZRNl =E2Pp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
(If I was just doing a clean install, I'd just use a new drive :)
Plain dd :-)
Actually, I'd use dd_rescue, or rather, dd_rhelp. If you use this method, don't forget to regenerate uuid's for the cloned
On 14/01/2018 11:16, Carlos E. R. wrote: partitions otherwise you might have mounting problems if they're on the same box. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-01-14 at 12:19 +0200, Dave Plater wrote:
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
(If I was just doing a clean install, I'd just use a new drive :)
Plain dd :-)
Actually, I'd use dd_rescue, or rather, dd_rhelp. If you use this method, don't forget to regenerate uuid's for the cloned
On 14/01/2018 11:16, Carlos E. R. wrote: partitions otherwise you might have mounting problems if they're on the same box.
Of course, but not something one does for a backup. Do the copy, remove the disk :-) - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpbl8MACgkQtTMYHG2NR9VYuQCeN5vWxgwoC2/g7UIokB1z9B9S 6qUAn2vtAKKPqSNvIAGZosGrSdc9YHDW =pDiQ -----END PGP SIGNATURE-----
David C. Rankin wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
You probably don't need an image, but just a filesystem copy. 'rsync' or 'tar' is the answer. -- Per Jessen, Zürich (0.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-01-14 at 10:29 +0100, Per Jessen wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
You probably don't need an image, but just a filesystem copy. 'rsync' or 'tar' is the answer.
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-) If the files backup is to hard disk, rsync is more advantageous than tar; easier to recover a single file, a redo only copies the modifications, more resilient to errors, can do CRC checksums... A dd runs faster than a full rsync - for each file the directory table and an inode have to be written on another place of the disk, so head movements. A disk image like dd writes many contiguous tracks. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpbKnMACgkQtTMYHG2NR9XrYgCeKT0cGAkuUlzD28Yn/PqnOawN 2rMAn1C/3nbDeJT1gwn8kREbVehGMDpV =emuk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On Sunday, 2018-01-14 at 10:29 +0100, Per Jessen wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
You probably don't need an image, but just a filesystem copy. 'rsync' or 'tar' is the answer.
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
If the files backup is to hard disk, rsync is more advantageous than tar; easier to recover a single file, a redo only copies the modifications, more resilient to errors, can do CRC checksums...
A dd runs faster than a full rsync - for each file the directory table and an inode have to be written on another place of the disk, so head movements. A disk image like dd writes many contiguous tracks.
It will depend on the situation. A 'dd' will copy unused space needlessly. -- Per Jessen, Zürich (0.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-01-14 at 11:15 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On Sunday, 2018-01-14 at 10:29 +0100, Per Jessen wrote:
look at.
You probably don't need an image, but just a filesystem copy. 'rsync' or 'tar' is the answer.
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
If the files backup is to hard disk, rsync is more advantageous than tar; easier to recover a single file, a redo only copies the modifications, more resilient to errors, can do CRC checksums...
A dd runs faster than a full rsync - for each file the directory table and an inode have to be written on another place of the disk, so head movements. A disk image like dd writes many contiguous tracks.
It will depend on the situation. A 'dd' will copy unused space needlessly.
True (but not clonezilla). On my systems, dd is typically faster, I did the test :-) - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpbmFwACgkQtTMYHG2NR9WHvQCfeBw41d5tr7pzgD8RC0KynNr9 bUAAoIWpRyUCaiNb9IY032bDVQYtQ+aC =SMqi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14/01/18 10:01, Carlos E. R. wrote:
On Sunday, 2018-01-14 at 10:29 +0100, Per Jessen wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
You probably don't need an image, but just a filesystem copy. 'rsync' or 'tar' is the answer.
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
Unless your disk sizes are different ...
If the files backup is to hard disk, rsync is more advantageous than tar; easier to recover a single file, a redo only copies the modifications, more resilient to errors, can do CRC checksums...
And is more complicated ... plus once rsync starts having to handle hard links things get messy and run-times can explode :-(
A dd runs faster than a full rsync - for each file the directory table and an inode have to be written on another place of the disk, so head movements. A disk image like dd writes many contiguous tracks.
My favourite if I'm making a copy on a different size disk would be a simple "cp -a" with whatever the option is to stop it following mount points. Only good if the disk you are copying to is clean, though. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 14/01/2018 à 11:01, Carlos E. R. a écrit :
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
may be apart disk uid? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-01-14 at 18:58 +0100, jdd@dodin.org wrote:
Le 14/01/2018 à 11:01, Carlos E. R. a écrit :
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
may be apart disk uid?
Everything is copied: data, white space, partition tables, boot code, uids, labels... All. Replace one disk with the other and boot. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpbt/QACgkQtTMYHG2NR9UnLQCfcpCZGt0EKCR516sniPEAWE1t +fUAnA4W442THzrjWitxvaDFW9a9LVNs =JXj3 -----END PGP SIGNATURE-----
On Sun, 14 Jan 2018 01:35:35 -0600, David C. Rankin wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
(If I was just doing a clean install, I'd just use a new drive :)
-- David C. Rankin, J.D.,P.E.
Clonezilla is #1 for sure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/14/2018 08:35 AM, David C. Rankin wrote:
All,
Prepping for 42.2 to 42.3 update (yes, I'm actually going to try -- rather than clean install), I want to dump an image of my current 42.2 system to a spare 1T drive. I never do this (other than brute force dd images or shove the spare drive in an use parted to copy partitions).
What is the current favorite (FOSS) disk imaging utility being used. I'm not looking for long - HOWTO answers, just a project name to go look at.
(If I was just doing a clean install, I'd just use a new drive :)
There are a lot of possibilities to create an image of an (unmounted!) filesystem: FILESSYTEM='/dev/sda3' IMAGEFILE="/mnt/backup/image" cat "$FILESSYTEM" > "$IMAGE" or cp --copy-contents "$FILESSYTEM" "$IMAGE" or - I don't see anything wrong with it - the one which is made for this: dd bs=32M iflag=fullblock < "$FILESYSTEM" > "$IMAGE" Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/14/2018 10:55 AM, Bernhard Voelker wrote:
There are a lot of possibilities to create an image of an (unmounted!) filesystem:
FILESSYTEM='/dev/sda3' IMAGEFILE="/mnt/backup/image"
cat "$FILESSYTEM" > "$IMAGE"
or cp --copy-contents "$FILESSYTEM" "$IMAGE"
or - I don't see anything wrong with it - the one which is made for this:
dd bs=32M iflag=fullblock < "$FILESYSTEM" > "$IMAGE"
Have a nice day, Berny
Yes, thanks Carlos, Dave, Per, Wols, Juan and Bernhard, This is the check I wanted. No super-new magic best thing since sliced-bread imaging app. Just good old dd or clonezilla. (or parted, etc..) All the data on the drive is backed up. The only reason I want to image, is if things go south with the upgrade, I want to simply roll 42.2 back over the update mess and restore the 42.2 system. Then I'll yank the drive and do a clean install. I'm looking for the Carlo's method philosophy..
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
(specifically, the "No thinking needed" part for the rollback :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-15 10:49, David C. Rankin wrote:
On 01/14/2018 10:55 AM, Bernhard Voelker wrote:
There are a lot of possibilities to create an image of an (unmounted!) filesystem:
FILESSYTEM='/dev/sda3' IMAGEFILE="/mnt/backup/image"
cat "$FILESSYTEM" > "$IMAGE"
or cp --copy-contents "$FILESSYTEM" "$IMAGE"
or - I don't see anything wrong with it - the one which is made for this:
dd bs=32M iflag=fullblock < "$FILESYSTEM" > "$IMAGE"
Have a nice day, Berny
Yes, thanks Carlos, Dave, Per, Wols, Juan and Bernhard,
This is the check I wanted. No super-new magic best thing since sliced-bread imaging app. Just good old dd or clonezilla. (or parted, etc..)
All the data on the drive is backed up. The only reason I want to image, is if things go south with the upgrade, I want to simply roll 42.2 back over the update mess and restore the 42.2 system. Then I'll yank the drive and do a clean install.
I'm looking for the Carlo's method philosophy..
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
(specifically, the "No thinking needed" part for the rollback :)
LOL. Just remember to unplug the backup disk soon after finishing it - having it connected would confuse YaST a lot. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
I just realized... I use LVM. It lets me do two things in this arena. The fist, obviously, is that I can take a snapshot of a file system. if might happen that the LE I take that onto is on the new drive :-) That way I don't have to work around UUID duplication and a plethora of other things. The second: well I can tell LVM that I have extended LE to the second drive, then tell LVM to migrate all the sectors in that LE from the first drive to the second, then deallocate the the ones on the first drive. As far as LVM is concerned there was one FS and hence on UUDI that for part of the time was distributed over two drives (and how is that different from RAID?). At the beginning it was all on the first drive; at the end it was all on the second drive. At different times I've done both of these. Oh, and you can do them on live file systems. I did the latter once, while working with a DBA to optimize a 200T DB2 database on a large IBM AIX installation. All while the database was running and serving customers. We then said OK to the IBM techs who came in and carted out a bank of RAID drives that we'd just freed up on trolleys and carted in and commissioned and new bank, which we then introduced into the LVM array and redistributed and balanced the database and it performed better of course. We made a point of not telling the users any of this: why worry them? It may seem like a lot of work when written out here, but it's all an excellent example of making the machine work while you go get a coffee (something I'm in favour of), reliable and uncomplicated. LVM is a wonderful tool. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-01-15 13:36, Anton Aylward wrote:
I just realized...
I use LVM. It lets me do two things in this arena.
The fist, obviously, is that I can take a snapshot of a file system. if might happen that the LE I take that onto is on the new drive :-) That way I don't have to work around UUID duplication and a plethora of other things.
The second: well I can tell LVM that I have extended LE to the second drive, then tell LVM to migrate all the sectors in that LE from the first drive to the second, then deallocate the the ones on the first drive. As far as LVM is concerned there was one FS and hence on UUDI that for part of the time was distributed over two drives (and how is that different from RAID?). At the beginning it was all on the first drive; at the end it was all on the second drive.
At different times I've done both of these. Oh, and you can do them on live file systems. I did the latter once, while working with a DBA to optimize a 200T DB2 database on a large IBM AIX installation. All while the database was running and serving customers. We then said OK to the IBM techs who came in and carted out a bank of RAID drives that we'd just freed up on trolleys and carted in and commissioned and new bank, which we then introduced into the LVM array and redistributed and balanced the database and it performed better of course. We made a point of not telling the users any of this: why worry them?
It may seem like a lot of work when written out here, but it's all an excellent example of making the machine work while you go get a coffee (something I'm in favour of), reliable and uncomplicated. LVM is a wonderful tool.
While that is true, the use case here was a backup copy for restoring in case of disaster, so it needs to be to a different and separate media. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
participants (9)
-
Anton Aylward -
Bernhard Voelker -
Carlos E. R. -
Dave Plater -
David C. Rankin -
jdd＠dodin.org -
Juan R. de Silva -
Per Jessen -
Wols Lists