zfsnap - GitLite

KO | EN

gitlite — search

#javascript #python #react #typescript #golang #android #deep-learning #docker #java #cli #kubernetes #vue #pytorch #openai

zfsnap

(★ 370)

A portable, performant script to make rolling ZFS snapshots easy. (https://github.com/zfsnap/zfsnap/issues/109)

파일 탐색기

최종 버전 다운로드 (.zip)

- - tests.yml
- zfsnap-completion.bash
- zfsnap-completion.tcsh
- zfsnap-completion.zsh
- - zfsnap.8
- xPERIODICx_zfsnap.sh
- xPERIODICx_zfsnap_delete.sh
- zfsnap.sh
- - core.sh
- - 000_label.sh
  - getopts.sh
- - 000_label.sh
  - destroy.sh
  - snapshot.sh
- - 000_label.sh
  - bytes_to_human.sh
  - date_plus_ttl.sh
  - fs_exists.sh
  - greater_date.sh
  - is_false.sh
  - is_int.sh
  - is_leap_year.sh
  - is_snapshot.sh
  - is_true.sh
  - pool_exists.sh
  - skip_pool.sh
  - trim_to_date.sh
  - trim_to_file_system.sh
  - trim_to_pool.sh
  - trim_to_prefix.sh
  - trim_to_snapshot_name.sh
  - trim_to_ttl.sh
  - valid_date.sh
  - valid_prefix.sh
  - valid_snapshot_name.sh
  - valid_ttl.sh
- - fix_sunos.sh
  - test_shells.sh
  - test_vagrants.sh
  - Vagrantfile
- prepare.sh
- run.sh
- spec_helper.sh
- mod_shebang.sh
.cirrus.yml
.gitignore
AUTHORS
INSTALL
LICENSE
NEWS
PORTABILITY
README.md
TESTING

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Note

This branch contains the new 2.0 code-base which is in beta. While 2.0 is a big
step forward and has far better testing, it has not been used as widely in
production as the zfSnap 1.x line.

Testing is most welcome, but use at your own risk.

Please use the "legacy" branch for the older, more battle-tested version of zfSnap.

# About zfsnap

zfsnap makes rolling ZFS snapshots easy and — with cron — automatic.

The main advantages of zfsnap are its portability, simplicity, and performance.
It is written purely in /bin/sh and does not require any additional software —
other than a few core *nix utilies.

zfsnap stores all the information it needs about a snapshot directly in its name;
no database or special ZFS properties are needed. The information is stored in
a way that is human readable, making it much easier for a sysadmin to manage
and audit backup schedules.

Snapshot names are in the format of pool/fs@[prefix]Timestamp--TimeToLive (e.g.
pool/fs@weekly-2014-04-07_05.30.00--6m). The prefix is optional but can be quite
useful for filtering, Timestamp is the date and time when the snapshot was
created, and TimeToLive (TTL) is the amount of time the snapshot will be kept
until it can be deleted.

# Need help?

The wiki covers zfSnap 1.x. https://github.com/zfsnap/zfsnap/wiki

For information about zfsnap 2.0, please refer to the manpage or the [zfsnap
website](http://www.zfsnap.org).

We have a mailing list (zfsnap@librelist.com) for questions, suggestions, and
discussion. It can also be found at gmane.comp.sysutils.zfsnap on gmane.

# Will zfsnap run on my system?

zfsnap is written with portability in mind, and our aim is for it to run on
any and every OS that supports ZFS.

Currently, zfsnap supports FreeBSD, Solaris (and Solaris-like OSs), Linux,
GNU/kFreeBSD, and OS X. It should run on your system as long as:
- ZFS is installed
- your Bourne shell is POSIX compliant and supports "local" variables (all modern systems should)
- your system provides at least the most basic of POSIX utilities (uname, head, etc)
- your system uses the Gregorian calendar

See the PORTABILITY file for additional information on specific shells and OSs.