NSLU2-Linux
view · edit · print · history

HowTo.InstallRSnapshot History

Hide minor edits - Show changes to markup

April 09, 2007, at 04:32 AM by Matthew -- Fixing formatting, clarified my last edit.
Changed lines 88-91 from:

Update! rsnapshot doesn't seem to work properly when the link_dest option is configured!

I installed rsnapshot 1.2.9-1 using ipkg. Each time it ran, it seemed to take a constant amount of time and according to du, each hourly snapshot was taking up new space. After setting the link_dest parameter in rsnapshot.conf to zero (it defaulted to 1 in the package) rsnapshot began to behave as expected, 1st run was slow, and subsequent runs took time proportional to what had been changed,so usually very fast. Also, the unnecessary space consumption problem appeared to go away,

to:

Update! rsnapshot doesn't seem to work properly when the link_dest option is configured!

I installed rsnapshot 1.2.9-1 using ipkg following above instructions on unslung 6.8beta. Each time it ran, it seemed to take a constant amount of time and according to du, each hourly snapshot was taking up new space. After setting the link_dest parameter in rsnapshot.conf to zero (it defaulted to 1 in the package) rsnapshot began to behave as expected - 1st run was slow then subsequent runs took time proportional to what had been changed, so usually very fast. Also, the unnecessary space consumption problem appeared to go away.

April 09, 2007, at 04:29 AM by Matthew -- Problem with link_dest option in rsnapshot 1.2.9-1 from ipkg
Added lines 87-91:

Update! rsnapshot doesn't seem to work properly when the link_dest option is configured!

I installed rsnapshot 1.2.9-1 using ipkg. Each time it ran, it seemed to take a constant amount of time and according to du, each hourly snapshot was taking up new space. After setting the link_dest parameter in rsnapshot.conf to zero (it defaulted to 1 in the package) rsnapshot began to behave as expected, 1st run was slow, and subsequent runs took time proportional to what had been changed,so usually very fast. Also, the unnecessary space consumption problem appeared to go away,

November 03, 2005, at 06:39 PM by JimmyFergus -- OpenSlug notes
Changed lines 13-14 from:

(OpenSlug doesn't require unslung-feeds here, but does require perl-modules after perl - this takes ages and installs huge numbers of packages, you could probably install a subset of the modules, if you'd rather.)

to:

(OpenSlug doesn't require unslung-feeds here, but does require perl-modules after perl - this takes ages and installs huge numbers of packages, you could probably install a subset of the modules based on the use directives at the top of rsnapshot.)

November 03, 2005, at 06:37 PM by JimmyFergus --
Changed lines 13-14 from:

(OpenSlug doesn't require unslung-feeds here, but does require perl-modules after perl - this takes a while, you could probably install a subset of the modules, if you'd rather)

to:

(OpenSlug doesn't require unslung-feeds here, but does require perl-modules after perl - this takes ages and installs huge numbers of packages, you could probably install a subset of the modules, if you'd rather.)

November 03, 2005, at 06:32 PM by JimmyFergus -- Some notes for OpenSlug use
Changed lines 42-43 from:

(OpenSlug: if you didn't tell configure otherwise, the conf files will be in /usr/local/etc)

to:

(OpenSlug: if you didn't tell configure otherwise with --sysconfdir, the conf files will be in /usr/local/etc)

November 03, 2005, at 06:31 PM by JimmyFergus --
Added lines 13-14:

(OpenSlug doesn't require unslung-feeds here, but does require perl-modules after perl - this takes a while, you could probably install a subset of the modules, if you'd rather)

Added lines 27-28:

(for OpenSlug, just ./configure without arguments is fine)

Added lines 42-43:

(OpenSlug: if you didn't tell configure otherwise, the conf files will be in /usr/local/etc)

August 26, 2005, at 01:48 AM by tman --
Changed lines 5-12 from:
  # ipkg update
  # ipkg install unslung-feeds
  # ipkg update
  # ipkg install perl
  # ipkg install rsync  
  # ipkg install coreutils
  # ipkg install make
to:
  ipkg update
  ipkg install unslung-feeds
  ipkg update
  ipkg install perl
  ipkg install rsync  
  ipkg install coreutils
  ipkg install make
Changed lines 17-18 from:
  # ./configure --with-perl=/opt/bin/perl --with-rsync=/opt/bin/rsync --with-cp=/opt/bin/cp --sysconfdir=/opt/etc --bindir=/opt/bin --mandir=/opt/doc
to:
  ./configure \ 
--with-perl=/opt/bin/perl \
--with-rsync=/opt/bin/rsync \
--with-cp=/opt/bin/cp \
--sysconfdir=/opt/etc \
--bindir=/opt/bin \
--mandir=/opt/doc
Changed lines 28-29 from:
  # /opt/bin/make install
to:
 /opt/bin/make install
Changed lines 31-34 from:
  # sed -ie 's/system("du/system("\/opt\/bin\/du/' /opt/bin/rsnapshot 

  (the rsnapshot 1.2.1 version has a cmd_du arg to specify the path to du, you may want to consider this instead).
to:
 sed -ie 's/system("du/system("\/opt\/bin\/du/' /opt/bin/rsnapshot 

(the rsnapshot 1.2.1 version has a cmd_du arg to specify the path to du, you may want to consider this instead).

Changed lines 36-37 from:
  # cp /opt/etc/rsnapshot.conf.default /opt/etc/rsnapshot.conf
to:
 cp /opt/etc/rsnapshot.conf.default /opt/etc/rsnapshot.conf
Changed lines 47-53 from:

If you are lucky enough to have 2 physical drives then I'd recommend setting your snapshot_root to a different drive than the one your primary data is stored on.

9. Test whether your configuration file is valid:

  # /opt/bin/rsnapshot configtest
  Syntax OK
to:

If you are lucky enough to have 2 physical drives then I'd recommend setting your snapshot_root to a different drive than the one your primary data is stored on.

9. Test whether your configuration file is valid. It should return "Syntax OK"

 /opt/bin/rsnapshot configtest
Changed lines 65-66 from:
  # /opt/bin/rsnapshot hourly
to:
 /opt/bin/rsnapshot hourly
Changed lines 74-77 from:
  1. ipkg install unslung-feeds
  2. ipkg update
  3. ipkg install rsnapshot
to:
 ipkg install unslung-feeds
 ipkg update
 ipkg install rsnapshot
Changed lines 80-81 from:

Update: rsnapshot 1.1.6 and 1.2.0 had security problems, which were fixed in versions 1.1.7 and 1.2.1. Please do not use the earlier versions, as they are vulnerable. See http://www.rsnapshot.org details.

to:

Update: rsnapshot 1.1.6 and 1.2.0 had security problems, which were fixed in versions 1.1.7 and 1.2.1. Please do not use the earlier versions, as they are vulnerable. See http://www.rsnapshot.org details.

August 25, 2005, at 02:23 PM by HannesReich --
Changed lines 1-2 from:

rsnapshot is a great replacement for the built-in backup script the NSLU2 provides. As well as providing a copy of the data in some other place (probably another drive), it also provides versioning of your data so you can recover from an accidental file deletion, corruption, or unwanted change. Commercial products refer to these version as snapshots.

to:

rsnapshot is a great replacement for the built-in backup script the NSLU2 provides. As well as providing a copy of the data in some other place (probably another drive), it also provides versioning of your data so you can recover from an accidental file deletion, corruption, or unwanted change. Commercial products refer to these version as snapshots. rsnapshot can also be used to make backups of remote machines via SSH.

July 24, 2005, at 11:56 PM by Nathan -- Version changes
Changed line 24 from:

6. Fix a small bug with the du feature in rsnapshot 1.1.6:

to:

6. Fix a small bug with the du feature in rsnapshot 1.1.7:

Added lines 27-28:
  (the rsnapshot 1.2.1 version has a cmd_du arg to specify the path to du, you may want to consider this instead).
Changed lines 51-52 from:

11. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be ran. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete. If you've replaced the version of syslogd then you may not need to do this step and you can ignore the /opt/bin/cronlogger section in the next step.

to:

11. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be run. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete. If you've replaced the version of syslogd then you may not need to do this step and you can ignore the /opt/bin/cronlogger section in the next step.

Added lines 75-77:

Update: rsnapshot 1.1.6 and 1.2.0 had security problems, which were fixed in versions 1.1.7 and 1.2.1. Please do not use the earlier versions, as they are vulnerable. See http://www.rsnapshot.org details.

March 26, 2005, at 05:25 AM by Blaise at geeky dot net --
Added lines 64-72:

Update: if you install the unslung-feeds ipkg, rsnapshot 1.2.0 is now available prebuilt, depracating the requirement to build it from source on the NSLU2. simply issue the following commands:

  1. ipkg install unslung-feeds
  2. ipkg update
  3. ipkg install rsnapshot

then configure as described above, from step 7 down.

January 26, 2005, at 12:39 PM by paulhar --
Changed lines 3-8 from:

Installing rsnapshot is reasonably trivial. Use the following as a guide.

1. You may need to add the "native" feed into your (possibly freshly created) /etc/ipkg/unslung-native.conf by adding the following line:

  src/gz unslung-native http://ipkg.nslu2-linux.org/feeds/unslung/native

2. Install the required packages

to:

1. Install the required packages in the following order:

Added lines 5-6:
  # ipkg update
  # ipkg install unslung-feeds
Changed line 13 from:

3. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version]

to:

2. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version]

Changed line 15 from:

4. Change into the directory you extracted rsnapshot into and run the following.

to:

3. Change into the directory you extracted rsnapshot into and run the following.

Changed line 19 from:

5. Ignore any warnings/errors about missing tr/cmp if they occur, otherwise try to figure out what went wrong.

to:

4. Ignore any warnings/errors about missing tr/cmp if they occur, otherwise try to figure out what went wrong.

Changed line 21 from:

6. Complete the install:

to:

5. Complete the install:

Changed line 24 from:

7. Fix a small bug with the du feature in rsnapshot 1.1.6:

to:

6. Fix a small bug with the du feature in rsnapshot 1.1.6:

Changed line 27 from:

8. Copy the defaults file to your own:

to:

7. Copy the defaults file to your own:

Changed line 30 from:

9. Edit your /opt/etc/rsnapshot.conf file following the documentation included on the

to:

8. Edit your /opt/etc/rsnapshot.conf file following the documentation included on the

Changed line 42 from:

10. Test whether your configuration file is valid:

to:

9. Test whether your configuration file is valid:

Changed line 46 from:

11. If you got errors about your backup lines then double check you followed the rsnapshot manual

to:

10. If you got errors about your backup lines then double check you followed the rsnapshot manual

Changed line 49 from:

12. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be ran. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete. If you've replaced the version of syslogd then you may not need to do this step and you can ignore the /opt/bin/cronlogger section in the next step.

to:

11. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be ran. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete. If you've replaced the version of syslogd then you may not need to do this step and you can ignore the /opt/bin/cronlogger section in the next step.

Changed line 51 from:

13. Once you are happy with your configuration, you've added the cronlogger script and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

to:

12. Once you are happy with your configuration, you've added the cronlogger script and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

Changed line 54 from:

14. Repeat the above for any daily and weekly, again referring to the documentation and normal

to:

13. Repeat the above for any daily and weekly, again referring to the documentation and normal

Changed lines 58-61 from:

15. Consider enabling the rsync daemon logging logging to get more useful errors if you plan on using remote ssh/rsyncd copies and rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

  log file = /share/hdd/conf/rsyncd.log

16. Either wait until your next scheduled run or start one manually:

to:

14. Either wait until your next scheduled run or start one manually:

Changed line 61 from:

17. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

to:

15. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

Changed line 63 from:

18. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

to:

16. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

January 26, 2005, at 11:55 AM by uSURPER --
Changed lines 5-6 from:

1. Install the required packages

to:

1. You may need to add the "native" feed into your (possibly freshly created) /etc/ipkg/unslung-native.conf by adding the following line:

  src/gz unslung-native http://ipkg.nslu2-linux.org/feeds/unslung/native
Added lines 8-10:

2. Install the required packages

  # ipkg update
Changed line 16 from:

2. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version]

to:

3. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version]

Changed line 18 from:

3. Change into the directory you extracted rsnapshot into and run the following.

to:

4. Change into the directory you extracted rsnapshot into and run the following.

Changed line 22 from:

4. Ignore any warnings/errors about missing tr/cmp if they occur, otherwise try to figure out what went wrong.

to:

5. Ignore any warnings/errors about missing tr/cmp if they occur, otherwise try to figure out what went wrong.

Changed line 24 from:

5. Complete the install:

to:

6. Complete the install:

Changed line 27 from:

6. Fix a small bug with the du feature in rsnapshot 1.1.6:

to:

7. Fix a small bug with the du feature in rsnapshot 1.1.6:

Changed line 30 from:

7. Copy the defaults file to your own:

to:

8. Copy the defaults file to your own:

Changed line 33 from:

8. Edit your /opt/etc/rsnapshot.conf file following the documentation included on the

to:

9. Edit your /opt/etc/rsnapshot.conf file following the documentation included on the

Changed line 45 from:

9. Test whether your configuration file is valid:

to:

10. Test whether your configuration file is valid:

Changed line 49 from:

10. If you got errors about your backup lines then double check you followed the rsnapshot manual

to:

11. If you got errors about your backup lines then double check you followed the rsnapshot manual

Changed line 52 from:

11. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be ran. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete.

to:

12. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be ran. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete. If you've replaced the version of syslogd then you may not need to do this step and you can ignore the /opt/bin/cronlogger section in the next step.

Changed line 54 from:

12. Once you are happy with your configuration, you've added the cronlogger script and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

to:

13. Once you are happy with your configuration, you've added the cronlogger script and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

Changed line 57 from:

13. Repeat the above for any daily and weekly, again referring to the documentation and normal

to:

14. Repeat the above for any daily and weekly, again referring to the documentation and normal

Changed line 61 from:

14. Consider enabling the rsync daemon logging logging to get more useful errors if you plan on using remote ssh/rsyncd copies and rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

to:

15. Consider enabling the rsync daemon logging logging to get more useful errors if you plan on using remote ssh/rsyncd copies and rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

Changed line 64 from:

15. Either wait until your next scheduled run or start one manually:

to:

16. Either wait until your next scheduled run or start one manually:

Changed line 67 from:

16. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

to:

17. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

Changed line 69 from:

17. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

to:

18. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

January 25, 2005, at 08:24 PM by rwhitby --
Changed line 7 from:
  # ipkg install perl561-shared
to:
  # ipkg install perl
January 25, 2005, at 03:15 PM by uSURPER --
Changed line 7 from:
  # ipkg install perl    
to:
  # ipkg install perl561-shared
January 25, 2005, at 02:28 PM by uSURPER --
Changed line 7 from:
  # ipkg install perl      [if this fails then see http://www.nslu2-linux.org/wiki/HowTo/BuildPerlOnYourNSLU2Box the Binary installation section]
to:
  # ipkg install perl    
Changed line 12 from:

2. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version)

to:

2. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version]

Changed line 23 from:

6. Fix a small bug with the du feature in rsnapshot:

to:

6. Fix a small bug with the du feature in rsnapshot 1.1.6:

Changed lines 48-50 from:

11. Once you are happy with your configuration and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

  5 9-22 * * * root /opt/bin/rsnapshot hourly &>/dev/null
to:

11. Follow the instructions on HowTo.EnableLoggingInCron - at a minimum install the cronlogger script and change it's permissions so it can be ran. If you don't then you will see rsync 13 errors in your log file and your snapshots will not be complete.

Changed lines 50-53 from:

12. Repeat the above for any daily and weekly, again referring to the documentation and normal

to:

12. Once you are happy with your configuration, you've added the cronlogger script and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

  5 9-22 * * * root /opt/bin/cronlogger /opt/bin/rsnapshot hourly &>/dev/null

13. Repeat the above for any daily and weekly, again referring to the documentation and normal

Changed line 57 from:

13. Consider enabling the rsync daemon logging logging to get more useful errors if you plan on using remote ssh/rsyncd copies and rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

to:

14. Consider enabling the rsync daemon logging logging to get more useful errors if you plan on using remote ssh/rsyncd copies and rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

Changed lines 60-61 from:

14. Either wait until your next scheduled run or start one manually:

  /opt/bin/rsnapshot hourly
to:

15. Either wait until your next scheduled run or start one manually:

  # /opt/bin/rsnapshot hourly
Changed line 63 from:

15. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

to:

16. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

Changed line 65 from:

16. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

to:

17. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

January 23, 2005, at 04:49 PM by uSURPER --
Changed line 7 from:
  # ipkg install perl      [if this fails then see http://www.nslu2-linux.org/wiki/HowTo/BuildPerlOnYourNSLU2Box the Binary installation] section
to:
  # ipkg install perl      [if this fails then see http://www.nslu2-linux.org/wiki/HowTo/BuildPerlOnYourNSLU2Box the Binary installation section]
January 23, 2005, at 12:51 PM by uSURPER --
Changed line 56 from:

13. Consider enabling the rsync daemon logging to get more useful errors if rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

to:

13. Consider enabling the rsync daemon logging logging to get more useful errors if you plan on using remote ssh/rsyncd copies and rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

January 23, 2005, at 10:44 AM by uSURPER --
Changed lines 33-34 from:
  • Comment out all the existing backup lines because they won't work with a normal NSLU2

configuration.

to:
  • Comment out all the existing backup lines because they won't work with a normal NSLU2 configuration.
January 23, 2005, at 10:43 AM by uSURPER --
Changed lines 54-60 from:

cron rules for timing. Either wait until your next scheduled run or start one manually:

to:

cron rules for timing. Restart cron:

  /etc/rc.d/rc.crond

13. Consider enabling the rsync daemon logging to get more useful errors if rsnapshot fails for some reason (e.g. error code 13) by editing /etc/rsyncd.conf and adding something like:

  log file = /share/hdd/conf/rsyncd.log

14. Either wait until your next scheduled run or start one manually:

Changed lines 63-65 from:

13. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

to:

15. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

16. You can have multiple different configuration files that allow you to have totally different configurations for certain backups. Again, read the rsnapshot documentation.

January 22, 2005, at 05:42 PM by uSURPER --
Changed lines 1-3 from:

Installing http://www.rsnapshot.org rsnapshot is reasonably trivial. Use the following as a guide.

to:

http://www.rsnapshot.org rsnapshot is a great replacement for the built-in backup script the NSLU2 provides. As well as providing a copy of the data in some other place (probably another drive), it also provides versioning of your data so you can recover from an accidental file deletion, corruption, or unwanted change. Commercial products refer to these version as http://www.netapp.com/products/snapshot.html snapshots.

Installing rsnapshot is reasonably trivial. Use the following as a guide.

January 22, 2005, at 05:36 PM by uSURPER --
Changed lines 5-8 from:
  ipkg install perl      [if this fails then see http://www.nslu2-linux.org/wiki/HowTo/BuildPerlOnYourNSLU2Box the Binary installation] section
  ipkg install rsync  
  ipkg install coreutils
  ipkg install make
to:
  # ipkg install perl      [if this fails then see http://www.nslu2-linux.org/wiki/HowTo/BuildPerlOnYourNSLU2Box the Binary installation] section
  # ipkg install rsync  
  # ipkg install coreutils
  # ipkg install make
Changed line 14 from:
  ./configure --with-perl=/opt/bin/perl --with-rsync=/opt/bin/rsync --with-cp=/opt/bin/cp --sysconfdir=/opt/etc --bindir=/opt/bin --mandir=/opt/doc
to:
  # ./configure --with-perl=/opt/bin/perl --with-rsync=/opt/bin/rsync --with-cp=/opt/bin/cp --sysconfdir=/opt/etc --bindir=/opt/bin --mandir=/opt/doc
Changed line 19 from:
  /opt/bin/make install
to:
  # /opt/bin/make install
Changed line 22 from:
  sed -ie 's/system("du/system("\/opt\/bin\/du/' /opt/bin/rsnapshot 
to:
  # sed -ie 's/system("du/system("\/opt\/bin\/du/' /opt/bin/rsnapshot 
Changed line 25 from:
  cp /opt/etc/rsnapshot.conf.default /opt/etc/rsnapshot
to:
  # cp /opt/etc/rsnapshot.conf.default /opt/etc/rsnapshot.conf
Changed lines 27-28 from:

8. -- more to follow --

to:

8. Edit your /opt/etc/rsnapshot.conf file following the documentation included on the http://www.rsnapshot.org rsnapshot website. Specifically pay attention to the following:

  • Uncomment the cmd_cp* line
  • Comment out the cmd_logger line
  • Comment out all the existing backup lines because they won't work with a normal NSLU2

configuration.

  • Consider uncommenting the lockfile line because the NSLU2 isn't the fastest machine in the world and snapshots can take a long time. This way they won't overlap and cause problems. [though - if you reboot or crash while a snapshot is happening then you'll need to manually remove the lock file]
  • Consider using logging by uncommenting and changing the logfile line. To get useful output also change the

loglevel to 5.

If you are lucky enough to have 2 physical drives then I'd recommend setting your snapshot_root to a different drive than the one your primary data is stored on.

9. Test whether your configuration file is valid:

  # /opt/bin/rsnapshot configtest
  Syntax OK

10. If you got errors about your backup lines then double check you followed the rsnapshot manual and used <tabs> instead of <spaces>.

11. Once you are happy with your configuration and you've tested it, you probably want to schedule it in cron. Edit /etc/crontab and add something like this:

  5 9-22 * * * root /opt/bin/rsnapshot hourly &>/dev/null

12. Repeat the above for any daily and weekly, again referring to the documentation and normal cron rules for timing. Either wait until your next scheduled run or start one manually:

  /opt/bin/rsnapshot hourly

13. Your first snapshot may take a long time to run. If you enabled logging then check your log file occasionally as it may be telling you that there is a problem and since the cron NSLU uses doesn't send mail you may not notice them.

January 22, 2005, at 04:50 PM by uSURPER --
Changed line 1 from:

1. Install required packages

to:

Installing http://www.rsnapshot.org rsnapshot is reasonably trivial. Use the following as a guide.

Changed lines 3-5 from:
  ipkg install rsync  (if not already installed)
  ipkg install perl  [magic needed]
  ipkg install coreutils   (for cp, etc)
to:

1. Install the required packages

  ipkg install perl      [if this fails then see http://www.nslu2-linux.org/wiki/HowTo/BuildPerlOnYourNSLU2Box the Binary installation] section
  ipkg install rsync  
  ipkg install coreutils
  ipkg install make
Changed lines 12-13 from:

Bugfix:

   # sed -ie 's/system("du/system("\/opt\/bin\/du/' rsnapshot 
to:

3. Change into the directory you extracted rsnapshot into and run the following.

  ./configure --with-perl=/opt/bin/perl --with-rsync=/opt/bin/rsync --with-cp=/opt/bin/cp --sysconfdir=/opt/etc --bindir=/opt/bin --mandir=/opt/doc

4. Ignore any warnings/errors about missing tr/cmp if they occur, otherwise try to figure out what went wrong.

5. Complete the install:

  /opt/bin/make install

6. Fix a small bug with the du feature in rsnapshot:

  sed -ie 's/system("du/system("\/opt\/bin\/du/' /opt/bin/rsnapshot 

7. Copy the defaults file to your own:

  cp /opt/etc/rsnapshot.conf.default /opt/etc/rsnapshot

8.

January 22, 2005, at 03:44 PM by uSURPER --
Added lines 9-10:

Bugfix:

   # sed -ie 's/system("du/system("\/opt\/bin\/du/' rsnapshot 
January 22, 2005, at 10:37 AM by uSURPER --
Changed lines 1-3 from:

ipkg install rsync (if not already installed) ipkg install perl [magic needed] ipkg install coreutils (for cp, etc)

to:

1. Install required packages

Added lines 3-9:
  ipkg install rsync  (if not already installed)
  ipkg install perl  [magic needed]
  ipkg install coreutils   (for cp, etc)

2. Download and extract rsnapshot from the http://www.rsnapshot.org site [choose the Generic Linux version)

-- more to follow --

January 22, 2005, at 10:33 AM by uSURPER --
Changed lines 1-4 from:

Describe InstallRSnapshot here.

to:

ipkg install rsync (if not already installed) ipkg install perl [magic needed] ipkg install coreutils (for cp, etc)

view · edit · print · history · Last edited by Matthew.
Based on work by Matthew, JimmyFergus, tman, HannesReich, Nathan, Blaise at geeky dot net, paulhar, uSURPER, and rwhitby.
Originally by uSURPER.
Page last modified on April 09, 2007, at 04:32 AM