Skip to content

Commit b34bae8

Browse files
committed
Updated README
1 parent bf74949 commit b34bae8

File tree

1 file changed

+47
-17
lines changed

1 file changed

+47
-17
lines changed

README.md

+47-17
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,34 @@
1-
Python Incremental Backup Scripts
1+
Python Backup Scripts
22
=============
33

44
Python scripts for incremental backups of servers. This includes filesystem
5-
backup and mysql backup.
5+
backups and mysql backups.
66

7-
8-
Filesystem Backups
7+
Pulled Backups
98
===========
10-
Filesystem backups are done through the incrbackup script.
9+
Pulled filesystem backups are done through the incrbackup.py script. Backups
10+
are pulled down from remote systems to the backup server for security, the
11+
backup server can get to the remote systems being backed up but not vice versa.
12+
Hence if a remote system is compromised the backup server isn't.
1113

12-
Filesystem backups use rsync and hard links to keep multiple copies of one or
14+
Pulled backups use rsync and hard links to keep multiple copies of one or
1315
more filesystems while using minimal space. If backing up remote
1416
servers this script assumes that the proper ssh keys have been setup from the
1517
backup server hosting this script to the servers being backed up.
1618

17-
A pid file is placed into the system temp directory to prevent concurrent
18-
backups from running at once. The script provides options for the number of
19-
backups to keep. After the max number of backups is reached, backups are
20-
deleted starting with the oldest backup first.
21-
2219
Backup paths can be either local or remote. The backup directory where
2320
the backups are stored must be local and must already exist. If a users isn't
2421
specified then the remote user used by ssh for rsync is considered to be a
2522
user named backup.
2623

2724
Use the -h or the --help flag to get a listing of options.
2825

29-
incremental_backup.py [-hnksftu]
26+
incrbackup.py [-hnksctu]
3027
[-h | --help] prints this help and usage message
3128
[-n | --name] backup namespace
3229
[-k | --keep] number of backups to keep before deleting
3330
[-s | --server] the server to backup, if remote
34-
[-f | --config] configuration file with backup paths
31+
[-c | --config] configuration file with backup paths
3532
[-t | --store] directory locally to store the backups
3633
[-u | --user] the remote username used to ssh for backups
3734

@@ -56,9 +53,38 @@ Usually the backup scripts are run from a remote, off-site, server pulling down
5653
content from the servers to backup. Scripts are usually setup to run from cron
5754
periodically.
5855

56+
57+
Pushed Filesystem Backups
58+
===========
59+
Pushed filesystem backups are done through the pushbackup.py script.
60+
61+
his is an incremental backup system that pushes to a remote server. Useful
62+
for remote systems that aren't always on (laptops). Backups use rsync and hard
63+
links to keep multiple full copies while using minimal space. It is assumed
64+
that the rotatebackups.py script exists on the remote backup server and that
65+
the proper ssh keys have been setup from the pushing server to the backup
66+
server.
67+
68+
Use the -h or the --help flag to get a listing of options.
69+
70+
pushbackup.py [-hnksctuxr]
71+
[-h | --help] prints this help and usage message
72+
[-n | --name] backup namespace
73+
[-k | --keep] number of backups to keep before deleting
74+
[-s | --server] the server to push to backup to
75+
[-c | --config] configuration file with backup paths
76+
[-t | --store] directory locally to store the backups
77+
[-u | --user] the remote username used to ssh for backups
78+
[-x | --ssh-key] the ssh key used to connect to the backup
79+
[-r | --rotate-script] the rotatebackups script remote location
80+
81+
Pushed backup use the same config format as pulled backups. Pushed backups are
82+
usually run manually when needed. They should not be used to backup servers due
83+
to security reasons. If backing up server filesystem see pulled backups.
84+
5985
MySQL Backups
6086
===========
61-
MySQL backups are done through the mysqlbackup script.
87+
MySQL backups are done through the mysqlbackup.py script.
6288

6389
A pid file is placed into the system temp directory to prevent concurrent
6490
backups from running at once. The script provides options for the number of
@@ -67,13 +93,17 @@ deleted starting with the oldest backup first.
6793

6894
Use the -h or the --help flag to get a listing of options.
6995

70-
mysqlback [-hnkdbus]
96+
mysqlbackup.py [-hkdbups]
7197
[-h | --help] prints this help and usage message
7298
[-k | --keep] number of backups to keep before deleting
7399
[-d | --databases] a comma separated list of databases
74-
[-b | --backup-root] directory locally to store the backups
100+
[-t | --store] directory locally to store the backups
75101
[-u | --user] the database user
76102
[-p | --password] the database password
77103
[-s | --host] the database server hostname
78104

79-
Please feel free to send any improvements or bug fixes.
105+
License and Bug Fixes
106+
===========
107+
These works are public domain or licensed under the Apache Licene. You can do
108+
anything you want with them. Please feel free to send any improvements or
109+
bug fixes.

0 commit comments

Comments
 (0)