Rescuezilla needs your support.

Contribute $1/month on the crowdfunding website Patreon so Rescuezilla can continue to be developed

Need Help?

Please take a moment to read the FAQ below, as it has the answers to the most common questions about Rescuezilla. If you don't find the answer here, please search the Rescuezilla limitations and GitHub issues.

Rescuezilla an actively developed version of an old application named Redo Backup and Recovery. Rescuezilla provides world-class support to as many users as possible. The official Rescuezilla Sourceforge forum is used to provide Rescuezilla support. Please read the information below before posting.

Frequently Asked Questions

Q: How do I restore individual partition(s)?

A: Rescuezilla is currently only suitable for backup and restore of whole hard drives. It is not yet well-suited for restoring single partitions individually, as might be desired for users with dual-boot systems. Even with this limitation Rescuezilla is still useful for many end-users. The tracking number for this task is #46 and it will be completed for Rescuezilla v1.0.7 (should be released in mid-October 2020).

Q: I want to surgically move a partition from one drive to another. Is Rescuezilla suitable for me?

A: No, absolutely not. Again, as stated in the Rescuezilla limitations page, Rescuezilla currently only officially supports backing up and restoring entire disks. Individual partition backup and restore is very immature right now and is not recommended. Rescuezilla v1.0.7 will improve this.

Q: Is Rescuezilla a drop-in replacement to Clonezilla?

A: No, not yet. However, Rescuezilla v1.0.7 will support the image format used by Clonezilla. This will mean backups created by Clonezilla will be able to be restored with Rescuezilla (and vice versa). The tracking number for this task is #4. Please support Rescuezilla by contributing $1/month on the crowdfunding website Patreon to support the implementation of this feature (and many others).

Q: Can I restore a backup to a smaller drive?

A: No, Rescuezilla currently does not support this. Rescuezilla v1.0.6 only supports restoring backups to a drive of equal or greater size.

Q: Does Rescuezilla support EFI?

A: Yes, since v1.0.6 the 64-bit version of Rescuezilla can boot on any EFI-only machine (including with Secure Boot enabled), and both Rescuezilla 32-bit and 64-bit can boot on legacy PC-BIOS machines. Rescuezilla can safely backup and restore all fileystems on GPT formatted disks often used with EFI systems, as well all filesystems on traditional DOS (MBR) formatted disks.

Q: Is Rescuezilla related to Redo Rescue?

A: Kind of. Both are independent projects but originally built upon the same base. Rescuezilla is a methodical revival an old application named Redo Backup and Recovery which was abandoned by its original author between 2012 and 2020 (leaving hundreds of open forum threads including many users struggling to restore important data without any support being provided). Since the initial release in November 2019, the Rescuezilla developer has systematically unified a number of unofficial customized Redo Backup and Recovery versions (including language translations) into a single version that, after many attempts to contact the original author with the changes, was reluctantly released under the new name “Rescuezilla”. The Rescuezilla developer continues to release new versions to provide new features, bug fixes, backwards compatibility, and user support for everybody to benefit from, including a major upgrade planned for v1.0.7.

In June 2020, the original Redo Backup and Recovery author suddenly resurfaced after a 7.5 year absence and released a new version named “Redo Rescue” with some features that were planned for Rescuezilla v1.0.7. The original author deleted all of the user-support that Rescuezilla was systematically providing to the hundreds of open forum threads. Despite this, Rescuezilla will continue to be actively developed, and from v1.0.7, Rescuezilla will always maintain complete feature parity and restore compatibility with Redo Rescue, in addition to the already planned Clonezilla image format support and other Rescuezilla-specific enhancements and improvements.

Q: Rescuezilla v1.0.6 64-bit takes a long time to shutdown. How do I fix this?

A: Sorry for any inconvenience. This situation has been fixed in Rescuezilla v1.0.6.1.

Q: Rescuezilla backup and restore is running VERY slow for me. How do I fix this?

A: On machines with 16GB of RAM or greater, backup/restore speeds become intolerably slow when using the 32-bit version of Resecuezilla. On machines 64-bit machines with 16GB of RAM or greater, always use the 64-bit version of Rescuezilla.

Q: Does Rescuezilla support Mac?

A: Yes, since v1.0.6 the 64-bit version of Rescuezilla can boot on all Intel-based Mac's, and Rescuezilla is always able to backup and restore all hard disks without issue. Rescuezilla does not yet support “filesystem-aware” backup of the APFS filesystem (which is used since macOS High Sierra). This means for APFS filesystems Rescuezilla copies both free space and used space, resulting in a larger backup image. A future version of Rescuezilla will add filesystem-aware APFS support. The tracking number for this task is #65.

Q: I restored my Linux backup using Rescuezilla. It boots past the GRUB bootloader fully, but the Linux boot gets stuck at "Rescue Mode" login prompt. How do I fix this?

A: For modern systemd Linux environments (such as Ubuntu 18.04), the partitions listed in the /etc/fstab file must be present for the system to complete booting. This means if the hard drive environment does not match exactly, the system will enter Rescue Mode until the /etc/fstab is modified to only refer to the drives which are present in the system.

Fixing a machine in this situation requires logging in at the Rescue Mode prompt, remounting the root partition as read/write, modifying /etc/fstab to remove the line of the partition which is no longer present, then remounting the root partition as read-only before hard rebooting the machine. There are plenty of guides on the internet to help fix this particular issue. If you need further help, post on the support forum and you will receive detailed assistance for as long as it takes to fix your issues.

Please note, in some older Linux distributions it's not the partition's UUID that is used by /etc/fstab but the partition's device node (eg. /dev/sdc1). This means the Linux boot is expecting a hard drive connnected to an identical numbered SATA port! But don't worry, any problems can be resolved by modifying /etc/fstab. As mentioned, if you need more help please ask for it on the support forum.

Q: My Linux backup created with Rescuezilla v1.0.5.1 (or earlier) does not boot. How do I fix this?

A: A small number of backups of Linux environments that were created with Rescuezilla v1.0.5.1 or earlier are unable to have the GRUB bootloader restored correctly, leaving the user unable to boot into their systems. The root cause is Rescuezilla v1.0.5.1 not fully backing up certain larger-than-typical GRUB bootloaders which sometimes reside on traditional DOS (MBR) formatted disks. This issue reportedly affected a small number of Ubuntu, Linux Mint, MXLinux and Peppermint Linux environments. A deeper technical explanation is available in #64.

But don't worry, all your data is completely safe. If you're one of the unlucky few users experiencing this issue, a GRUB repair needs to be manually conducted for your system to properly boot. First, try restoring with the latest version of Rescuezilla. Then use Rescuezilla to follow this guide. If you need more detailed support, post on the support forum to receive direct support for as long as it takes to restore your system to full operation.

Since Rescuezilla v1.0.6, these larger-than-typical GRUB bootloaders are correctly backed up, so everything should restore correctly. If you discover any situation where something is not restoring correctly, please immediately report a bug.

Q: I am having trouble connecting to a network shared directory using SMB/CIFS?

A: First make sure the fields have the correct UNC path (eg "\\fileserver\johnsmith") and username/password. Some network shares may not support the default SMB 3.1.1 protocol, so you may need to enter '2.1' or even '1.0' in the version field. There's also an issue with samba servers hosted on Ubuntu 20.04 that is currently being investigated.

Q: How do I install new software packages?

A: It is possible for advanced users to use the command-line to install software from Ubuntu (remember to first run 'apt-get update'). However any newly installed software lives only in your computer's main memory so will disappear when you reboot your computer (see next question). Also on machines without much RAM, please always double-check you have enough free space before installing anything.

Q: Can I modify Rescuezilla to save my settings between reboots?

A: No, not easily. The Rescuezilla USB stick operates in a read-only mode and loads a “nonpersistent” environment into your computer's memory. This environment disappear after you reboot your computer, along with any modifications you have made. Some users have requested Rescuezilla switch to a “persistent” environment. This feature request is tracked by task #8. Please support Rescuezilla by contributing $1/month on the crowdfunding website Patreon to support the implementation of this feature (and many others).

Q: Is Rescuezilla related to Clonezilla?

A: Rescuezilla has no relation to Clonezilla, which is a separate project by a different developer. However, Rescuezilla v1.0.7 will be optionally be able to backup and restore hard drives in same image format used by Clonezilla.

Q: Can I use the same Rescuezilla USB drive with many computers simultaneously?

A: Yes. Select the 'Safe Mode' menu item (which includes the 'toram' parameter) and wait for the system to boot before removing the USB drive. Because this loads all of Rescuezilla into memory, please note the minimum RAM requirements are higher.

Report a Bug

If you have encountered a bug, please review this checklist:

  • Please double-check you are using the latest version of Rescuezilla, and check whether the bug is already listed in the Bug Advisories table.
  • Is the problem the result of the Rescuezilla program, or is it a hardware incompatibility issue that should be reported to Ubuntu Linux?
  • If you provide the steps, can the error be reproduced by the Rescuezilla developer?
Create a GitHub issue with details of the bug (please attach the log files from your backup directory, and provide as much information as possible)


If you need help restoring your data (or have questions, suggestions and requests) please visit the official Rescuezilla Sourceforge forum. For best results, create an account and always write descriptive subject lines and provide enough detail. You will receive direct support from the Rescuezilla developer for as long as it takes to restore your system to full operation.

Rescuezilla support is not provided over email as any discussion is usually of interest to the broader community. Instead it is provided on the official Rescuezilla Sourceforge forum. Again, before creating any new forum posts, please first read this FAQ, the bug advisories section, and search the GitHub issues and the forum.

Rescuezilla needs your support.

Contribute $1/month on the crowdfunding website Patreon so Rescuezilla can continue to be developed