Steps to Backup Linux Disk Using dd: A Comprehensive Guide for Ubuntu 18.04

Understanding the dd Command

The dd utility is a powerful low-level tool available in most Linux distributions, including Ubuntu 18.04. It copies data from one location to another with precision, making it ideal for creating full disk images. Unlike higher-level tools that might skip empty blocks or handle metadata differently, dd works at the block level. This means it reads every single sector from the source disk and writes it to the target, ensuring a bit-for-bit replica. While this guarantees completeness, it also requires careful handling because mistakes can lead to data loss if the wrong devices are selected.

Preparation and Safety Checks

Before executing any backup commands, you must identify the correct device names for both your source and destination disks. Using the wrong device name can result in overwriting your primary operating system instead of creating a backup. Open a terminal and use the lsblk command to list all block devices. Look for the disk containing your Ubuntu installation, typically identified as sda, vda, or nvme0n1 depending on your hardware. Ensure that the destination drive has sufficient capacity to hold the entire image of the source disk. If you are backing up to an external USB drive, verify that it is mounted or accessible but not actively writing to it during the process.

It is also crucial to unmount any partitions on the source disk that you intend to back up. While dd can read mounted filesystems, doing so may result in inconsistent snapshots if files are being modified during the copy. For a consistent state, consider booting from a Live USB environment. This approach allows you to access the disk without the operating system actively using it, ensuring a clean and stable backup. If you must back up while running, ensure no critical services are modifying large files during the operation.

Executing the Backup Command

Once you have identified your source and destination devices, you can construct the dd command. The basic syntax involves specifying the input file (if) as the source disk and the output file (of) as the destination. For example, to back up the entire disk /dev/sda to a file named backup.img on an external drive mounted at /mnt/external, you would use the following command:

sudo dd if=/dev/sda of=/mnt/external/backup.img bs=4M status=progress

In this command, bs=4M sets the block size to 4 megabytes, which optimizes the transfer speed by reducing the number of read/write operations. The status=progress flag is essential for long-running backups, as it displays the amount of data transferred so far. Without this flag, the terminal will appear frozen, leading users to prematurely interrupt the process. Always run this command with sudo privileges, as reading raw disk devices requires root access.

If you prefer to save the backup as a compressed file to save space, you can pipe the output to gzip. However, note that compression significantly increases CPU usage and may slow down the process. A typical command for compressed backup looks like this:

sudo dd if=/dev/sda bs=4M | gzip > /mnt/external/backup.img.gz

This method creates a smaller file but requires more time to complete. Choose the uncompressed method if speed is your priority and you have ample storage space. Remember that the resulting image file will be the same size as the source disk, even if the disk is mostly empty, unless you use specialized tools that skip unused blocks.

Restoring and Verification

To restore the backup, reverse the roles of the input and output files. Use the same dd command structure but swap if and of. Be extremely cautious during restoration, as this operation will overwrite the destination disk completely. Verify the integrity of the backup by comparing checksums of the source and destination after creation. You can use sha256sum to generate hashes for both the original disk and the image file, ensuring they match perfectly.

For those managing complex setups involving encrypted volumes, understanding how to handle LUKS headers is vital. If your system uses LVM with LUKS encryption, refer to our guide on Backup and Restore Partition Information for Ubuntu LUKS LVM on a 250GB SSD for specific instructions on preserving cryptographic metadata alongside the disk image.

Frequently Asked Questions

Can I use dd to backup only specific partitions?

Yes, you can target specific partitions by replacing the disk identifier with the partition identifier, such as /dev/sda1 instead of /dev/sda. This creates an image of just that partition rather than the entire disk, which is useful for saving space when you do not need to backup the whole drive.

What happens if I select the wrong output device?

Selecting the wrong output device will overwrite the data on that drive immediately and irreversibly. There is no undo function for dd, so triple-check your of parameter before pressing enter. Always verify device names using lsblk or fdisk -l to avoid catastrophic data loss.

Is dd faster than other backup tools like rsync?

dd is generally faster for creating full disk clones because it does not check file contents or permissions, simply copying raw bytes. However, rsync is better for incremental backups and file-level synchronization, as it only transfers changed files and preserves attributes. Choose dd for disaster recovery images and rsync for regular file backups.

How do I monitor the progress of a dd backup?

Use the status=progress option in newer versions of GNU coreutils to see real-time transfer statistics. For older systems, you can send a USR1 signal to the dd process using pkill -USR1 dd to print progress without stopping the operation.

Does dd work on network drives?

You can direct the output to a network share by mounting it locally first, then pointing of to a path on that mount. Alternatively, you can pipe the output directly to ssh or nc (netcat) to stream the image over the network, though this may introduce latency and require more bandwidth.