This release is old. Always use the latest release.
Rescuezilla is a fork of Redo Backup and Recovery (now called Redo Rescue) after it had been abandoned for 7 years.
RESCUEZILLA IS NOW OFFICIALLY OPEN FOR TRANSLATIONS!
Rescuezilla v2.0 is a major upgrade. Key changes are summarized below:
- Switched to creating backups in Clonezilla format for full interoperability with Clonezilla: Rescuezilla is now a drop-in replacement to Clonezilla!
In other words, backups created using Clonezilla can be restored using Rescuezilla, and vice versa :) - Warning: Backups created with Rescuezilla v2.0 cannot be restored using earlier versions of Rescuezilla. Backups created with older versions of Rescuezilla can still of course be restored with v2.0
- Added ability to restore individual partitions, and optionally to not overwrite partition table (#46)
- Rewrote the Rescuezilla frontend in the Python3 programming language (#111, #49, #48)
- Added backup/restore confirmation and summary pages, back button (#6)
- Improved exit code handling and error messages (#29, #114), image selection (#109)
- Disabled Linux time sync to prevent hardware clock modification (thanks zebradots!) (#107)
- Added the ability to backup and restore software RAID (md) devices (#45)
- Added the ability to backup and restore SD card (mmcblk) devices (#95)
- Added filesystem-aware backup/restore of Linux Logical Volume Manager (LVM) (#44)
- RESCUEZILLA IS NOW OFFICIALLY OPEN FOR TRANSLATIONS!
The complete list of changes is available in the changelog.
Thank you to the 10 people who support Rescuezilla on Patreon. Future plans include a graphical tool to extract individual files from backup images, a data-salvage tool to rescue data from dying hard drives and much more! Consider contributing $1/month on the crowdfunding website Patreon so that Rescuezilla can continue to be developed.
Backwards compatibility
Rescuezilla v2.0 creates backups using the Clonezilla image format. Backups created with Rescuezilla v2.0 cannot be restored using prior versions of Rescuezilla. Backups created with older versions of Rescuezilla can still of course be restored with v2.0.
Rescuezilla v2.0 supports restoring images created by Clonezilla, Rescuezilla, Redo Backup and Recovery v0.9.8-v1.0.4, and the old, unofficial Redo Backup updates by Sourceforge users OAM775, chcatzsf and louvetch.
Rescuezilla does not yet support restoring Redo Rescue 2.x/3.x image format. Support will be added once other higher priorities tasks have been completed.
Bug advisories
Rescuezilla is thoroughly tested using Windows, Linux, and Mac environments. The following are known bugs in v2.0. Please regularly consult the following table in case new bugs are discovered.
| Severity | Tracking # | Description | Fixed in release |
|---|---|---|---|
| High | #131 | On both Rescuezilla and Clonezilla, if there is a >1024MB gap between the MBR partition table and the first partition on a Linux disk, the backup of the GRUB bootloader is not done. Clonezilla automatically re-installs the GRUB bootloader to workaround this, but Rescuezilla does not yet implement this (task #146). This means on a small number of systems after a backup made with Rescuezilla v2.0 or Clonezilla may not boot without either a GRUB re-install / repair (or alternatively a restore using Clonezilla). If you need assistance with this process please post on the Rescuezilla support forum and you will help for as long as you need. In Rescuezilla v2.1, Rescuezilla correctly makes a backup the GRUB bootloader in this circumstance and displays a warning for such Clonezilla images. In the longer term task #146 will match Clonezilla's automatic GRUB re-install behavior exactly. | v2.1 |
| High | #162 | Due to a pattern matching bug, when restoring MBR backups with default settings, backups created with Clonezilla and Rescuezilla can potentially not boot. This happened to a user using a Windows based network share, but restoring using a locally attached USB drive worked fine for that user. All data within the backup is fine, it's just a bug in the Rescuezilla restore logic. I am still unable to reproduce the error, but the incorrect pattern matching root cause is clear. Rescuezilla v2.1.2 resolved this bug. Until then, restoring using a locally attached USB drive should be a workaround. | v2.1.2 |
| Medium | #127 | A user reports the newly added image scanning feature does not successfully scan some of his legacy images that were created with prior versions of Rescuezilla. The scanning feature will be improved around those problematic images. | v2.1 |
| Medium | #125 | A user has reported v2.0 creates backups much slower than the prior version v1.0.6.1 (1.5GB/minute rather than the previous ~4GB/minute). This issue will be improved in Rescuezilla v2.1. | v2.1 |
| Low | #122 | There has been a report that a drive cannot be queried for its hard drive geometry, which causes the backup to fail. The root cause of this issue is being investigated. | v2.1 |
| Low | #126 | Many users report the newly added image scanning is annoyingly slow. This will be improved in the next version | v2.1 |
| Low | #132 | A user with a disk with apparently inconsistent partitioning has issues backup and restoring their drive using Rescuezilla or other tools. The root cause is still being investigated. | |
| Low | #139 | Images created using Clonezilla's bleeding-edge "testing" releases since October 2020 causes the Rescuezilla v2.0 scanning operation to produce ValueError: too many values to unpack (expected 2). Root cause is due to Clonezilla's changing the dev-fs.list file format slightly. Rescuezilla v2.1 will fix the scanning of such images.
| v2.1 |
| Low | #140 | Setting the "version" field when trying to connect to SMB/CIFS network shares causes the connection to fail due to a bug where the mount.cifs command is missing a comma character. This will be fixed in Rescuezilla v2.1.
| v2.1 |
| Low | #144 | While investigating a user issue I noticed that Rescuezilla does not match Clonezilla's behavior for Windows MSR partitions by creating a certain text file. This may affect using Clonezilla when restoring a Rescuezilla image to a different size drive (proportional restore). In testing Windows 10 has of course been tested to backup and restore without issue. The next version (Rescuezilla v2.1) will create this text file to match behavior with Clonezilla. | v2.1 |
This release is old. Always use the latest version of Rescuezilla
Checksums
sha256sum:
72525c0961708614cd61cd4ecfddf724a24d99be9c1a4c34dc68c7bf366d96ba rescuezilla-2.0-64bit.iso
sha1sum:
d0041c5a72feea70dcf8f7019bf8370896dd74b7 rescuezilla-2.0-64bit.iso
md5sum:
7de4a6e1ead22bcae45cdb7c14da65cc rescuezilla-2.0-64bit.iso
Discussion and User Support
If you need support, start by checking the frequently asked questions, then proceed to the Rescuezilla forum.
Reviews and Testimonials
You can read reviews of Rescuezilla on AlternativeTo. Please consider writing a review and giving the project a like -- as of writing, Rescuezilla has 0 likes and 0 reviews compared to Clonezilla's 406 likes and 14 reviews, so very few people are discovering Rescuezilla.
Download
This release is old. Always use the latest release.