-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathbackupld.conf
More file actions
91 lines (85 loc) · 2.65 KB
/
backupld.conf
File metadata and controls
91 lines (85 loc) · 2.65 KB
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
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# Main settings
#
::BACKUP_
# Set the name of the archive that will get saved to each repo.
# 'date' is a special name that will use the date in YYYYMMDD format
NAME = date
# The name of your remote host
# This should be set with an SSH key in your SSH 'config' file
HOST = someOtherServer
# The day of the week to run validity checks
# Uses $(date +%u) so numbers are (1..7); 1 is Monday
CHECK_DAY = 7
# What do we care about?
# In the format: repoName = /directory/to/backup
#
# Support for encrypted repos is available, just append the passphrase:
# repoName = /directory/to/backup;passphrase123
#
==LOCAL_BACKUP_DIRS
vhosts = /var/www/vhosts
git = /home/git
cron = /var/spool/cron;CronSaf3ty
# How often do we want to prune?
# (How many to keep on each timescale)
#
# 'default' is the default setting for all repos.
# For individual repo settings, use the name of the repo instead
# If you don't set a repo specifically, it will use the default setting
# If you don't set a default setting, no pruning is done on this timescale
# Supports hourly, daily, weekly, monthly and yearly
#
==PRUNE_DAILY
default=7
==PRUNE_WEEKLY
default=4
==PRUNE_MONTHLY
default=6
# How do we want to send notifications?
# Supported methods are 'email', 'pushover' or 'file'
#
# Email ---
# Set type: TYPE = email
# We use Mandrill or Mailgun, set your keys as so:
# MANDIRLL = <key here> or
# MAILGUN = <key here>
# with Mailgun, you also need to set the name of the api domain:
# MAILGUN_API_DOMAIN = example.com
#
# FROM_DOMAIN is the domain of the sender: example.com
# MESSAGE is the body of the email in text (no HTML)
# EMAIL_SUBJECT is the subject of the email (amazing!)
#
# Pushover ---
# Set type: TYPE = pushover
# Using Pushover.net, set your keys as so:
# PUSHOVER_API_KEY = <api key hare>
# PUSHOVER_USER_KEY = <user key here>
#
# Pushover supports the MESSAGE option too
# MESSAGE = <body of notification>
#
# File ---
# Set type: TYPE = file
# The log file will be copied per user,
# specify location for each one with NOTIFY_USERS.
# To echo to the console as well, set
# ECHO = true
#
# Extra ---
# Both the message and subject support some macros:
# 'name' will be changed to the name of the archive
# 'date' is changed to the date from above: YYYYMMDD
# 'fail_count' is changed to the failure count of the backups
#
::NOTIFY_
TYPE = email
MANDRILL = sajnDCSsSDCnkiaScERPOJ
FROM_DOMAIN = example.com
MESSAGE = Completed with fail_count errors.
EMAIL_SUBJECT = [Daily name] Failure Count fail_count
# Who should we tell?
# In the format: Recipient Name;recipient@email.address
# Or: Recipient Name;/path/to/file
--NOTIFY_USERS
Joe Eaves;joe@example.com