SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone,
I seem to have a bit of a problem with rsnapshot. After the 1st (full) backup, the i am trying to do the 2nd one (back to back really, so not many files will be changed) and it takes a loooong time ( i actually didn't let it finish )
I check the newly created backup a couple of minutes later and it already has copied 150MB of 'altered' data compared to the original full backup. This can't be.
I have checked the time on my 2 systems (the main server and this backup server) and the dates coincide ( I have a time server too for the internal network ). so modification times shouldn't be the reason why rsnapshot gets fooled into backing things up.
ofcourse nothing in the original full bakcup has bee chmod'ed between the 2 backups so thats not the reason either...
I do not know what else could be there reason though... any thoughts?
I check the newly created backup a couple of minutes later and it already has copied 150MB of 'altered' data compared to the original full backup. This can't be.
nass
Why do think 150MB can't be ? I do a daily incremental backup of my home directory (2 users) and that's usually over 165MB, most of which is firefox and thunderbird related and that excludes the cache directories. I also do a weekly incremental full backup, excluding home directories, and according to my logs that's over 179MB although it only takes 3-4 minutes over wired 100Mb ethernet.
I use my own scripts using rsync and hard links for this so I can't comment on rsnapshot but just thought I would give an indication that 150MB is really not that much data. If I were to include the firefox cache then my backups would be much larger.
well 150MB of data seem little esp compared to 1.7TB of office data, but among those I find a backup of the /etc/ directory and I know I didn't change any config files between these 2 backups...
Also, you can use "rsnapshot-diff" to see what changed.
Eg.
Code:
$ sudo rsnapshot-diff /backup/daily.0 /backup/daily.1
Comparing /backup/daily.1 to /backup/daily.0
Between /backup/daily.1 and /backup/daily.0:
897 were added, taking 1678470607 bytes;
25028 were removed, saving 2293944092 bytes;
but among those I find a backup of the /etc/ directory and I know I didn't change any config files between these 2 backups...
You do realize that each snapshot is actually a complete backup with all files and directories using hardlinks for unchanged files? (Strictly speaking I should say rsync overwrites hardlinks for changed files, replacing with the new file.)
I do not get rsnapshot to do incremental backups. See below:
Code:
# rsnapshot-diff ./daily.0 ./daily.1
Comparing ./daily.1 to ./daily.0
Between ./daily.1 and ./daily.0:
220911 were added, taking 604634711656 bytes;
220911 were removed, saving 604634711656 bytes;
If you are performing the backups manually back-to-back, then I agree there should be almost no time involved with the second backup. In fact, the kernel will have cached much of the files to help improve the time. I saw this on another system I was testing about two weeks ago.
How do you have sync_first configured? If that option is set to 1, then you have to perform the very first backup manually before rsnapshot will start accumulating rotations. If set to 0 then rsnapshot will perform the first backup in its own.
I have just found the source of the problem. I had:
Code:
# 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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.