Installation | Basic Usage | Documentation | Contributing
A lone hard drive stands atop a data heap, staring at the full moon. Suddenly, it transforms...into a bootable clone of your drive, whirring hungrily at the digital moon.
WereSync takes a Linux hard drive and effectively clones it, but works incrementally so you don't have to spend so long backing up each time. Additionally, WereSync can clone to a smaller drive, if your data will fit on the smaller drive. Because WereSync uses rsync to copy, it can copy a running drive, though certain parts of state may not be preserved.
Hopefully, you think this project looks amazing and you want to try it right away. However, you may be skeptical about the usefulness of WereSync. You may be thinking, I can do this exact same thing using gparted or ddrescue. Hear me out! There are a few reasons to use WereSync over the other tools.
- WereSync is accessible to less-technical users. It comes with a simple interface and clone a drive with a single command while your computer is running. No booting to a live disk or pushing through a long initiation process. Unlike dd or CloneZilla, WereSync requires a low level of technical skill and has an easy learning curve
- WereSync can run while your main drive is being used, instead of blocking your computer up for hours at a time
- WereSync will incrementally update clones, making subsequent clones much faster.
- WereSync works quickly, a single command copies your entire drive, no booting to live CDs or managing MBRs.
- WereSync can copy to a smaller drive, provided your drive's data will fit.
- WereSync creates new UUIDs for the new partitions, allowing you to use the old and new drives alongside each other.
Full documentation may be found here.
WereSync can be installed using the setup.py file.
$ ./setup.py installIf you have pip installed, you can easily install WereSync with the following command:
$ pip install weresync
For more in-depth instructions, see the installation documentation.
Note: The WereSync daemon requires root capabilities to run because it has to access block devices. The client GUI and CLI programs do not need root permissions.
Copy the policy file in src/wersync/resources/weresync-dbus.conf to /etc/dbus-1/system.d. Then start the daemon:
$ sudo weresync-daemon & >/dev/null 2>&1
Then gui can be launched with the command:
$ weresync-gui
Which generates the following GUI, though generally the advanced options are unneeded:
To see the options for the terminal command use:
$ weresync -h
To copy from /dev/sda to /dev/sdb (the two drives must have the same partition scheme) use:
$ weresync /dev/sda /dev/sdb
After the copy is completely finished, you can kill the daemon process.
For more information, including how to copy the partition table from one drive to another, see the Basic Usage documentation page.
Documentation can be found on Read the Docs.
First, take a look at our contribution guidelines.
To contribute simply fork this repository, make your changes, and submit a pull request. Bugs can be reported on the issue tracker
WereSync currently has a huge need of people testing the program on complex drive setups. In order to do this please:
Install WereSync from pip:
pip install weresync
Run it on your system:
sudo weresync -C source_drive target_drive
Report any errors to the issue tracker. Please be sure to post the contents of
/var/log/weresync/weresync.logandfdisk -l.
All contributions will be greatly appreciated!
If you are able to test any of these systems, please report your exprience at the issue tracker. Any help will be much appreciated.
This project is licensed under the Apache 2.0 License. Licensing is in the LICENSE.txt file in this directory.
Huge thanks to the creators of:
- rsync, whose software allowed this project to be possible.
- GNU Parted
- And GPT fdisk