v2.3 (2021-12-24)
This release is old. Always use the latest release.
The main additional feature for Rescuezilla v2.3 is basic image verification, as well as a new "rescue" option to force filesystem errors to be ignored. Virtually all partclone-based tools other than Clonezilla always ignore errors using partclone's --force option, which I think is a bad idea. Some bugs and important feature requests from Rescuezilla v2.2 continue to remain yet-unaddressed, including unfortunately the highly requested "persistent partition" feature as it still requires further changes and testing. Sorry I could implement more for this release, I was focused on moving from Australia to America to start a new job.
I am aiming to release a feature update in February 2022, in addition to the scheduled 6-monthly May 2022 feature update to try and maintain the project's velocity. Here is a partial list of what’s changed in Rescuezilla v2.3:
- Implemented image verification feature (#30)
- Adds "Rescue" option to ignore filesystem inconsistencies and bad sectors (#237)
- Replaces Ubuntu 21.04 (Hirsute) build with build based on Ubuntu 21.10 (Impish) for best support of new hardware
- Added ability to restore and explore images created by "Apart" partclone GUI (#230)
- Improved image scanning to try to fix report of where some images not scanning except with Browse (#251)
- Fixed display of LVM shutdown error message (#250)
- Displayed serial number of drives in response to feedback (#227)
- Added lxappearance package to make it easy to set the dark theme (#275)
- Added ability to open file manager as root using right-click (#281)
- Added user-provided Intel Xorg conf file to hopefully stop screen tearing (#281)
- Fixed issue preventing restoring of images created by FSArchiver/qtfsarchiver (#255)
- Switched to "xdg-open" to launch file manager and web browser, rather than hardcoding pcmanfm and Firefox
- Added (or significantly updated) translations:
For full details available in the changelog.
Please consider giving a like on AlternativeTo so that more people can discover Rescuezilla! Thanks to the 48 people who support Rescuezilla by contributing $1/month on the crowdfunding website Patreon.
Compatibility
Rescuezilla creates backups that are fully compatible with the industry-standard Clonezilla tool. Rescuezilla works with images created by:
- Clonezilla
- Rescuezilla
- Every virtual machine image format supported by the
qemu-nbdutility. Eg,- VirtualBox’s VDI
- VMWare’s VMDK
- Qemu’s QCOW2
- Hyper-V's VHDx
- raw .dd/.img
- ...and more!
- Redo Rescue
- Foxclone
- FOG Project (still in-development: only supports Windows MBR/GPT disks due to FOG Project's more advanced image manipulation)
- FSArchiver (restore only, not explore)
- Apart GTK
- Redo Backup and Recovery (v0.9.2 format, v0.9.3-v1.0.4 format and the old community updates)
Bug advisories
Rescuezilla is thoroughly tested using Windows, Linux, and Mac environments. The following are known bugs in v2.3. Please regularly consult the following table (and the links below the table) in case new bugs are discovered.
| Severity | Tracking # | Description | Fixed in release |
|---|---|---|---|
| High | #297 | Rescuezilla v2.3 broke disk cloning feature, leading to a "stuck at 0%" issue whenever any clone is attempted. This has been fixed in v2.3.1 and it's recommend all users upgrade. | v2.3.1 |
| High | #254 | When making a backup of a Windows drive, some users report the error "Windows is hibernated, refused to mount" or "Error: read-only file system" and a failed backup. This is usually due to Windows' hibernate feature, with widely used workaround to select 'Restart' (not shutdown) from the Windows Start Menu before booting the Rescuezilla USB stick. But some users are reporting even after doing a full restart the problem is now persisting, with the only workaround for these users to disable hibernation entirely (which is definitely not a good solution). This issue is being investigated as part of task #254 | |
| Low | #168 | Rescuezilla uses the version of partclone that’s available in the official Ubuntu repositories, so handling of the uncommon Btrfs filesystem is worse than Clonezilla which uses a more recent partclone version compiled from source. This only matters if you use a Btrfs filesystems using more recent features like "zstd transparent compression", which even many Btrfs filesystem users will not be using. A future version will compile partclone from source like Clonezilla rather than using the older Ubuntu repository versions. |
There may be other bugs listed on the Rescuezilla v2.3 development page. If you encounter any additional bugs, please report them (ideally with logs) on the GitHub issues page (after searching for duplicate issues).
Checksums
sha256sum:
d8bf6d271bf117ec201291751b701751502487cee674b1fe6e18e2a924d2b7e4 rescuezilla-2.3-64bit.impish.iso
56046d20ca5ddfac2f08bbe093cc9d76e5f5b260079f89ac576d499aa1d1b51f rescuezilla-2.3-64bit.focal.iso
sha1sum:
6b34e36e423132c61411d7bc74551addb38c7c93 rescuezilla-2.3-64bit.impish.iso
0a894658bc893b56421dc24cb45c5793a05e7291 rescuezilla-2.3-64bit.focal.iso
md5sum:
1881a8af1c6252c4adc1be61162d7e18 rescuezilla-2.3-64bit.impish.iso
b0d0afeb60c79cce8f84c6ee22b723c0 rescuezilla-2.3-64bit.focal.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 joining AlternativeTo and giving the project a like -- as of writing, Rescuezilla has 61 likes compared to Clonezilla's 426 likes, so fewer people are discovering Rescuezilla.
Download
This release is old. Always use the latest release.