linux:backup-clone:backup-clone-ssd
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| linux:backup-clone:backup-clone-ssd [2022/09/30 09:49] – oscar | linux:backup-clone:backup-clone-ssd [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Backup or Clone SSD ====== | ||
| - | There are more then enough approaches to backup or clone a SD card. I prefer to use one of the following two approaches: | ||
| - | - Creating a raw diskimage using dd | ||
| - | * Relatively easy | ||
| - | * Makes a diskimage of the complete diskspace, including not used / empty disk space | ||
| - | * Results in a large image. | ||
| - | * Relatively slow. | ||
| - | * Can only be restored on disk with identical of larger size | ||
| - | - Creating a file and partition based disk image (MBR disk) | ||
| - | * Takes a bit more steps | ||
| - | * Makes a diskimage of only the used diskspace, including only used data (files). | ||
| - | * Results in a small image. | ||
| - | * Relatively fast. | ||
| - | * Can be restored on smaller disks | ||
| - | ===== Using dd ===== | ||
| - | This will only work for restoring to a larger or identical size disk. | ||
| - | Backup image will be very large as well. | ||
| - | ==== Create Backup Image ==== | ||
| - | < | ||
| - | dd bs=4M if=/dev/sdb | gzip > image.gz | ||
| - | </ | ||
| - | ==== Restore Backup Image ==== | ||
| - | < | ||
| - | gzip -dc image.gz | dd bs=4M of=/dev/sdb | ||
| - | sync | ||
| - | </ | ||
| - | ==== Monitor Progress ==== | ||
| - | Using dd for large SD cards could be quite lengthy. E.g. a 32Gb card could take up to 20 minutes to read. Use the following steps to watch the progress. First, find out the process id of the dd process by running the following in the new virtual terminal. | ||
| - | < | ||
| - | $ pgrep -l ' | ||
| - | 8789 dd | ||
| - | $ | ||
| - | </ | ||
| - | This shows that the running dd proces has proces Id 8789. The dd process will print out the current statistics when it receives an user signal (USR1). To send the USR1 signal to the dd process: | ||
| - | < | ||
| - | $ kill -USR1 8789 | ||
| - | $ | ||
| - | </ | ||
| - | Note that as soon as the USR1 signal is detected, dd will print out the current statistics to its STDERR. | ||
| - | < | ||
| - | $ dd if=/ | ||
| - | 0+14 records in | ||
| - | 0+14 records out | ||
| - | 204 bytes (204 B) copied, 24.92 seconds, 0.0 kB/s | ||
| - | </ | ||
| - | After reporting the status, dd will resume copying. You can repeat the above kill command any time you want to see the interim statistics. Alternatively, | ||
| - | < | ||
| - | $ watch -n 10 kill -USR1 8789 | ||
| - | </ | ||
| - | ===== Using files archives (MBR disk) ===== | ||
| - | This approach will work for restoring to smaller disks and will result in a minimal sized image. It consist of the following steps: | ||
| - | |||
| - | Backup: | ||
| - | * Save the partition table structure of the SD card | ||
| - | * Save the MBR | ||
| - | * Mount and save the files for each partition in an individual archive | ||
| - | Restore: | ||
| - | * Create the partitions on the new HDD card | ||
| - | * Restore the MBR to new HDD card | ||
| - | * Mount and restore the files in the partitions | ||
| - | |||
| - | Use **lsblk** to figure out the block device of the HDD card. | ||
| - | ==== Save Partition Table Structure ==== | ||
| - | Save the partition table/ | ||
| - | < | ||
| - | sudo sfdisk -d /dev/sdX > part_table | ||
| - | </ | ||
| - | ==== Save the MBR ==== | ||
| - | < | ||
| - | # dd if=/dev/sdX of=mbr.backup.img bs=512 count=1 | ||
| - | </ | ||
| - | ==== Backup the partition data ==== | ||
| - | For each of the partitions do (use the correct fs-type): | ||
| - | < | ||
| - | # umount /dev/sdX1 | ||
| - | # mkdir / | ||
| - | # mount -t ext4 /dev/sdX1 / | ||
| - | # tar -zcvf image-sdX1.tgz / | ||
| - | </ | ||
| - | ==== Restore Partition Table Structure ==== | ||
| - | Restore the partition table/ | ||
| - | < | ||
| - | sudo sfdisk /dev/sdX < part_table | ||
| - | </ | ||
| - | Now we have the empty partitions that needs to be formated. | ||
| - | < | ||
| - | sudo umount /dev/sdbX | ||
| - | sudo mkfs.ext4 -l root /dev/sdbX | ||
| - | </ | ||
| - | ==== Restore the MBR ==== | ||
| - | See explanation on MBR above. For disks with identical partitions and size: | ||
| - | < | ||
| - | # dd if=/ | ||
| - | </ | ||
| - | For disks with different partitions and size: | ||
| - | < | ||
| - | # dd if=/ | ||
| - | </ | ||
| - | ==== Restore the partition data ==== | ||
| - | Let's mount both partitions and restore the files back on the volumes. The absolute path is stored in the tar file and used to restore the files. It is therefore important that the partition is mounted in the same location as it was done while making the backup. And that you execute at /. | ||
| - | < | ||
| - | # mount -t ext4 /dev/sdX1 / | ||
| - | </ | ||
| - | Now restore the files to the partitions. | ||
| - | < | ||
| - | cd / | ||
| - | sudo tar -zxvf image-sdX1.tgz | ||
| - | </ | ||
| - | |||
linux/backup-clone/backup-clone-ssd.1664531348.txt.gz · Last modified: by oscar