| View previous topic :: View next topic |
| Author |
Message |
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
 Posted: Sat Jan 10, 2015 10:36 pm Post subject: [solved] Rsnapshot : only daily backup working |
 |
|
Hi,
I am using rsnapshot to backup my system. It is partially working : it keeps 4 hourly snapshot as expected, but no daily, nor weekly snapshots.
Some information follows :
| Code: | | more /etc/rsnapshot.conf |
| Quote: | #################################################
# 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/sauvegarde/
# 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 /root/montage-partition-sauvegarde
# Specify the path to a script (and any optional arguments) to run right
# after rsnapshot syncs files
#
cmd_postexec /root/demontage-partition-sauvegarde
#########################################
# BACKUP INTERVALS #
# Must be unique and in ascending order #
# i.e. hourly, daily, weekly, etc. #
#########################################
interval hourly 4
interval daily 3
interval weekly 2
#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.
#
#rsync_short_args -a
#rsync_long_args --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 /path/to/include/file
exclude_file /home/pierre/.exclusion_rsync.txt
# 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
###############################
### BACKUP POINTS / SCRIPTS ###
###############################
# LOCALHOST
backup /home/pierre/ localhost/
backup /etc/ localhost/
backup /usr/local/ localhost/
#backup /var/log/rsnapshot localhost/
#backup /etc/passwd localhost/
#backup /home/foo/My Documents/ localhost/
#backup /foo/bar/ localhost/ one_fs=1, rsync_short_args=-urltvpog
#backup_script /usr/local/bin/backup_pgsql.sh localhost/postgres/
# EXAMPLE.COM
#backup_script /bin/date "+ backup of example.com started at %c" unused1
#backup root@example.com:/home/ example.com/ +rsync_long_args=--bwlimit=16,exclude=core
#backup root@example.com:/etc/ example.com/ exclude=mtab,exclude=core
#backup_script ssh root@example.com "mysqldump -A > /var/db/dump/mysql.sql" unused2
#backup root@example.com:/var/db/dump/ example.com/
#backup_script /bin/date "+ backup of example.com ended at %c" unused9
# CVS.SOURCEFORGE.NET
#backup_script /usr/local/bin/backup_rsnapshot_cvsroot.sh rsnapshot.cvs.sourceforge.net/
# RSYNC.SAMBA.ORG
#backup rsync://rsync.samba.org/rsyncftp/ rsync.samba.org/rsyncftp/ |
| Code: | | systemctl list-timers |
| Quote: | NEXT LEFT LAST PASSED UNIT ACTIVATES
sam. 2015-01-10 23:47:27 CET 21min left sam. 2015-01-10 22:47:27 CET 38min ago sauvegarde_heure.timer sauvegarde_heure.service
dim. 2015-01-11 10:59:37 CET 11h left sam. 2015-01-10 09:50:31 CET 13h ago sauvegarde_jour.timer sauvegarde_jour.service
sam. 2015-01-17 11:14:57 CET 6 days left sam. 2015-01-10 10:05:51 CET 13h ago sauvegarde_semaine.timer sauvegarde_semaine.service
n/a n/a n/a n/a systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
4 timers listed.
Pass --all to see loaded but inactive timers, too. |
| Code: | | ls /usr/lib64/systemd/system/ | grep sauvegarde |
| Quote: | -rw-r--r-- 1 root root 191 18 oct. 16:06 sauvegarde_heure.service
-rw-r--r-- 1 root root 213 18 oct. 17:05 sauvegarde_heure.timer
-rw-r--r-- 1 root root 195 18 oct. 15:46 sauvegarde_jour.service
-rw-r--r-- 1 root root 275 18 oct. 17:04 sauvegarde_jour.timer
-rw-r--r-- 1 root root 197 18 oct. 16:19 sauvegarde_semaine.service
-rw-r--r-- 1 root root 279 18 oct. 17:05 sauvegarde_semaine.timer |
| Code: | | more sauvegarde_heure.timer |
| Quote: | [Unit]
Description=Timer sauvegarde horaire
RefuseManualStart=no
RefuseManualStop=no
[Timer]
OnBootSec=20min
OnUnitActiveSec=1h
#OnCalendar=hourly
Unit=sauvegarde_heure.service
[Install]
WantedBy=default.target |
| Code: | | more sauvegarde_heure.service |
| Quote: | [Unit]
Description=Sauvegarde horaire
RefuseManualStart=no
RefuseManualStop=yes
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
Type=oneshot
ExecStart=/usr/bin/rsnapshot hourly |
| Code: | | more sauvegarde_jour.timer |
| Quote: | [Unit]
Description=Timer sauvegarde journalière
RefuseManualStart=no
RefuseManualStop=no
[Timer]
OnBootSec=35min
#OnCalendar=daily
OnUnitActiveSec=1d
# Autoriser la persistence entre les reboot
Persistent=yes
Unit=sauvegarde_jour.service
[Install]
WantedBy=default.target |
| Code: | | more sauvegarde_jour.service |
| Quote: | [Unit]
Description=Sauvegarde journalière
RefuseManualStart=no
RefuseManualStop=yes
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
Type=oneshot
ExecStart=/usr/bin/rsnapshot daily |
| Code: | | more sauvegarde_semaine.timer |
| Quote: | [Unit]
Description=Timer sauvegarde hebdomadaire
RefuseManualStart=no
RefuseManualStop=no
[Timer]
OnBootSec=50min
OnUnitActiveSec=1w
#OnCalendar=weekly
# Autoriser la persistence entre les reboot
Persistent=yes
Unit=sauvegarde_semaine.service
[Install]
WantedBy=default.target |
| Code: | | more sauvegarde_semaine.service |
| Quote: | [Unit]
Description=Sauvegarde hebdomadaire
RefuseManualStart=no
RefuseManualStop=yes
[Service]
Nice=19
IOSchedulingClass=2
IOSchedulingPriority=7
Type=oneshot
ExecStart=/usr/bin/rsnapshot weekly |
_________________
Linux, cause booting is for adding new hardware
Last edited by Nitro_146 on Sat Jan 31, 2015 9:20 pm; edited 1 time in total |
|
| Back to top |
|
 |
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
| Posted: Thu Jan 22, 2015 9:28 pm Post subject: |
|
|
Up 
_________________
Linux, cause booting is for adding new hardware |
|
| Back to top |
|
|
Section_8
l33t
Joined: 22 May 2004
Posts: 627
|
| Posted: Sat Jan 24, 2015 1:57 am Post subject: |
|
|
Ok, since no one else has responded, maybe I can help with this. I use rsnapshot for daily/weekly/monthly backups (not hourly)
First, I don't know what those .timer and .service files are you posted, that I guess schedule the backups, so I won't be much help if they're the problem. I just use fcrontab for that.
My approach to solving service problems like this is make sure everything is being logged and figure it out in the logs. Whatever service schedules these commands should be logging everything it does. I would start by looking in those logs at when the daily & weekly backups were supposed to run and see if there was a problem.
If everything looks good there, you need to turn on rsapshot's logging. Even though I just run gentoo on a home desktop system (no mission critical company servers), with something like automated daily backups, my philosophy is you can't have too many logs.
A the minimum, I would uncomment:
| Code: | | #logfile /var/log/rsnapshot |
in my rsnapshot.conf. I also have:
| Code: | loglevel 5
verbose 5
rsync_short_args -av |
That last setting causes rsync to log every file it backs up.
If your daily and weekly rsnapshots are actually running, you should be able to see what's happening in those logs. |
|
| Back to top |
|
|
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
| Posted: Sat Jan 24, 2015 7:34 am Post subject: |
|
|
Hi Section_8, and thank's for your answer.
I will try to uncomment the line.
However, the snapshot seem to be executed
| Code: | # more messages | grep snapshot
...
Jan 23 07:57:06 core-i5 rsnapshot[6494]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 08:11:39 core-i5 rsnapshot[8789]: /usr/bin/rsnapshot daily: completed successfully
Jan 23 13:28:59 core-i5 rsnapshot[11444]: /usr/bin/rsnapshot weekly: completed successfully
Jan 23 13:59:22 core-i5 rsnapshot[16424]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 14:59:42 core-i5 rsnapshot[26188]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 15:59:52 core-i5 rsnapshot[3945]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 17:00:23 core-i5 rsnapshot[13872]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 18:00:42 core-i5 rsnapshot[23958]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 20:37:47 core-i5 rsnapshot[1048]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 21:38:11 core-i5 rsnapshot[10839]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 22:38:19 core-i5 rsnapshot[20268]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 23:38:38 core-i5 rsnapshot[29686]: /usr/bin/rsnapshot hourly: completed successfully
Jan 24 07:23:57 core-i5 rsnapshot[6390]: /usr/bin/rsnapshot hourly: completed successfully
Jan 24 07:38:19 core-i5 rsnapshot[8611]: /usr/bin/rsnapshot daily: completed successfully
Jan 24 07:53:17 core-i5 rsnapshot[10912]: /usr/bin/rsnapshot weekly: completed successfully
Jan 24 08:24:22 core-i5 rsnapshot[15724]: /usr/bin/rsnapshot hourly: completed successfully |
_________________
Linux, cause booting is for adding new hardware |
|
| Back to top |
|
|
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
| Posted: Sat Jan 24, 2015 7:39 am Post subject: |
|
|
| Nitro_146 wrote: | Hi Section_8, and thank's for your answer.
I will try to uncomment the line.
However, the snapshot seem to be executed
| Code: | # more /var/log/messages | grep snapshot
...
Jan 23 07:57:06 core-i5 rsnapshot[6494]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 08:11:39 core-i5 rsnapshot[8789]: /usr/bin/rsnapshot daily: completed successfully
Jan 23 13:28:59 core-i5 rsnapshot[11444]: /usr/bin/rsnapshot weekly: completed successfully
Jan 23 13:59:22 core-i5 rsnapshot[16424]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 14:59:42 core-i5 rsnapshot[26188]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 15:59:52 core-i5 rsnapshot[3945]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 17:00:23 core-i5 rsnapshot[13872]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 18:00:42 core-i5 rsnapshot[23958]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 20:37:47 core-i5 rsnapshot[1048]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 21:38:11 core-i5 rsnapshot[10839]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 22:38:19 core-i5 rsnapshot[20268]: /usr/bin/rsnapshot hourly: completed successfully
Jan 23 23:38:38 core-i5 rsnapshot[29686]: /usr/bin/rsnapshot hourly: completed successfully
Jan 24 07:23:57 core-i5 rsnapshot[6390]: /usr/bin/rsnapshot hourly: completed successfully
Jan 24 07:38:19 core-i5 rsnapshot[8611]: /usr/bin/rsnapshot daily: completed successfully
Jan 24 07:53:17 core-i5 rsnapshot[10912]: /usr/bin/rsnapshot weekly: completed successfully
Jan 24 08:24:22 core-i5 rsnapshot[15724]: /usr/bin/rsnapshot hourly: completed successfully |
|
_________________
Linux, cause booting is for adding new hardware |
|
| Back to top |
|
|
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
| Posted: Sun Jan 25, 2015 10:54 pm Post subject: |
|
|
After some days of testing, it seems that rnsapshot starts sucessfully on a daily and weekly basis
from /var/log/rsnapshot.log
| Quote: | [25/Jan/2015:10:07:39] require Lchown
[25/Jan/2015:10:07:39] Lchown module loaded successfully
[25/Jan/2015:10:07:39] /usr/bin/rsnapshot daily: started
[25/Jan/2015:10:07:39] Setting locale to POSIX "C"
[25/Jan/2015:10:07:39] echo 8421 > /var/run/rsnapshot.pid
[25/Jan/2015:10:07:39] /mnt/sauvegarde/daily.2 not present (yet), nothing to delete
[25/Jan/2015:10:07:39] /mnt/sauvegarde/daily.1 not present (yet), nothing to rotate
[25/Jan/2015:10:07:39] /mnt/sauvegarde/daily.0 not present (yet), nothing to rotate
[25/Jan/2015:10:07:39] /mnt/sauvegarde/hourly.3 not present (yet), nothing to copy
[25/Jan/2015:10:07:39] No directory to delete: /mnt/sauvegarde/_delete.8421
[25/Jan/2015:10:07:39] rm -f /var/run/rsnapshot.pid
[25/Jan/2015:10:07:39] /usr/bin/logger -i -p user.info -t rsnapshot /usr/bin/rsnapshot daily: completed successf
ully
[25/Jan/2015:10:07:39] /usr/bin/rsnapshot daily: completed successfully
[25/Jan/2015:10:22:39] require Lchown
[25/Jan/2015:10:22:39] Lchown module loaded successfully
[25/Jan/2015:10:22:39] /usr/bin/rsnapshot weekly: started
[25/Jan/2015:10:22:39] Setting locale to POSIX "C"
[25/Jan/2015:10:22:39] echo 10778 > /var/run/rsnapshot.pid
[25/Jan/2015:10:22:39] /mnt/sauvegarde/weekly.1 not present (yet), nothing to delete
[25/Jan/2015:10:22:39] /mnt/sauvegarde/weekly.0 not present (yet), nothing to rotate
[25/Jan/2015:10:22:39] /mnt/sauvegarde/daily.2 not present (yet), nothing to copy
[25/Jan/2015:10:22:39] No directory to delete: /mnt/sauvegarde/_delete.10778
[25/Jan/2015:10:22:39] rm -f /var/run/rsnapshot.pid
[25/Jan/2015:10:22:39] /usr/bin/logger -i -p user.info -t rsnapshot /usr/bin/rsnapshot weekly: completed success
fully
[25/Jan/2015:10:22:39] /usr/bin/rsnapshot weekly: completed successfully |
I think there might be a problem with the script that mounts /mnt/sauvegarde because it seem not to be executed, whereas in the hourly backup it is :
| Quote: | [25/Jan/2015:10:52:49] require Lchown
[25/Jan/2015:10:52:49] Lchown module loaded successfully
[25/Jan/2015:10:52:49] /usr/bin/rsnapshot hourly: started
[25/Jan/2015:10:52:49] Setting locale to POSIX "C"
[25/Jan/2015:10:52:49] echo 15446 > /var/run/rsnapshot.pid
[25/Jan/2015:10:52:49] /root/montage-partition-sauvegarde
[25/Jan/2015:10:52:50] /bin/rm -rf /mnt/sauvegarde/hourly.3/
[25/Jan/2015:10:52:58] mv /mnt/sauvegarde/hourly.2/ /mnt/sauvegarde/hourly.3/
[25/Jan/2015:10:52:58] mv /mnt/sauvegarde/hourly.1/ /mnt/sauvegarde/hourly.2/
[25/Jan/2015:10:52:58] /bin/cp -al /mnt/sauvegarde/hourly.0 /mnt/sauvegarde/hourly.1
[25/Jan/2015:10:53:08] /usr/bin/rsync -avv --delete --numeric-ids --relative --delete-excluded --exclude-from=/h
ome/pierre/.exclusion_rsync.txt /home/pierre /mnt/sauvegarde/hourly.0/localhost/
[25/Jan/2015:10:53:11] rsync succeeded
[25/Jan/2015:10:53:11] /usr/bin/rsync -avv --delete --numeric-ids --relative --delete-excluded --exclude-from=/h
ome/pierre/.exclusion_rsync.txt /etc /mnt/sauvegarde/hourly.0/localhost/
[25/Jan/2015:10:53:11] rsync succeeded
[25/Jan/2015:10:53:11] /usr/bin/rsync -avv --delete --numeric-ids --relative --delete-excluded --exclude-from=/h
ome/pierre/.exclusion_rsync.txt /usr/local /mnt/sauvegarde/hourly.0/localhost/
[25/Jan/2015:10:53:12] rsync succeeded
[25/Jan/2015:10:53:12] touch /mnt/sauvegarde/hourly.0/
[25/Jan/2015:10:53:12] /root/demontage-partition-sauvegarde
[25/Jan/2015:10:53:14] No directory to delete: /mnt/sauvegarde/_delete.15446
[25/Jan/2015:10:53:14] rm -f /var/run/rsnapshot.pid
[25/Jan/2015:10:53:14] /usr/bin/logger -i -p user.info -t rsnapshot /usr/bin/rsnapshot hourly: completed success
fully
[25/Jan/2015:10:53:14] /usr/bin/rsnapshot hourly: completed successfully |
Why this script is not executed ? It is called from /etc/rsnapshot.conf
_________________
Linux, cause booting is for adding new hardware |
|
| Back to top |
|
|
Section_8
l33t
Joined: 22 May 2004
Posts: 627
|
| Posted: Mon Jan 26, 2015 12:46 am Post subject: |
|
|
If I understand correctly, this may be your problem (quoted from man rsnapshot):
| Quote: | cmd_preexec
Full path (plus any arguments) to preexec script (optional). This script will run
immediately before each backup operation (but not any rotations).
|
Only the hourly run actually does a backup (synchs). The higher intervals - daily, weekly, monthly - just rotate previously made backups, and so don't run the cmd_preexec script. You could try just writing a little wrapper script that mounts the backup drive, runs rsnapshot, then unmounts it. |
|
| Back to top |
|
|
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Mon Jan 26, 2015 6:12 am Post subject: |
|
|
| Code: | #########################################
# BACKUP INTERVALS #
# Must be unique and in ascending order #
# i.e. hourly, daily, weekly, etc. #
#########################################
interval hourly 4
interval daily 3
interval weekly 2
#interval monthly 3 |
Those are in descending order (not that I know anything about the software.) The rotation thing sounds like the issue, but this stuck out, so I thought I'd query it. |
|
| Back to top |
|
|
Section_8
l33t
Joined: 22 May 2004
Posts: 627
|
| Posted: Mon Jan 26, 2015 12:40 pm Post subject: |
|
|
| That's the normal order for those intervals - from shortest to longest. |
|
| Back to top |
|
|
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
| Posted: Mon Jan 26, 2015 8:58 pm Post subject: |
|
|
I have written a script that includes mounting and unmounting the filesytem.
It seems to work, but I need some time to test it further.
I'll report back here in some time.
_________________
Linux, cause booting is for adding new hardware |
|
| Back to top |
|
|
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Tue Jan 27, 2015 3:09 am Post subject: |
|
|
| Section_8 wrote: | | That's the normal order for those intervals - from shortest to longest. |
Well if that's ordered-by ascending value as the comment indicated, then it's configured from longest to shortest, since weekly is set to 2, and hourly is set to 4.
That's why it stuck out.
No idea if that affects anything; it just seems silly not to follow the indicated ordering. |
|
| Back to top |
|
|
Section_8
l33t
Joined: 22 May 2004
Posts: 627
|
| Posted: Tue Jan 27, 2015 4:01 am Post subject: |
|
|
This is the paragraph from man rsnapshot that discusses the order of those intervals:
| Quote: | Backup levels must be specified in the config file in order, from most frequent to least
frequent. The first entry is the one which will be synced with the backup points. The
subsequent backup levels (e.g., daily, weekly, etc) simply rotate, with each higher
backup level pulling from the one below it for its .0 directory.
|
I think he has them in the correct order - hourly (most frequent) first. The order has nothing to do with the values in the parameters (the number of backups retained), just the frequency. Maybe they should clarify that comment in the sample config file. |
|
| Back to top |
|
|
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Tue Jan 27, 2015 8:29 am Post subject: |
|
|
| Section_8 wrote: | | I think he has them in the correct order - hourly (most frequent) first. The order has nothing to do with the values in the parameters (the number of backups retained), just the frequency. Maybe they should clarify that comment in the sample config file. |
Ah that's the critical distinction: the value is the number of backups retained, not an identifier.
Thanks. |
|
| Back to top |
|
|
Nitro_146
Apprentice
Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France
|
| Posted: Sat Jan 31, 2015 9:20 pm Post subject: |
|
|
After some testing, I believe the problem is solved by now.
Thank you for your help !
_________________
Linux, cause booting is for adding new hardware |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
