Skip to content

Latest commit

 

History

History
110 lines (75 loc) · 3.27 KB

README.md

File metadata and controls

110 lines (75 loc) · 3.27 KB
Raw

ZnapZend 0.15.7

Build Status Coverage Status [Gitter](https://gitter.im/oetiker/znapzend?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=body_badg e)

ZnapZend is a ZFS centric backup tool. It relies on snapshot, send and receive todo its work. It has the built-in ability to manage both local snapshots as well as remote copies by thining them out as time progresses.

The ZnapZend configuration is stored as properties in the ZFS filesystem itself.

Zetup Inztructionz

Follow these zimple inztructionz below to get a custom made copy of znapzend. Yes you need a compiler and stuff for this to work.

On RedHat you get the necessaries with:

yum install perl-core

On Ubuntu / Debian with:

apt-get install perl

On Solaris you may need the c compiler from Solaris Studio and gnu-make since the installed perl version is probably very old.

On OmniOS/SmartOS you will need perl and gnu-make

with that in place you can now utter:

wget https://github.com/oetiker/znapzend/releases/download/v0.15.7/znapzend-0.15.7.tar.gz
tar zxvf znapzend-0.15.7.tar.gz
cd znapzend-0.15.7
./configure --prefix=/opt/znapzend-0.15.7

If configure finds anything noteworthy, it will tell you about it. If any perl modules are found to be missing, they get installed locally into the znapzend installation. Your perl installation will not get modified!

make
make install

Optionally (but recommended) put symbolic links to the installed binaries in the system PATH.

for x in /opt/znapzend-0.15.7/bin/*; do ln -s $x /usr/local/bin; done

Configuration

Use the znapzendzetup program to define your backup settings. For remote backup, znapzend uses ssh. Make sure to configure password free login for ssh to the backup target host.

Running

The znapzend demon is responsible for doing the actual backups.

To see if your configuration is any good, run znapzend in noaction mode first.

znapzend --noaction --debug

If you don't want to wait for the scheduler to actually schedule work, you can also force immediate action by calling

znapzend --noaction --debug --runonce=<src_dataset>

then when you are happy with what you got, start it in daemon mode.

znapzend --daemonize

Best is to integrate znapzend into your system startup sequence, but you can also run it by hand. See the init/README.md for some inspiration.

Statistics

If you want to know how much space your backups are using, try the znapzendztatz utility.

Support and Contributions

If you find a problem with znapzend, please open an Issue on GitHub.

If you like to get in touch, come to [Gitter](https://gitter.im/oetiker/znapzend?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=body_badg e).

And if you have a contribution, please send a pull request.

Enjoy!

Dominik Hassler & Tobi Oetiker 2016-05-09