Johannes Schild | 9 May 13:14 2014
Picon
Picon

Question about excluding subdirectories

Hey Guys,
hope i will get some help ;)
I try to config rsnapshot and it works fine, i have only one problem. I would like to exclude some subdirectories on my home.
The directory to exclude is "/home/s0nic/.mozilla/firefox/". I only want /home/s0nic/.mozilla/firefox/a9flepah.default/bookmarkbackups/ in my backup.
 
My exclude looks like this:
Klappi s0nic # cat /root/Scripts/SystemBackup/backup.exclude
+ /.mozilla/
+ /.mozilla/firefox/
+ /.mozilla/firefox/a9flepah.default/
+ /.mozilla/firefox/a9flepah.default/bookmarkbackups/
+ /.mozilla/firefox/a9flepah.default/bookmarkbackups/*
- /.mozilla/firefox/a9flepah.default/*
- /.mozilla/firefox/*
- /.mozilla/*
 
 
If i run:
Klappi s0nic # rsnapshot -t daily
echo 9571 > /var/run/rsnapshot.pid
mv /mnt/Passport/BACKUP/daily.0/ /mnt/Passport/BACKUP/daily.1/
/usr/bin/rsync -a --filter="merge
    /root/Scripts/SystemBackup/backup.exclude" /home/s0nic/
    /mnt/Passport/BACKUP/daily.0/Gentoo-Klappi/
touch /mnt/Passport/BACKUP/daily.0/
 
i got:
Klappi BACKUP # tree -a daily.1/Gentoo-Klappi/.mozilla/firefox/
daily.1/Gentoo-Klappi/.mozilla/firefox/
└── a9flepah.default
    └── bookmarkbackups
        ├── bookmarks-2014-04-25.json
        ├── bookmarks-2014-04-29.json
        ├── bookmarks-2014-04-30.json
        ├── bookmarks-2014-05-01.json
        ├── bookmarks-2014-05-02.json
        ├── bookmarks-2014-05-03.json
        ├── bookmarks-2014-05-04.json
        ├── bookmarks-2014-05-05.json
        ├── bookmarks-2014-05-06.json
        └── bookmarks-2014-05-07.json
2 directories, 10 files
 
Thats perfect. But if i run (thats the default in /etc/rsnapshot.conf (see below for config file)):
Klappi s0nic # rsnapshot -t daily
echo 9571 > /var/run/rsnapshot.pid
mv /mnt/Passport/BACKUP/daily.0/ /mnt/Passport/BACKUP/daily.1/
/usr/bin/rsync -a --filter="merge
    /root/Scripts/SystemBackup/backup.exclude" /home/s0nic/
    /mnt/Passport/BACKUP/daily.0/Gentoo-Klappi/
touch /mnt/Passport/BACKUP/daily.0/

Then i got:
Klappi BACKUP # tree -a daily.0/Gentoo-Klappi/home/s0nic/.mozilla/firefox/
daily.0/Gentoo-Klappi/home/s0nic/.mozilla/firefox/
├── a9flepah.default
│   ├── .parentlock
│   ├── _CACHE_CLEAN_
│   ├── addons.sqlite
│   ├── blocklist.xml
│   ├── bookmarkbackups
│   │   ├── bookmarks-2014-04-25.json
│   │   ├── bookmarks-2014-04-29.json
│   │   ├── bookmarks-2014-04-30.json
│   │   ├── bookmarks-2014-05-01.json
│   │   ├── bookmarks-2014-05-02.json
│   │   ├── bookmarks-2014-05-03.json
│   │   ├── bookmarks-2014-05-04.json
│   │   ├── bookmarks-2014-05-05.json
│   │   ├── bookmarks-2014-05-06.json
│   │   └── bookmarks-2014-05-07.json
│   ├── cert8.db
│   ├── cert_override.txt
│   ├── chromeappsstore.sqlite
│   ├── compatibility.ini
│   ├── content-prefs.sqlite
│   ├── cookies.sqlite
│   ├── cookies.sqlite-shm
│   ├── cookies.sqlite-wal
│   ├── downloads.sqlite
│   ├── extensions.ini
│   ├── extensions.sqlite
│   ├── formhistory.sqlite
│   ├── healthreport
│   ├── healthreport.sqlite
│   ├── healthreport.sqlite-shm
│   ├── healthreport.sqlite-wal
│   ├── indexedDB
│   │   └── chrome
│   │      ├── .metadata
│   │      └── idb
│   │          ├── 2588645841ssegtnti
│   │          └── 2588645841ssegtnti.sqlite
│   ├── key3.db
│   ├── localstore.rdf
│   ├── lock -> 192.168.178.107:+3011
│   ├── marionette.log
│   ├── mimeTypes.rdf
│   ├── mozilla-media-cache
│   ├── permissions.sqlite
│   ├── places.sqlite
│   ├── places.sqlite-shm
│   ├── places.sqlite-wal
│   ├── pluginreg.dat
│   ├── prefs.js
│   ├── safebrowsing
│   │   ├── classifier.hashkey
│   │   ├── goog-malware-shavar.cache
│   │   ├── goog-malware-shavar.pset
│   │   ├── goog-malware-shavar.sbstore
│   │   ├── goog-phish-shavar.cache
│   │   ├── goog-phish-shavar.pset
│   │   ├── goog-phish-shavar.sbstore
│   │   ├── test-malware-simple.cache
│   │   ├── test-malware-simple.pset
│   │   ├── test-malware-simple.sbstore
│   │   ├── test-phish-simple.cache
│   │   ├── test-phish-simple.pset
│   │   └── test-phish-simple.sbstore
│   ├── search-metadata.json
│   ├── search.json
│   ├── search.sqlite
│   ├── secmod.db
│   ├── sessionstore.bak
│   ├── sessionstore.js
│   ├── signons.sqlite
│   ├── times.json
│   ├── urlclassifier.pset
│   ├── urlclassifier3.sqlite
│   ├── urlclassifierkey3.txt
│   ├── weave
│   │   ├── changes
│   │   ├── failed
│   │   └── toFetch
│   ├── webapps
│   │   └── webapps.json
│   ├── webappsstore.sqlite
│   ├── webappsstore.sqlite-shm
│   └── webappsstore.sqlite-wal
└── profiles.ini
14 directories, 71 files
 
Thats too much...
I tried many times and found out, that the parameter --relative creates that stuff... Without this option i got what i want. But if i understand the system correctly i need the parameter --relative right?
 
Klappi BACKUP #  cat /etc/rsnapshot.conf
#################################################
# 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    /mnt/Passport/BACKUP/
# If no_create_root is enabled, rsnapshot will not automatically create the
# snapshot_root directory. This is particularly useful if you are backing
# up to removable media, such as a FireWire or USB drive.
#
no_create_root    1
#################################
# EXTERNAL PROGRAM DEPENDENCIES #
#################################
# LINUX USERS:  Be sure to uncomment "cmd_cp". This gives you extra 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 routine.
#
cmd_rm        /bin/rm
# rsync must be enabled for anything to work. This is the only command that
# must be enabled.
#
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 the path to "du" for disk usage checks.
# If you have an older version of "du", you may also want to check the
# "du_args" parameter below.
#
#cmd_du        /usr/bin/du
# Uncomment this to specify the path to rsnapshot-diff.
#
#cmd_rsnapshot_diff    /usr/local/bin/rsnapshot-diff
# Specify the path to a script (and any optional arguments) to run right
# before rsnapshot syncs files
#
#cmd_preexec    /path/to/preexec/script
# Specify the path to a script (and any optional arguments) to run right
# after rsnapshot syncs files
#
#cmd_postexec    /path/to/postexec/script
#########################################
#          BACKUP INTERVALS            #
# Must be unique and in ascending order #
# i.e. hourly, daily, weekly, etc.      #
#########################################
#interval    hourly    6
interval    daily    7
interval    weekly    4
interval    monthly    3
############################################
#              GLOBAL OPTIONS              #
# All are optional, with sensible defaults #
############################################
# 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      Everything
#
verbose        2
# 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
# If enabled, rsnapshot will write a lockfile to prevent two instances
# from running simultaneously (and messing up the snapshot_root).
# If you enable this, make sure the lockfile directory is not world
# writable. Otherwise anyone can prevent the program from running.
#
lockfile    /var/run/rsnapshot.pid
# Default rsync args. All rsync commands have at least these options set.
#
#=sync_short_args    -a
#rsync_long_args    --delete --numeric-ids --relative --delete-excluded
#rsync_long_args    --filter="merge /root/Scripts/SystemBackup/backupE" --delete --numeric-ids --relative --delete-excluded
rsync_long_args    --filter="merge /root/Scripts/SystemBackup/backup.exclude" --delete --numeric-ids --relative --delete-excluded
# ssh has no args passed by default, but you can specify some here.
#
#ssh_args    -p 22
# Default arguments for the "du" program (for disk space reporting).
# The GNU version of "du" is preferred. See the man page for more details.
# If your version of "du" doesn't support the -h flag, try -k flag instead.
#
#du_args    -csh
# 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
# The include and exclude parameters, if enabled, simply get passed directly
# to rsync. If you have multiple include/exclude patterns, put each one on a
# separate line. Please look up the --include and --exclude options in the
# rsync man page for more details on how to specify file name patterns.
#
#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    /root/Scripts/SystemBackup/backup.include
#exclude_file    /root/Scripts/SystemBackup/backup.exclude
# If your version of rsync supports --link-dest, consider enable this.
# This is the best way to support special files (FIFOs, etc) cross-platform.
# The default is 0 (off).
#
link_dest    1
# When sync_first is enabled, it changes the default behaviour of rsnapshot.
# Normally, when rsnapshot is called with its lowest interval
# (i.e.: "rsnapshot hourly"), it will sync files AND rotate the lowest
# intervals. With sync_first enabled, "rsnapshot sync" handles the file sync,
# and all interval calls simply rotate files. See the man page for more
# details. The default is 0 (off).
#
#sync_first    0
# If enabled, rsnapshot will move the oldest directory for each interval
# to [interval_name].delete, then it will remove the lockfile and delete
# that directory just before it exits. The default is 0 (off).
#
#use_lazy_deletes    0
# Number of rsync re-tries. If you experience any network problems or
# network card issues that tend to cause ssh to crap-out with
# "Corrupted MAC on input" errors, for example, set this to a non-zero
# value to have the rsync operation re-tried
#
#rsync_numtries 0
###############################
### BACKUP POINTS / SCRIPTS ###
###############################
# LOCALHOST
#backup    /boot/        Gentoo-Klappi/
#backup    /etc/        Gentoo-Klappi/
backup    /home/s0nic/            Gentoo-Klappi/
 
Any help or hints would be appreciated

Thanks in advance

Jo
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Dennis Chege | 7 May 15:17 2014
Picon

SCO Unix

I have sco unix V6 running on a hp DL380 G8 with 18GB of disk space so far been utilized. Can rsnapshot take backups that can be restored within 5mins or less?

Regards,

Dennis G
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Christopher Barry | 28 Apr 16:58 2014
Picon

Re: Fw: Unzustellbar: Re: Copying vmdk files

On Mon, 28 Apr 2014 15:14:00 +0200
"Helmut Hullen" <hhullen <at> aktivanet.de> wrote:

>Hallo, Christopher,
>
>Du meintest am 28.04.14:
>
>
>> Is there a way to configure the mailing list to drop these bounces
>> getting spammed to the list?
>
>> -C
>
>> Begin forwarded message:
>
>> Date: Mon, 28 Apr 2014 14:45:05 +0200
>> From: <postmaster <at> dsseals.com>
>> To: <christopher.r.barry <at> gmail.com>
>> Subject: Unzustellbar: Re: [rsnapshot-discuss] Copying vmdk files
>
>No - please tell "postmaster <at> dsseals.com" that he has to reconfigure
>his system. It's a very nasty behaviour to send such "undeliverable"  
>notifications.
>
>Viele Gruesse!
>Helmut
>

Um, actually no, it's not 'nasty', it's the correct behavior of MTAs to
do so. NDRs are a correct response by MTAs for mail that fails for
whatever reason. The list server itself should be configured to
recognize these emails and drop the user from the list that is causing
them, so they do not continue to get propagated to all list members.

These may be helpful:
http://wiki.list.org/display/DOC/Tracking+down+elusive+subscriber+bounces
http://wiki.list.org/display/DOC/So+what+is+this+VERP+stuff

--
Regards,
Christopher Barry

Random geeky fortune:
All most people want is a little more than they'll ever get.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
Christopher Barry | 28 Apr 14:57 2014
Picon

Fw: Unzustellbar: Re: Copying vmdk files


Is there a way to configure the mailing list to drop these bounces
getting spammed to the list?

-C

Begin forwarded message:

Date: Mon, 28 Apr 2014 14:45:05 +0200
From: <postmaster <at> dsseals.com>
To: <christopher.r.barry <at> gmail.com>
Subject: Unzustellbar: Re: [rsnapshot-discuss] Copying vmdk files

Fehler bei der Zustellung der Nachricht an folgende Empfänger oder
Verteilerlisten:

ullmann <at> dsseals.com<mailto:ullmann <at> dsseals.com>
Fehler beim Versuch, diese Nachricht der E-Mail-Adresse des Empfängers
zuzustellen. Microsoft Exchange versucht nicht, diese Nachricht erneut
für Sie zuzustellen. Versuchen Sie, diese Nachricht erneut zu senden,
oder wenden Sie sich mit dem folgenden Diagnosetext an Ihren
Systemadministrator.

Die folgende Organisation hat Ihre Nachricht zurückgewiesen:
wp297.webpack.hosteurope.de.

________________________________
Mit Microsoft Exchange Server 2007 gesendet

Diagnoseinformationen für Administratoren:

Generierender Server: steinhoff.de

ullmann <at> dsseals.com
wp297.webpack.hosteurope.de #550 You are not allowed to use the domain
gmail.com as a sender domain. ##

Ursprüngliche Nachrichtenkopfzeilen:

Received: from exchange-pop3-connector.com (192.168.0.114) by
 W2k8-Ex2k7.steinhoff.de (192.168.0.108) with Microsoft SMTP Server id
 8.3.348.2; Mon, 28 Apr 2014 14:45:03 +0200
Return-Path: <rsnapshot-discuss-bounces <at> lists.sourceforge.net>
Delivery-date: Mon, 28 Apr 2014 14:41:33 +0200
Received: from mi022.mc1.hosteurope.de ([80.237.138.233])       by
 wp297.webpack.hosteurope.de running ExIM with esmtps
 (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)   id 1WeksH-0006FA-At; Mon, 28
Apr 2014 14:41:33 +0200
Received: from lists.sourceforge.net ([216.34.181.88])  by
 mx0.webpack.hosteurope.de (mi022.mc1.hosteurope.de) with esmtps
 (TLSv1:DHE-RSA-AES256-SHA:256) id 1WeksG-000689-FT     for
ullmann <at> dsseals.com; Mon, 28 Apr 2014 14:41:33 +0200
Received: from localhost ([127.0.0.1]
helo=sfs-ml-2.v29.ch3.sourceforge.com) by
sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rsnapshot-discuss-bounces <at> lists.sourceforge.net>)
id 1Wekq4-0000LA-U7; Mon, 28 Apr 2014 12:39:16 +0000 Received: from
sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)        by sfs-ml-2.v29.ch3.sourceforge.com
with esmtp (Exim 4.76)  (envelope-from <christopher.r.barry <at> gmail.com>)
id 1Wekq2-0000Ky-TH     for
rsnapshot-discuss <at> lists.sourceforge.net;       Mon, 28 Apr 2014
12:39:14 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com:
domain of gmail.com designates 209.85.216.47 as permitted sender)
client-ip=209.85.216.47; envelope-from=christopher.r.barry <at> gmail.com;
helo=mail-qa0-f47.google.com; Received: from mail-qa0-f47.google.com
([209.85.216.47])        by sog-mx-4.v43.ch3.sourceforge.com with
esmtps (TLSv1:RC4-SHA:128)       (Exim 4.76) id 1Wekq1-0005Wy-6g    for
rsnapshot-discuss <at> lists.sourceforge.net;    Mon, 28 Apr 2014 12:39:14
+0000 Received: by mail-qa0-f47.google.com with SMTP id
j7so2014658qaq.34     for
<rsnapshot-discuss <at> lists.sourceforge.net>;     Mon, 28 Apr 2014
05:39:07 -0700 (PDT) X-Received: by 10.140.19.212 with SMTP id
78mr31281599qgh.84.1398688747624; Mon, 28 Apr 2014 05:39:07 -0700 (PDT)
Received: from monolith.infinux.org
        (pool-108-52-115-204.phlapa.fios.verizon.net. [108.52.115.204])
by mx.google.com with ESMTPSA id
l3sm14208953qao.33.2014.04.28.05.39.06   for
<rsnapshot-discuss <at> lists.sourceforge.net>      (version=SSLv3
cipher=RC4-SHA bits=128/128); Mon, 28 Apr 2014 05:39:07 -0700 (PDT)
Date: Mon, 28 Apr 2014 08:41:01 -0400 From: Christopher Barry
<christopher.r.barry <at> gmail.com> To:
<rsnapshot-discuss <at> lists.sourceforge.net> Message-ID:
<20140428084101.34a41c99 <at> monolith.infinux.org> In-Reply-To:
<c5b1803aa8f541e388fefb60c8fa18c9 <at> CO2PR04MB684.namprd04.prod.outlook.com>
References: <53511695.1000708 <at> collisiondetection.biz>
<c5b1803aa8f541e388fefb60c8fa18c9 <at> CO2PR04MB684.namprd04.prod.outlook.com>
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu)
MIME-Version: 1.0 X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
        See http://spamassassin.org/tag/ for more details.
        -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender
for sender-domain
        0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
provider (christopher.r.barry[at]gmail.com)
        -0.0 SPF_PASS               SPF: sender matches SPF record
        -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
        author's domain
        0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
        not necessarily valid
        -0.1 DKIM_VALID Message has at least one valid DKIM or DK
signature X-Headers-End: 1Wekq1-0005Wy-6g
Subject: Re: [rsnapshot-discuss] Copying vmdk files
X-BeenThere: rsnapshot-discuss <at> lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: rsnapshot discussion list
<rsnapshot-discuss.lists.sourceforge.net> List-Unsubscribe:
<https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss>,
<mailto:rsnapshot-discuss-request <at> lists.sourceforge.net?subject=unsubscribe>
List-Archive:
<http://sourceforge.net/mailarchive/forum.php?forum_name=rsnapshot-discuss>
List-Post: <mailto:rsnapshot-discuss <at> lists.sourceforge.net> List-Help:
<mailto:rsnapshot-discuss-request <at> lists.sourceforge.net?subject=help>
List-Subscribe:
<https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss>,
<mailto:rsnapshot-discuss-request <at> lists.sourceforge.net?subject=subscribe>
Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding:
7bit Errors-To: rsnapshot-discuss-bounces <at> lists.sourceforge.net
X-HE-Virus-Scanned: Yes X-HE-Spam-Level: -- X-HE-Spam-Score: -2.5
X-HE-Spam-Report: Content analysis details:   (-2.5 points)
  pts rule name              description
 ---- ----------------------
-------------------------------------------------- -5.0
RCVD_IN_DNSWL_HI       RBL: Sender listed at http://www.dnswl.org/,
high trust [216.34.181.88 listed in list.dnswl.org]
  2.5 RCVD_IN_SORBS_HTTP     RBL: SORBS: sender is open HTTP proxy
server [108.52.115.204 listed in dnsbl.sorbs.net]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser
mail provider (christopher.r.barry[at]gmail.com)
  0.0 DKIM_ADSP_CUSTOM_MED   No valid author signature, adsp_override is
                             CUSTOM_MED
X-HE-SPF: PASSED
Envelope-to: ullmann <at> dsseals.com

Fehler bei der Zustellung der Nachricht an folgende Empfänger oder Verteilerlisten:

ullmann <at> dsseals.com
Fehler beim Versuch, diese Nachricht der E-Mail-Adresse des Empfängers zuzustellen. Microsoft Exchange versucht nicht, diese Nachricht erneut für Sie zuzustellen. Versuchen Sie, diese Nachricht erneut zu senden, oder wenden Sie sich mit dem folgenden Diagnosetext an Ihren Systemadministrator.

Die folgende Organisation hat Ihre Nachricht zurückgewiesen: wp297.webpack.hosteurope.de.

Mit Microsoft Exchange Server 2007 gesendet





Diagnoseinformationen für Administratoren:

Generierender Server: steinhoff.de

ullmann <at> dsseals.com
wp297.webpack.hosteurope.de #550 You are not allowed to use the domain gmail.com as a sender domain. ##

Ursprüngliche Nachrichtenkopfzeilen:

Received: from exchange-pop3-connector.com (192.168.0.114) by W2k8-Ex2k7.steinhoff.de (192.168.0.108) with Microsoft SMTP Server id 8.3.348.2; Mon, 28 Apr 2014 14:45:03 +0200 Return-Path: <rsnapshot-discuss-bounces <at> lists.sourceforge.net> Delivery-date: Mon, 28 Apr 2014 14:41:33 +0200 Received: from mi022.mc1.hosteurope.de ([80.237.138.233]) by wp297.webpack.hosteurope.de running ExIM with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1WeksH-0006FA-At; Mon, 28 Apr 2014 14:41:33 +0200 Received: from lists.sourceforge.net ([216.34.181.88]) by mx0.webpack.hosteurope.de (mi022.mc1.hosteurope.de) with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) id 1WeksG-000689-FT for ullmann <at> dsseals.com; Mon, 28 Apr 2014 14:41:33 +0200 Received: from localhost ([127.0.0.1] helo=sfs-ml-2.v29.ch3.sourceforge.com) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <rsnapshot-discuss-bounces <at> lists.sourceforge.net>) id 1Wekq4-0000LA-U7; Mon, 28 Apr 2014 12:39:16 +0000 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <christopher.r.barry <at> gmail.com>) id 1Wekq2-0000Ky-TH for rsnapshot-discuss <at> lists.sourceforge.net; Mon, 28 Apr 2014 12:39:14 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.47 as permitted sender) client-ip=209.85.216.47; envelope-from=christopher.r.barry <at> gmail.com; helo=mail-qa0-f47.google.com; Received: from mail-qa0-f47.google.com ([209.85.216.47]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wekq1-0005Wy-6g for rsnapshot-discuss <at> lists.sourceforge.net; Mon, 28 Apr 2014 12:39:14 +0000 Received: by mail-qa0-f47.google.com with SMTP id j7so2014658qaq.34 for <rsnapshot-discuss <at> lists.sourceforge.net>; Mon, 28 Apr 2014 05:39:07 -0700 (PDT) X-Received: by 10.140.19.212 with SMTP id 78mr31281599qgh.84.1398688747624; Mon, 28 Apr 2014 05:39:07 -0700 (PDT) Received: from monolith.infinux.org (pool-108-52-115-204.phlapa.fios.verizon.net. [108.52.115.204]) by mx.google.com with ESMTPSA id l3sm14208953qao.33.2014.04.28.05.39.06 for <rsnapshot-discuss <at> lists.sourceforge.net> (version=SSLv3 cipher=RC4-SHA bits=128/128); Mon, 28 Apr 2014 05:39:07 -0700 (PDT) Date: Mon, 28 Apr 2014 08:41:01 -0400 From: Christopher Barry <christopher.r.barry <at> gmail.com> To: <rsnapshot-discuss <at> lists.sourceforge.net> Message-ID: <20140428084101.34a41c99 <at> monolith.infinux.org> In-Reply-To: <c5b1803aa8f541e388fefb60c8fa18c9 <at> CO2PR04MB684.namprd04.prod.outlook.com> References: <53511695.1000708 <at> collisiondetection.biz> <c5b1803aa8f541e388fefb60c8fa18c9 <at> CO2PR04MB684.namprd04.prod.outlook.com> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (christopher.r.barry[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wekq1-0005Wy-6g Subject: Re: [rsnapshot-discuss] Copying vmdk files X-BeenThere: rsnapshot-discuss <at> lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: rsnapshot discussion list <rsnapshot-discuss.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss>, <mailto:rsnapshot-discuss-request <at> lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=rsnapshot-discuss> List-Post: <mailto:rsnapshot-discuss <at> lists.sourceforge.net> List-Help: <mailto:rsnapshot-discuss-request <at> lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss>, <mailto:rsnapshot-discuss-request <at> lists.sourceforge.net?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rsnapshot-discuss-bounces <at> lists.sourceforge.net X-HE-Virus-Scanned: Yes X-HE-Spam-Level: -- X-HE-Spam-Score: -2.5 X-HE-Spam-Report: Content analysis details: (-2.5 points) pts rule name description ---- ---------------------- -------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high trust [216.34.181.88 listed in list.dnswl.org] 2.5 RCVD_IN_SORBS_HTTP RBL: SORBS: sender is open HTTP proxy server [108.52.115.204 listed in dnsbl.sorbs.net] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (christopher.r.barry[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED X-HE-SPF: PASSED Envelope-to: ullmann <at> dsseals.com
Attachment: message/delivery-status, 343 bytes
Picon
From: Christopher Barry <christopher.r.barry <at> gmail.com>
Subject: Re: [rsnapshot-discuss] Copying vmdk files
Date: 2014-04-28 12:41:01 GMT
On Mon, 28 Apr 2014 11:39:46 +0000
"Edward Ned Harvey (rsnapshot)" <rsnapshot <at> nedharvey.com> wrote:

>> From: Daniel [mailto:info <at> collisiondetection.biz]
>> 
>> I would like to copy my virtualbox VM folder. When I check the the
>> backup I see everything but the vmdk file.
>> 
>> Does rsnaphot support copying this file format?
>
>The best way to send vmdk and similar files, is to use zfs (or maybe
>btrfs?) and snapshot at the block level, and send incremental blocks.
>
>I haven't used zfs on linux in a while, but it's supposedly stable and
>useful now.  http://zfsonlinux.org/ 
>

Is there a reason LVM-based snapshots would not work in this case? LVM
is quite stable and performant, and a bit less esoteric than the above
file systems.

--
Regards,
Christopher Barry

Random geeky fortune:
Hate is like acid.  It can damage the vessel in which it is stored as
well as destroy the object on which it is poured.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Dirk Engelmann | 24 Apr 10:05 2014
Picon

rsnapshot hourly doesnt start from /etc/cron.d/rsnapshot entry

Hello , a couple of weeks ago i started a thread about(apparent) Problems
copying open files.
The thread was named:"backup open files from mailserver Problem".
After trying different approaches to solving this issue, i am faced with a
new Problem.
I found that rsnapshot hourly doesnt do anything when started from
/etc/cron.d/rsnapshot,(not even creating the logfile
'/var/log/backup/'$(date +%F_%T)'rsyncd.log' ) but behaves nicely when i
start it from the commandline, as root. The odd thing is that all the
other Jobs in
/etc/cron.d/rsnapshot (e.g.rsnapshot daily) do work, as expected.

Any ideas??
Dirk

This is the logfile /var/log/backup/rsnapshot.log
+++++++++++++++++++++++++++++++
[22/Apr/2014:18:19:49] require Lchown
[22/Apr/2014:18:19:49] Lchown module loaded successfully
[22/Apr/2014:18:19:49] /usr/bin/rsnapshot hourly: started
[22/Apr/2014:18:19:49] Setting locale to POSIX "C"
[22/Apr/2014:18:19:49] echo 3944 > /var/run/rsnapshot.pid
[22/Apr/2014:18:19:49] rm -rf /media/backup/hourly.3/
[22/Apr/2014:18:37:06] mv /media/backup/hourly.2/ /media/backup/hourly.3/
[22/Apr/2014:18:37:07] mv /media/backup/hourly.1/ /media/backup/hourly.2/
[22/Apr/2014:18:37:07] /bin/cp -al /media/backup/hourly.0
/media/backup/hourly.1
[22/Apr/2014:19:07:37] mkdir -m 0755 -p /media/backup/tmp/
[22/Apr/2014:19:07:37] cd /media/backup/tmp/
[22/Apr/2014:19:07:37] /bin/date "+ Start Backup des lokalen /etc um %c"
[22/Apr/2014:19:07:37] cd /media/backup/
[22/Apr/2014:19:07:37] sync_if_different("/media/backup/tmp/",
"/media/backup/hourly.0/unused1")
[22/Apr/2014:19:07:37] sync_cp_src_dest("/media/backup/tmp",
"/media/backup/hourly.0/unused1")
[22/Apr/2014:19:07:37] sync_rm_dest("/media/backup/tmp",
"/media/backup/hourly.0/unused1")
[22/Apr/2014:19:07:37] rm -rf /media/backup/tmp/
[22/Apr/2014:19:07:37] /usr/bin/rsync -av
--log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log'
--exclude-from=/etc/rsnapshot.excludes /etc/ /media/backup/hourly.0/localh
ost/etc/
[22/Apr/2014:19:07:39] rsync succeeded
[22/Apr/2014:19:07:39] mkdir -m 0755 -p /media/backup/tmp/
[22/Apr/2014:19:07:39] cd /media/backup/tmp/
[22/Apr/2014:19:07:39] /bin/date "+ Start Backup von banal um %c"
[22/Apr/2014:19:07:39] cd /media/backup/
[22/Apr/2014:19:07:39] sync_if_different("/media/backup/tmp/",
"/media/backup/hourly.0/unused2")
[22/Apr/2014:19:07:39] sync_cp_src_dest("/media/backup/tmp",
"/media/backup/hourly.0/unused2")
[22/Apr/2014:19:07:39] sync_rm_dest("/media/backup/tmp",
"/media/backup/hourly.0/unused2")
[22/Apr/2014:19:07:39] rm -rf /media/backup/tmp/
[22/Apr/2014:19:07:40] /usr/bin/rsync -av
--log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log' --exclude=mtab
--exclude=core --rsh=/usr/bin/ssh root <at> 10.9.1.1:/etc/ /medi
a/backup/hourly.0/banal/etc/
[22/Apr/2014:19:07:45] rsync succeeded
[22/Apr/2014:19:07:45] /usr/bin/rsync -av
--log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log'
--exclude-from=/etc/rsnapshot.excludes --rsh=/usr/bin/ssh root <at> 10.9.1.1:/w
ww/ /media/backup/hourly.0/banal/www/
[22/Apr/2014:19:10:19] rsync succeeded
[22/Apr/2014:19:10:19] /usr/bin/rsync -av
--log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log'
--exclude-from=/etc/rsnapshot.excludes --rsh=/usr/bin/ssh root <at> 10.9.1.1:/s
vn/ /media/backup/hourly.0/banal/svn/
[22/Apr/2014:19:10:22] rsync succeeded
[22/Apr/2014:19:10:22] /usr/bin/rsync -av
--log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log'
--exclude-from=/etc/rsnapshot.excludes --rsh=/usr/bin/ssh root <at> 10.9.1.1:/h
ome/ /media/backup/hourly.0/banal/home/
[22/Apr/2014:19:20:48] rsync succeeded
[22/Apr/2014:19:20:48] mkdir -m 0755 -p /media/backup/tmp/
[22/Apr/2014:19:20:48] cd /media/backup/tmp/
[22/Apr/2014:19:20:48] /bin/date "+ Ende backup von banal um %c"
[22/Apr/2014:19:20:48] cd /media/backup/
[22/Apr/2014:19:20:48] sync_if_different("/media/backup/tmp/",
"/media/backup/hourly.0/unused9")
[22/Apr/2014:19:20:48] sync_cp_src_dest("/media/backup/tmp",
"/media/backup/hourly.0/unused9")
[22/Apr/2014:19:20:48] sync_rm_dest("/media/backup/tmp",
"/media/backup/hourly.0/unused9")
[22/Apr/2014:19:20:48] rm -rf /media/backup/tmp/
[22/Apr/2014:19:20:48] touch /media/backup/hourly.0/
[22/Apr/2014:19:20:49] No directory to delete: /media/backup/_delete.3944
[22/Apr/2014:19:20:49] rm -f /var/run/rsnapshot.pid
[22/Apr/2014:19:20:49] /usr/bin/rsnapshot hourly: completed successfully
+++++++++++++++++++++++++++++++

This is my /etc/cron.d/rsnapshot
+++++++++++++++++++++++++++++++

# This is a sample cron file for rsnapshot.
# The values used correspond to the examples in /etc/rsnapshot.conf.
# There you can also set the backup points and many other things.
#
# To activate this cron file you have to uncomment the lines below.
# Feel free to adapt it to your needs.

#m      h       D M W           User    Befehl
#-----------------------------------------------------------------
0       0-18/4  * * *           root    /usr/bin/rsnapshot hourly
30      0       * * *           root    /usr/bin/rsnapshot daily
0       1       * * 1           root    /usr/bin/rsnapshot weekly
0       2       1 * *           root    /usr/bin/rsnapshot monthly

+++++++++++++++++++++++++++++++

This is my rsnapshot.conf
+++++++++++++++++++++++++++++++

#################################################
# 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   /media/backup/


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

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

# LINUX USERS:   Be sure to uncomment "cmd_cp". This gives you extra
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 routine.
#
cmd_rm          /bin/rm

# rsync must be enabled for anything to work. This is the only command that
# must be enabled.
#
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 the path to "du" for disk usage checks. # If
you have an older version of "du", you may also want to check the #
"du_args" parameter below.
#
cmd_du          /usr/bin/du

# Uncomment this to specify the path to rsnapshot-diff.
#
cmd_rsnapshot_diff      /usr/bin/rsnapshot-diff

# Specify the path to a script (and any optional arguments) to run right #
before rsnapshot syncs files
#
#cmd_preexec    /path/to/preexec/script

# Specify the path to a script (and any optional arguments) to run right #
after rsnapshot syncs files
#
#cmd_postexec   /path/to/postexec/script

# Paths to lvcreate, lvremove, mount and umount commands, for use with #
Linux LVMs.
#
#linux_lvm_cmd_lvcreate /sbin/lvcreate
#linux_lvm_cmd_lvremove /sbin/lvremove
#linux_lvm_cmd_mount    /bin/mount
#linux_lvm_cmd_umount   /bin/umount

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

retain  hourly  4
retain  daily   7
retain  weekly  4
retain  monthly 12

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

# 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      Everything
#
verbose 5

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

# 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/backup/rsnapshot.log

# If enabled, rsnapshot will write a lockfile to prevent two instances #
from running simultaneously (and messing up the snapshot_root).
# If you enable this, make sure the lockfile directory is not world #
writable. Otherwise anyone can prevent the program from running. #
lockfile        /var/run/rsnapshot.pid

# By default, rsnapshot check lockfile, check if PID is running
# and if not, consider lockfile as stale, then start
# Enabling this stop rsnapshot if PID in lockfile is not running
#
#stop_on_stale_lockfile         0

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

# Default arguments for the "du" program (for disk space reporting). # The
GNU version of "du" is preferred. See the man page for more details. # If
your version of "du" doesn't support the -h flag, try -k flag instead.
#
#du_args        -csh

# 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

# The include and exclude parameters, if enabled, simply get passed directly
# to rsync. If you have multiple include/exclude patterns, put each one on a
# separate line. Please look up the --include and --exclude options in the
# rsync man page for more details on how to specify file name patterns. #
#include        ???
#                        Alle User mit momentan über 10 G Platzbelegung # 
                      gut zu sehen mit ncdu
#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    /etc/rsnapshot.excludes

# Default rsync args. All rsync commands have at least these options set. #
#rsync_short_args       -a
rsync_long_args --log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log'
--delete        --numeric-ids   --relative      --delete-excluded

# If your version of rsync supports --link-dest, consider enable this. #
This is the best way to support special files (FIFOs, etc)
cross-platform.
# The default is 0 (off).
#
#link_dest              0

# When sync_first is enabled, it changes the default behaviour of
rsnapshot.
# Normally, when rsnapshot is called with its lowest interval
# (i.e.: "rsnapshot hourly"), it will sync files AND rotate the lowest #
intervals. With sync_first enabled, "rsnapshot sync" handles the file
sync,
# and all interval calls simply rotate files. See the man page for more #
details. The default is 0 (off).
#
#sync_first             0

# If enabled, rsnapshot will move the oldest directory for each interval #
to [interval_name].delete, then it will remove the lockfile and delete #
that directory just before it exits. The default is 0 (off).
#
#use_lazy_deletes       0

# Number of rsync re-tries. If you experience any network problems or #
network card issues that tend to cause ssh to crap-out with
# "Corrupted MAC on input" errors, for example, set this to a non-zero #
value to have the rsync operation re-tried
#rsync_numtries         0

# LVM parameters. Used to backup with creating lvm snapshot before backup
# and removing it after. This should ensure consistency of data in some
special
# cases
#
# LVM snapshot(s) size (lvcreate --size option).
#
#linux_lvm_snapshotsize 100M

# Name to be used when creating the LVM logical volume snapshot(s). #
#linux_lvm_snapshotname         rsnapshot

# Path to the LVM Volume Groups.
#
#linux_lvm_vgpath       /dev

# Mount point to use to temporarily mount the snapshot(s).
#
#linux_lvm_mountpath    /path/to/mount/lvm/snapshot/during/backup

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

backup_script   /bin/date "+ Start Backup des lokalen /etc um %c"
unused1
# LOCALHOST
backup          /etc/           localhost/etc/

backup_script   /bin/date "+ Start Backup von banal  um %c"     unused2 #
banal
backup          root <at> ...:/etc/     banal/etc/
exclude=mtab,exclude=core
backup          root <at> ...:/www/     banal/www/
backup          root <at> ...:/svn/     banal/svn/
backup          root <at> ...:/home/    banal/home/
backup_script   /bin/date "+ Ende backup von banal um %c"
unused9

+++++++++++++++++++++++++++++++

Gruß vom
Dirk

A sufficient amount of googling is
undistinguishable from real knowledge.

Dirk Engelmann             dirk <at> trillke.net
M:+49 (0)171/3287042  shivahoj <at> gmail.com.de
Steinbergstr. 42  D31139 Hildesheim Germany
ICBM Address:52°08'33.36''N 009°56'02.64''E

------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
Daniel | 18 Apr 14:12 2014

Copying vmdk files

Hi,

I would like to copy my virtualbox VM folder. When I check the the 
backup I see everything but the vmdk file.

Does rsnaphot support copying this file format?

Thanks for the help,

Dan

------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
Tapani Tarvainen | 12 Apr 14:33 2014
Picon

Re: backup open files from mailserver problem'

On Sat, Apr 12, 2014 at 01:01:00PM +0200, Helmut Hullen (hhullen <at> aktivanet.de) wrote:

> Hallo, Dirk,
> 
> Du meintest am 12.04.14:

> > The backups are written to a mirrored(RAID1) set of 2 internal
> > 3.5"SATA Disks, 2TB each, about half a year old.
> 
> > So i assume the disks are not faulty,
> 
> Maybe you're wrong ...
> Even new disks may be faulty.

Indeed. The next thing I'd do is run selftest on the disks
(install smartmontools and do smartctl -t long /dev/sdwhatever
for each disk).

> Another possible problem: weak power supply.

Yes, bad PSUs cause all kinds of hard-to-trace problems.
It is somewhat unlikely here though because the error always
occurs on the same directory, if I understood correctly.

--

-- 
Tapani Tarvainen

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
Patrick O'Callaghan | 10 Apr 12:03 2014
Picon

NFS vs Rsync revisited

I've been using Rsnapshot for a few years on my home network but
haven't participated in this list until now, so please bear with me.

I recently changed computers and decided to take a new look at how my
backups were configured. My hardware setup is:

* Client: PC with an i7 cpu, 16GB of RAM, a 120GB SSD and a 1TB
hard drive, running Fedora 20.

* Server: Iomega ix2-200 NAS with two 1TB drives configured as
RAID1, 512MB of RAM and an Arm cpu, i.e. fairly slow. It runs Debian
Edge as far as I can tell.

* Network: Gigabit Ethernet, with essentially no other loading.

My original setup used rsnapshot running on the PC with the backup to
the server over NFS. This worked for years (if it's not broken, don't
fix it ...). However some reading on the list archives and elsewhere
persuaded me that this wasn't the recommended method, so I decided to
run rsnapshot on the server and copy from the client via rsync. I
installed rsnapshot version 1.3.1 on the NAS, as it isn't supported by
Iomega.

Somewhat to my surprise, I found that the rsync setup was substantially
*slower* than the NFS one. For example, a 100GB rsnaphot sync takes
around 8 minutes over NFS but around 85 minutes using rsync. IOW *ten
times slower*. I repeat that this is on exactly the same hardware,
network and data.

As this goes against the received wisdom, I wondered if anyone can show
any light on the matter. For example, could it be a consequence of the
server cpu not being able to cope with the encrypted SSH session fast
enough to keep up? Can SSH encryption be turned off (both machines are
on a LAN with no entry except through a firewall, so the encryption is
really redundant here)?

I'm happy to post both config files and rsnapshot logs if anyone's
interested. It could be that I've done something stupid; it wouldn't be
the first time.

poc

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
Sam Pinkus | 9 Apr 13:17 2014

What is the official upstream source.

Hi,

I am wondering what the official upstream source is for rsnapshot. Is it
on github?

Thanks,

Sam.

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
Dirk Engelmann | 8 Apr 18:48 2014
Picon

backup open files from mailserver problem

Hello to all of You,
i do backups of our local mailserver(circa 50 active users plus maybe
100 inactive "Karteileichen"), to a backup server in another building.
Both machines are headless ubuntu servers.  Since 8-10 weeks i often
encounter the following problem:(this is the error mail, that rsnapshot
emails me)

echo 23194 > /var/run/rsnapshot.pid
/bin/rm -rf /media/backup/hourly.3/
/bin/rm: cannot remove
`/media/backup/hourly.3/banal/home/wanja/Maildir/cur': Directory not empty
/bin/rm: cannot remove
`/media/backup/hourly.3/banal/home/wanja/Maildir/.ablage+listen.reflect/cur':
Directory not empty
----------------------------------------------------------------------------
rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot hourly
----------------------------------------------------------------------------
ERROR: Warning! /bin/rm failed.
ERROR: Error! rm_rf("/media/backup/hourly.3/")
rm -f /var/run/rsnapshot.pid

another example complaining about a file in the users trash(maybe the
same reason?):

echo 29026 > /var/run/rsnapshot.pid
/bin/rm -rf /media/backup/hourly.3/
mv /media/backup/hourly.2/ /media/backup/hourly.3/
mv /media/backup/hourly.1/ /media/backup/hourly.2/
/bin/cp -al /media/backup/hourly.0 /media/backup/hourly.1
/bin/cp: cannot stat
`/media/backup/hourly.0/banal/home/macky/Maildir/.Trash/cur/1307642682.E407673P3009.banal,W=8616,S=8358:2,RS':
No such file or directory
----------------------------------------------------------------------------
rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot hourly
----------------------------------------------------------------------------
ERROR: /bin/cp -al /media/backup/hourly.0 /media/backup/hourly.1 failed
(result 256, exit status 1).  Perhaps your cp does not support -al options?
ERROR: Error! cp_al("/media/backup/hourly.0/", "/media/backup/hourly.1/")
rm -f /var/run/rsnapshot.pid

Upon investigation, this particular file does not exit in the users
maildir, nor in the backup.
I think it is a problem with open files since these errors occur with
all users, but ONLY  in the /home/$USER/Maildir/cur directory.
Strangely , these errors (kind of) heal themselves after a few days,
and i get mails about succesful backup runs.
But i starting to lose faith in the correct operation of rsnapshot
altogether.

Any Ideas?

Dirk

This is my rsnapshot.conf:

#################################################
# 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   /media/backup/


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

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

# LINUX USERS:   Be sure to uncomment "cmd_cp". This gives you extra
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 routine.
#
cmd_rm          /bin/rm

# rsync must be enabled for anything to work. This is the only command that
# must be enabled.
#
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 the path to "du" for disk usage checks.
# If you have an older version of "du", you may also want to check the
# "du_args" parameter below.
#
cmd_du          /usr/bin/du

# Uncomment this to specify the path to rsnapshot-diff.
#
cmd_rsnapshot_diff      /usr/bin/rsnapshot-diff

# Specify the path to a script (and any optional arguments) to run right
# before rsnapshot syncs files
#
#cmd_preexec    /path/to/preexec/script

# Specify the path to a script (and any optional arguments) to run right
# after rsnapshot syncs files
#
#cmd_postexec   /path/to/postexec/script

# Paths to lvcreate, lvremove, mount and umount commands, for use with
# Linux LVMs.
#
#linux_lvm_cmd_lvcreate /sbin/lvcreate
#linux_lvm_cmd_lvremove /sbin/lvremove
#linux_lvm_cmd_mount    /bin/mount
#linux_lvm_cmd_umount   /bin/umount

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

retain  hourly  4
retain  daily   7
retain  weekly  4
retain  monthly 12

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

# 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      Everything
#
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/backup/rsnapshot.log

# If enabled, rsnapshot will write a lockfile to prevent two instances
# from running simultaneously (and messing up the snapshot_root).
# If you enable this, make sure the lockfile directory is not world
# writable. Otherwise anyone can prevent the program from running.
#
lockfile        /var/run/rsnapshot.pid

# By default, rsnapshot check lockfile, check if PID is running
# and if not, consider lockfile as stale, then start
# Enabling this stop rsnapshot if PID in lockfile is not running
#
#stop_on_stale_lockfile         0

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

# Default arguments for the "du" program (for disk space reporting).
# The GNU version of "du" is preferred. See the man page for more details.
# If your version of "du" doesn't support the -h flag, try -k flag instead.
#
#du_args        -csh

# 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

# The include and exclude parameters, if enabled, simply get passed directly
# to rsync. If you have multiple include/exclude patterns, put each one on a
# separate line. Please look up the --include and --exclude options in the
# rsync man page for more details on how to specify file name patterns.
#
#include        ???
#                        Alle User mit momentan über 10 G Platzbelegung
#                        gut zu sehen mit ncdu
#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    /etc/rsnapshot.excludes

# Default rsync args. All rsync commands have at least these options set.
#
#rsync_short_args       -a
rsync_long_args --log-file='/var/log/backup/'$(date +%F_%T)'rsyncd.log'
--delete        --numeric-ids   --relative      --delete-excluded

# If your version of rsync supports --link-dest, consider enable this.
# This is the best way to support special files (FIFOs, etc) cross-platform.
# The default is 0 (off).
#
#link_dest              0

# When sync_first is enabled, it changes the default behaviour of rsnapshot.
# Normally, when rsnapshot is called with its lowest interval
# (i.e.: "rsnapshot hourly"), it will sync files AND rotate the lowest
# intervals. With sync_first enabled, "rsnapshot sync" handles the file
sync,
# and all interval calls simply rotate files. See the man page for more
# details. The default is 0 (off).
#
#sync_first             0

# If enabled, rsnapshot will move the oldest directory for each interval
# to [interval_name].delete, then it will remove the lockfile and delete
# that directory just before it exits. The default is 0 (off).
#
#use_lazy_deletes       0

# Number of rsync re-tries. If you experience any network problems or
# network card issues that tend to cause ssh to crap-out with
# "Corrupted MAC on input" errors, for example, set this to a non-zero
# value to have the rsync operation re-tried
#rsync_numtries         0

# LVM parameters. Used to backup with creating lvm snapshot before backup
# and removing it after. This should ensure consistency of data in some
special
# cases
#
# LVM snapshot(s) size (lvcreate --size option).
#
#linux_lvm_snapshotsize 100M

# Name to be used when creating the LVM logical volume snapshot(s).
#
#linux_lvm_snapshotname         rsnapshot

# Path to the LVM Volume Groups.
#
#linux_lvm_vgpath       /dev

# Mount point to use to temporarily mount the snapshot(s).
#
#linux_lvm_mountpath    /path/to/mount/lvm/snapshot/during/backup

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

backup_script   /bin/date "+ Start Backup des lokalen /etc um %c"
unused1
# LOCALHOST
backup          /etc/           localhost/etc/

backup_script   /bin/date "+ Start Backup von banal  um %c"     unused2
# banal
backup          root <at> 10.9.1.1:/etc/     banal/etc/
exclude=mtab,exclude=core
backup          root <at> 10.9.1.1:/www/     banal/www/
backup          root <at> 10.9.1.1:/svn/     banal/svn/
backup          root <at> 10.9.1.1:/home/    banal/home/
backup_script   /bin/date "+ Ende backup von banal um %c"
unused9

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Bjørn T Johansen | 8 Apr 11:26 2014
Picon

Re: /bin/cp: cannot create hard link File exists

On 8 April 2014 at 11:02:53 , Helmut Hullen (hhullen <at> aktivanet.de) wrote:
Hallo, Bj?rn, 

Du meintest am 08.04.14: 

> Shouldn?t be anything left other that rsnapshot itself leaves?. No 
> programs other rsnapshot writes to these directories?. Here is the 
> complete log?: 


> [08/Apr/2014:05:15:01] /usr/bin/rsnapshot daily: started 

[...] 

> [08/Apr/2014:05:38:09] mv 
> /mnt/nas/pennywise2/snapshots/daily.1/ /mnt/nas/pennywise2/snapshots 
> /daily.2/ 

There I miss "mv .../daily.0 .../daily.1" 

Was this renaming ever successful? 

As far as I can tell yes… I have a daily.0 directory and the files there seem to be what I expect….



What tells 

df 

about the free place on the target disk? 

I have no space problem, the NAS disk has 1.3TB free space..




What kind of filesystem is used from the backups? 

Do you mean the source or destination? The nas disk is mounted as NFS and the source is Linux ext4 FS...



What tells 

df -T 

about the type of net filesystem with which the NAS is connected to the 
machine where "rsnapshot" runs? 


It shows that I am unsing NFS….



Viele Gruesse! 
Helmut 


------------------------------------------------------------------------------ 
Put Bad Developers to Shame 
Dominate Development with Jenkins Continuous Integration 
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud. 
http://p.sf.net/sfu/13600_Cloudbees 
_______________________________________________ 
rsnapshot-discuss mailing list 
rsnapshot-discuss <at> lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss 




------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Gmane