Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Jan 2007 13:08:13 +0100
From:      bsd <bsd@todoo.biz>
To:        Gable Barber <gablebarber@gmail.com>
Cc:        Liste FreeBSD <freebsd-questions@freebsd.org>
Subject:   Re: Sorta OT - Backup solutions Mac to FreeBSD
Message-ID:  <E91547B4-AF7B-4BC4-AF1A-9CE2349F2195@todoo.biz>
In-Reply-To: <aab166ce0701261310y2b6b6855o42ce8f426b04d42d@mail.gmail.com>
References:  <aab166ce0701261310y2b6b6855o42ce8f426b04d42d@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Hello,

I am backing up 5 servers on one centralized machines using =20
"rsnapshot" It is doing a perfect job, including :

--> SSH transport.
--> Rsync based.
--> Incremental backup.

As It uses a symlink strategy, It does not use very much space on the =20=

backup device.

It is in the ports /usr/ports/sysutil/rsnapshot and described as :

rsnapshot is a filesystem snapshot utility based on rsync(1).
rsnapshot makes it easy to make periodic snapshots of local machines,
and remote machines over ssh. The code makes extensive use of hard links
whenever possible, to greatly reduce the disk space required.

It is written entirely in perl with no module dependencies, and has been
tested with versions 5.004 through 5.8.1.

WWW:    http://www.rsnapshot.org

----------

I am backing up 2To of data, with a daily flow of 20 to 100 Go.
The first backup is quite long - after it's a matter of hours (1 or 2 =20=

max).


In order to fully automate the process, I have created an ssh key =20
signature that allows me to access directly as root - if you would =20
like more security, you could create a specific user=85 which will lead =20=

you to ownership problem, unless very well setup.


The main problem with mac would be to sync the specific MetaData =20
files specific to the Mac.
I don't think these are synced in my backup. This is only a problem =20
if your users are not naming their files with the right extension =20
(.doc, .pdf, =85).

If you are syncing OSX 10.4 use the Apple provided rsync and not any =20
other (more steady).


The main piece if to configure rsnapshot.conf && cron


########
# Cron #
########

0 3 * * 1,2,3,4,5,6,7 /usr/bin/rsnapshot daily;
0 4 1 * * /usr/bin/rsnapshot monthly;




#################################################
# rsnapshot.conf - rsnapshot configuration file #
#################################################
#                                               #
# PLEASE BE AWARE OF THE FOLLOWING RULES:       #
#                                               #
# This file requires tabs between elements      #
#                                               #
# Directories require a trailing slash:         #
#   right: /home/                               #
#   wrong: /home                                #
#                                               #
#################################################

#######################
# CONFIG FILE VERSION #
#######################

config_version  1.2

###########################
# SNAPSHOT ROOT DIRECTORY #
###########################

# All snapshots will be stored under this root directory.
#snapshot_root  /var/cache/rsnapshot/
snapshot_root   /home/snapshot/

# If no_create_root is enabled, rsnapshot will not automatically =20
create the
# snapshot_root directory. This is particularly useful if you are =20
backing
# up to removable media, such as a FireWire drive.
#
#no_create_root 1

#################################
# EXTERNAL PROGRAM DEPENDENCIES #
#################################

# LINUX USERS:   Be sure to uncomment "cmd_cp". This gives you extra =20
features.
# EVERYONE ELSE: Leave "cmd_cp" commented out for compatibility.
#
# See the README file or the man page for more details.
#
#cmd_cp         /bin/cp

# uncomment this to use the rm program instead of the built-in perl =20
routine
cmd_rm          /bin/rm

# rsync must be enabled for anything to work.
cmd_rsync       /usr/bin/rsync

# Uncomment this to enable remote ssh backups over rsync.
cmd_ssh         /usr/bin/ssh

# Comment this out to disable syslog support.
cmd_logger      /usr/bin/logger

# Uncomment this to specify a path to "du" for disk usage checks.
cmd_du          /usr/bin/du

#########################################
#           BACKUP INTERVALS            #
# Must be unique and in ascending order #
# i.e. hourly, daily, weekly, etc.      #
#########################################

# The interval names (hourly, daily, ...) are just names and have no =20
influence
# on the length of the interval. The numbers set the number of =20
snapshots to
# keep for each interval (hourly.0, hourly.1, ...).
# The length of the interval is set by the time between two =20
executions of
# rsnapshot <interval name>, this is normally done via cron.
# Feel free to adopt the names, and the sample cron file under /etc/=20
cron.d/rsnapshot
# to your needs. The only requirement is that the intervals must be =20
listed
# in ascending order. To activate just uncomment the entries.

#interval       hourly  6
interval        daily   5
interval        monthly 1
#interval       monthly 6

############################################
#              GLOBAL OPTIONS              #
# All are optional, with sensible defaults #
############################################

# If your version of rsync supports --link-dest, you should enable this.
# This is the best way to support special files (FIFOs, etc) cross-=20
platform.
# The default is 0 (off).
# In Debian GNU cp is available which is superior to link_dest, so it =20=

should be
# commented out (disabled).
#
link_dest       1

# Verbose level, 1 through 5.
# 1     Quiet           Print fatal errors only
# 2     Default         Print errors and warnings only
# 3     Verbose         Show equivalent shell commands being executed
# 4     Extra Verbose   Show extra verbose information
# 5     Debug mode      More than you care to know
#
verbose         3

# Same as "verbose" above, but controls the amount of data sent to the
# logfile, if one is being used. The default is 3.
loglevel        3

# If you enable this, data will be written to the file you specify. The
# amount of data written is controlled by the "loglevel" parameter.
logfile /var/log/rsnapshot.log

# The include and exclude parameters, if enabled, simply get passed =20
directly
# to rsync. If you have multiple include/exclude patterns, put each =20
one on a
# seperate line. Please look up the --include and --exclude options =20
in the
# rsync man page for more details.
#
#include        ???
#include        ???
#exclude        ???
#exclude        ???

# The include_file and exclude_file parameters, if enabled, simply get
# passed directly to rsync. Please look up the --include-from and
# --exclude-from options in the rsync man page for more details.
#
#include_file   /path/to/include/file
#exclude_file   /path/to/exclude/file

# Default rsync args. All rsync commands have at least these options =20
set.
#
#rsync_short_args       -avz
#rsync_long_args        --delete --numeric-ids


# ssh has no args passed by default, but you can specify some here.
#
#ssh_args       -p 22

# If this is enabled, rsync won't span filesystem partitions within a
# backup point. This essentially passes the -x option to rsync.
# The default is 0 (off).
#
#one_fs         0
# If you enable the lockfile, make sure the lockfile directory is
# not world writable. Otherwise anyone can prevent the program from =20
running.
#
lockfile        /var/run/rsnapshot.pid

###############################
### BACKUP POINTS / SCRIPTS ###
###############################

# LOCALHOST
#backup /home/          localhost/home/
#backup /etc/           localhost/etc/
#backup /usr/local/     localhost/usr/local/
#backup /etc/passwd     localhost/etc/passwd
#backup /home/foo/My Documents/         localhost/home/foo/My Documents/
#backup /foo/bar/       localhost/foo/bar/      one_fs=3D1, =20
rsync_short_args=3D-urltvpog
#backup_script          /usr/local/bin/backup_pgsql.sh  localhost/=20
postgres/

# EXAMPLE.COM
# for these backup points you will need ssh installed on the
# local machine as well as on the remote host
#
#backup root@example.com:/home/ example.com/home/
#backup root@example.com:/etc/  example.com/home/
#backup root@tsuna.xyzw.com:/pac/Partage_Libre/  libre/  =20
rsync_short_args=3D-avz
#backup root@tsuna.xyzw.com:/pac/Partage_Prod/   prod/   =20
rsync_short_args=3D-avz
#backup root@tsuna.xyzw.com:/pac/Partage_Art/    art/    =20
rsync_short_args=3D-avz
#backup root@tsuna.xyzw.com:/pac/Partage_Edito/  editors/        =20
rsync_short_args=3D-avz

backup  root@superxserv.xyzw.com:/Volumes/RAID/Partage\ Libre/   =20
superx/libre/   rsync_short_args=3D-avz
backup  root@superxserv.xyzw.com:/Volumes/RAID/Partage\ =20
Artistique/      superx/art/     rsync_short_args=3D-avz
backup  root@superxserv.xyzw.com:/Volumes/RAID/Partage\ Editors/ =20
superx/editors/ rsync_short_args=3D-avz
backup  root@superxserv.xyzw.com:/Volumes/RAID/Partage\ Prod/    =20
superx/prod/    rsync_short_args=3D-avz
backup  root@superxserv.xyzw.com:/Volumes/RAID/Partage\ Devis/   =20
superx/devis/   rsync_short_args=3D-avz

backup  root@newmail.abcd.tw:/etc        newmail/etc/    =20
rsync_short_args=3D-avz
backup  root@newmail.abcd.tw:/var/named  newmail/varnamed/       =20
rsync_short_args=3D-avz
backup  root@newmail.abcd.tw:/usr/local/etc      newmail/=20
localetc/       rsync_short_args=3D-avz

backup  root@tsuna.xyzw.com:/etc/        tsuna/etc/      =20
rsync_short_args=3D-avz
backup  root@tsuna.xyzw.com:/usr/local/etc/      tsuna/localetc/ =20
rsync_short_args=3D-avz
backup  root@tsuna.xyzw.com:/data/       tsuna/data/     =20
rsync_short_args=3D-avz
backup  root@tsuna.xyzw.com:/var/named/  tsuna/  rsync_short_args=3D-avz

backup  root@fiesta.abcd.tw:/etc/        fiesta/ rsync_short_args=3D-avz
backup  root@fiesta.abcd.tw:/usr/local/etc/      fiesta/ =20
rsync_short_args=3D-avz
backup  root@fiesta.abcd.tw:/var/named/  fiesta/ rsync_short_args=3D-avz
backup  root@fiesta.abcd.tw:/www/        fiesta/ rsync_short_args=3D-avz

backup  root@big.big.net:/www/     bigbiz/www/     rsync_short_args=3D-avz=



# CVS.SOURCEFORGE.NET
#backup_script  /usr/local/bin/backup_rsnapshot_cvsroot.sh      =20
cvs.sourceforge.net/

# RSYNC.SAMBA.ORG
#backup rsync://rsync.samba.org/rsyncftp/       rsync.samba.org/=20
rsyncftp/



Le 26 janv. 07 =E0 22:10, Gable Barber a =E9crit :

> Hello all,
> I have been poking around the 'Net a bit looking for an easy to use
> backup solution for our Mac's (1 mini, 1 powerbook, more in the
> future).
>
> Basically there is a server, offsite (FBSD 6.2) with 2 RAID 5 arrays.
> I would like to be able to set the 2 (for now) clients to
> automatically, incrementally backup certain directories, nightly.
> Something encrypted would be nice aswell.
>
> This one looks interesting to me:
>
> http://sourceforge.net/projects/areca/
>
> If anyone has used an open source solution for this , I would
> genuinely appreciate hearing about it.
>
> Thanks in advance -
>
> Gable Barber
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-=20
> unsubscribe@freebsd.org"

________________________________________________
=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=
=BB=A7=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=BB=A7
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF
Gregober ---> PGP ID --> 0x1BA3C2FD
bsd @at@ todoo.biz
________________________________________________
=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=
=BB=A7=AB?=BB=A5=AB?=BB=A7=AB?=BB=A5=AB?=BB=A7
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF

P "Please consider your environmental responsibility before printing =20
this e-mail"





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?E91547B4-AF7B-4BC4-AF1A-9CE2349F2195>