1
0
mirror of https://github.com/deajan/obackup.git synced 2024-11-12 19:03:42 +01:00

fixed some typos.

This commit is contained in:
deajan 2013-06-13 08:24:25 +02:00
parent 938803a188
commit 16a948098b

View File

@ -13,14 +13,15 @@ Every action gets logged, and at the end of the backup process, if there was a w
a stopped task or an error an alert email will be sent.
OBackup can enumerate and backup all MariaDB / MySQL databases present on a server.
It can also enumerate all subdirectories of a given path and process them as separate tasks (usefull for multiple vhosts).
It will do several checks before launching a backup like checking backup size and available local disk space.
It can also enumarate all subdirectories of a given path and process them as separate tasks (usefull for multiple vhosts).
It will do several checks before launching a backup like execution checks, dryruns,
checking backup size and available local disk space.
Obackup will work well to backup to a snapshot aware filesystem like ZFS or btrfs.
In case you don't work with one of these, it may also rotate backups for you.
As of today, obackup has been tested successfully on RHEL / CentOS 5, CentOS 6, Debian 6.0.7 and Linux Mint 14
but it should basically run on any linux flavor. It relies on well known programs like rsync, ssh, mysqldump along
but should basically run on your favorite linux flavor. It relies on well known programs like rsync, ssh, mysqldump along
with other great GNU coreutils.
## Installation
@ -28,11 +29,11 @@ with other great GNU coreutils.
You can download the latest obackup script from authors website.
You may also clone this git which will maybe have some recent bugfixes.
$ git clone git://github.com/sickill/bitpocket.git
$ chmod +x ./bin/obackup.sh
$ git clone git://github.com/deajan/obackup.git
$ chmod +x ./obackup.sh
Once you have grabbed a copy of Obackup, just edit it with your favorite text editor to setup your environment
and you're ready to run.
and you're ready to run. A detailled documentation can be found in the CONFIG.TXT file.
You can run multiple instances of obackup scripts with different backup environments. Just copy the script to another
filename, edit it's environment and you're ready to run concurrently.