summaryrefslogtreecommitdiff
path: root/defs.m4
blob: da2ad92007ca965c0a92ddd219c365bdbbd0c2a2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
divert(-1)
changequote(`«', `»')

define(«SLOGAN», «the dyadic snapshot scheduler»)
define(«AUTHOR», «Andre Noll»)
define(«EMAIL», «maan@tuebingen.mpg.de»)
define(«URL», «https://people.tuebingen.mpg.de/maan/PACKAGE()/»)
define(«CLONE_URL», «https://git.tuebingen.mpg.de/PACKAGE()»)
define(«GITWEB_URL», «https://git.tuebingen.mpg.de/PACKAGE().git»)
define(«PACKAGE_HOMEPAGE», «https://people.tuebingen.mpg.de/maan/PACKAGE()/»)
define(«HOME_URL», «https://people.tuebingen.mpg.de/maan/»)
define(«LICENSE», «GPL-2.0»)
define(«LICENSE_URL», «https://www.gnu.org/licenses»)

define(«DESCRIPTION1», «dnl
PACKAGE() maintains hardlink-based snapshots of a given directory on
a remote or local host using rsync's link-dest feature. The snapshots
are organized so that any snapshot can directly be deployed as an
(emergency) replacement for the primary system.»)

define(«DESCRIPTION2», «dnl
PACKAGE() is admin friendly: It is easy to configure and needs
little attention after the initial setup. In particular, no full,
incremental or differential backups need to be configured, and there is
no database to maintain. PACKAGE() is also user-friendly: Assuming the
snapshot server allows read-only user access over the network, users
can restore accidentically removed files without admin intervention,
using their favorite file browser to copy files from the snapshot
directory back to the primary system.»)

define(«DESCRIPTION3», «dnl
PACKAGE() keeps track of the age and the state of existing snapshots and
triggers snapshot creation and removal according to the configuration
settings. It tries to maintain a scheme where many recent snapshots
and few old snapshots exist, for example 16 snapshots newer than a
week, 8 snapshots between one and two weeks old, 4 snapshots between
two and three weeks old, and so on.»)

divert(0)