NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Rsnapshot installed...nothing is happening...
Hi all, I've just installed this addon and commented out the following line in the addons-config/rsnapshot/rsnapshot.conf file :
backup /etc/ localhost/
which should backup my etc folder to the snapshot.
But....nothing is happening....
Should Rsync be activated in the frontview even if in the rsnapshot.conf file there's already this line :
# rsync must be enabled for anything to work. This is the only command that
# must be enabled.
cmd_rsync /usr/bin/rsync
Here's the rsnapshot.conf file :
#################################################
# 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 /c/snapshot/
# 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 2
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 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
# 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 --stats --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 /path/to/exclude/file
# 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).
#
# Super Poussin : Do Not change link_dest Value
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
##############################
### ReadyNAS Users ###
### Do not use path with ###
### symlinks !! ###
### /c/media is correct ###
### /media is not correct ###
### Super Poussin ###
##############################
#backup /home/ 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/
backup /etc/ localhost/
which should backup my etc folder to the snapshot.
But....nothing is happening....
Should Rsync be activated in the frontview even if in the rsnapshot.conf file there's already this line :
# rsync must be enabled for anything to work. This is the only command that
# must be enabled.
cmd_rsync /usr/bin/rsync
Here's the rsnapshot.conf file :
#################################################
# 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 /c/snapshot/
# 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 2
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 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
# 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 --stats --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 /path/to/exclude/file
# 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).
#
# Super Poussin : Do Not change link_dest Value
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
##############################
### ReadyNAS Users ###
### Do not use path with ###
### symlinks !! ###
### /c/media is correct ###
### /media is not correct ###
### Super Poussin ###
##############################
#backup /home/ 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/
16 Replies
Replies have been turned off for this discussion
michelefaccini wrote: what's the appropriate FS type to format my USB stick if I want to save entire nas directories ? Should I use EXT3 or EXT4.
FAT32 or NTFS can't be a chosen, right ?
I use EXT4, but NTFS is probably a better choice if you also need easy, direct access to the USB drive from Windows. Some of EXT3/4's obscure file permissions and properties are not supported by NTFS (and vice-versa), so those properties might be lost in the backup/restore process. However, the data itself (and the major file permissions and properties) will be preserved.
I would not use FAT32, as it has multiple limitations including lack of support for files larger than 4GB.- After reading the documentation, especially http://www.rsnapshot.org/howto/1.2/rsnapshot-HOWTO.en.pdf, things are a little bit clearer...
Executing rsnapshot configtest will tell you if there's any syntax error in the rsnapshot.conf file.
Executing rsnapshot -t hourly will tell rsnapshot to simulate an "hourly" backup. It should print out the commands it will perform when it runs for real (note that the test doesn't actually do things).
Under etc/cron.d/ you will find the rsnapshot file that contains :
0 */4 * * * root /c/addons-config/rsnapshot/hourly.sh
30 23 * * * root /c/addons-config/rsnapshot/daily.sh
0 3 * * 1 root /c/addons-config/rsnapshot/weekly.sh
30 2 1 * * root /c/addons-config/rsnapshot/monthly.sh
If you have setup alerts (from Frontview, System settings) you will receive a mail like the following :
ERRORS
/etc NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
NO STATS DATA
require Lchown
Lchown module loaded successfully
/usr/bin/du -csh /USB_FLASH_2/hourly.0/
5.0M /USB_FLASH_2/hourly.0/
5.0M total
The next step I would like to setup is :
to backup entire folders like the etc one once a month.
to backup single files daily or weekly. michelefaccini wrote: After reading the documentation, especially http://www.rsnapshot.org/howto/1.2/rsnapshot-HOWTO.en.pdf, things are a little bit clearer...
Good.michelefaccini wrote: The next step I would like to setup is :
to backup entire folders like the etc one once a month.
to backup single files daily or weekly.
With rsnapshot, there is usually no reason to do that. Only files that have changed are copied to the backup drive, so folders (like /etc) which contain files that do not frequently change are backed up almost instantaneously, and the snapshots of such folders consume almost no disk space.- Ok....Thanks again for your answer !
Now I have to try the same test as above but with my Windows 7 Desktop PC as the destination.....
I tried this :
snapshot_root /Michele-pc/k:/TEST_BACKUP/
where Michele-pc is my Windows 7 64 bit Ultimate Desktop PC
and k:/TEST_BACKUP is a shared folder (network access to everyone)
Executing rsnapshot hourly from the putty shell, I had a whole bunch of lines....the following are the latest :
Number of files: 1668
Number of files transferred: 1045
Total file size: 3325237 bytes
Total transferred file size: 3308973 bytes
Literal data: 3308973 bytes
Matched data: 0 bytes
File list size: 55809
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 3411765
Total bytes received: 21998
sent 3411765 bytes received 21998 bytes 2289175.33 bytes/sec
total size is 3325237 speedup is 0.97
rsync succeeded
touch /Michele-pc/k:/test backup/hourly.0/ No directory to delete: /Michele-pc/k:/test backup/ delete.4940
rm -f /var/run/rsnapshot.pid
/usr/bin/logger -p user.info -t rsnapshot /usr/local/bin/rsnapshot hourly: \
completed successfully
BUT NOTHING IN THE DESTINATION FOLDER michelefaccini wrote:
snapshot_root /Michele-pc/k:/TEST_BACKUP/
where Michele-pc is my Windows 7 64 bit Ultimate Desktop PC
and k:/TEST_BACKUP is a shared folder (network access to everyone)
Executing rsnapshot hourly from the putty shell, I had a whole bunch of lines....
....
BUT NOTHING IN THE DESTINATION FOLDER
It looks to me as though you have successfully backed up to a directory on the ReadyNAS called /Michele-pc/k:/TEST_BACKUP/. Have you checked to see whether your files are in that directory?
If you want programs running on the ReadyNAS to see your PC, mount the PC's shared folder as a Samba share on the ReadyNAS. See here for instructions:
http://www.cyberciti.biz/tips/how-to-mount-remote-windows-partition-windows-share-under-linux.html
http://www.cyberciti.biz/faq/configure-a-system-to-automount-a-samba-share-with-etcfstab/- Also, if there is any chance that the share on the PC might not always be mounted, uncomment this line in your rsnapshot.conf file by removing the "#":
#no_create_root 1
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
