Backup Central

I've read the docs and looked at the sample config, and I still have
absolutely no clue how to configure intervals to get rsnapshot to work
right.

Here's my config file:

config_version 1.2
snapshot_root /mybook2/backups
no_create_root 1
cmd_cp /bin/cp
cmd_rm /bin/rm
cmd_rsync /usr/bin/rsync
cmd_logger /usr/bin/logger
cmd_du /bin/du
cmd_rsnapshot_diff /usr/bin/rsnapshot-diff
verbose 2
loglevel 3
lockfile /var/run/rsnapshot.pid
link_dest 1
backup /home/ localhost/
backup /etc/ localhost/
interval daily 7
interval weekly 4
interval monthly 24

According to the docs, that means keep 7 daily backups, then 4 weekly
backups, then 24 monthly (28-day months) backups. The crontab entries
look like this:

3 1 * * * /usr/bin/rsnapshot monthly
3 2 * * * /usr/bin/rsnapshot weekly
3 3 * * * /usr/bin/rsnapshot daily

But all I get are daily backups for the past (7+4+24) days. [They
have various names starting with daily/weekly/monthly, but they're all
just 1 day apart.] Weekly backups be a 7 days apart and monthly
backups should be 4 weeks apart.

Here's an exmaple listing of a file that gets modified every few
minutes:

ls -lt */localhost/home/grante/.imapnotify.log
[...] May 20 03:22 daily.0/localhost/home/grante/.imapnotify.log
[...] May 19 04:13 daily.1/localhost/home/grante/.imapnotify.log
[...] May 18 04:11 daily.2/localhost/home/grante/.imapnotify.log
[...] May 17 04:17 daily.3/localhost/home/grante/.imapnotify.log
[...] May 16 04:14 daily.4/localhost/home/grante/.imapnotify.log
[...] May 15 04:12 daily.5/localhost/home/grante/.imapnotify.log
[...] May 14 04:11 daily.6/localhost/home/grante/.imapnotify.log
[...] May 13 04:13 weekly.0/localhost/home/grante/.imapnotify.log
[...] May 12 04:14 weekly.1/localhost/home/grante/.imapnotify.log
[...] May 11 04:14 weekly.2/localhost/home/grante/.imapnotify.log
[...] May 10 04:25 weekly.3/localhost/home/grante/.imapnotify.log
[...] May 9 04:17 monthly.0/localhost/home/grante/.imapnotify.log
[...] May 8 04:18 monthly.1/localhost/home/grante/.imapnotify.log
[...] May 7 04:16 monthly.2/localhost/home/grante/.imapnotify.log
[...] May 6 04:16 monthly.3/localhost/home/grante/.imapnotify.log
[...] May 5 04:17 monthly.4/localhost/home/grante/.imapnotify.log
[...] May 3 19:31 monthly.5/localhost/home/grante/.imapnotify.log
[...] May 3 03:55 monthly.6/localhost/home/grante/.imapnotify.log
[...] May 2 03:51 monthly.7/localhost/home/grante/.imapnotify.log
[...] May 1 03:51 monthly.8/localhost/home/grante/.imapnotify.log
[...] Apr 30 03:47 monthly.9/localhost/home/grante/.imapnotify.log
[...] Apr 29 03:46 monthly.10/localhost/home/grante/.imapnotify.log
[...] Apr 28 03:42 monthly.11/localhost/home/grante/.imapnotify.log
[...] Apr 27 03:42 monthly.12/localhost/home/grante/.imapnotify.log
[...] Apr 26 03:34 monthly.13/localhost/home/grante/.imapnotify.log
[...] Apr 25 03:28 monthly.14/localhost/home/grante/.imapnotify.log
[...] Apr 24 03:25 monthly.15/localhost/home/grante/.imapnotify.log
[...] Apr 23 03:20 monthly.16/localhost/home/grante/.imapnotify.log
[...] Apr 22 03:20 monthly.17/localhost/home/grante/.imapnotify.log
[...] Apr 21 03:22 monthly.18/localhost/home/grante/.imapnotify.log
[...] Apr 20 03:21 monthly.19/localhost/home/grante/.imapnotify.log
[...] Apr 19 03:21 monthly.20/localhost/home/grante/.imapnotify.log
[...] Apr 18 03:15 monthly.21/localhost/home/grante/.imapnotify.log
[...] Apr 17 03:13 monthly.22/localhost/home/grante/.imapnotify.log
[...] Apr 16 03:12 monthly.23/localhost/home/grante/.imapnotify.log

Why don't I get weekly/monthly backup?

I want daily backups going back 7 days, weekly backups going back 4
weeks, then montly backups going back 24 months [where "month" is
defined as 4 weeks]. Instead, what I get is daily backups going back
35 days.

--
Grant Edwards grant.b.edwards Yow! Those people look
at exactly like Donnie and
gmail.com Marie Osmond!!


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Grant,

I believe the problem is with your crontab entries. You should only be
running "weekly" once per 7 days and "monthly" once per month. cron is
running these every day. The man page gives this example crontab:
50 23 * * * /usr/local/bin/rsnapshot daily
40 23 * * 6 /usr/local/bin/rsnapshot weekly
30 23 1 * * /usr/local/bin/rsnapshot monthly

Hope that helps.

Steve

On 05/20/2011 04:23 PM, Grant Edwards wrote:
I've read the docs and looked at the sample config, and I still have
absolutely no clue how to configure intervals to get rsnapshot to work
right.

Here's my config file:

config_version 1.2
snapshot_root /mybook2/backups
no_create_root 1
cmd_cp /bin/cp
cmd_rm /bin/rm
cmd_rsync /usr/bin/rsync
cmd_logger /usr/bin/logger
cmd_du /bin/du
cmd_rsnapshot_diff /usr/bin/rsnapshot-diff
verbose 2
loglevel 3
lockfile /var/run/rsnapshot.pid
link_dest 1
backup /home/ localhost/
backup /etc/ localhost/
interval daily 7
interval weekly 4
interval monthly 24

According to the docs, that means keep 7 daily backups, then 4 weekly
backups, then 24 monthly (28-day months) backups. The crontab entries
look like this:

3 1 * * * /usr/bin/rsnapshot monthly
3 2 * * * /usr/bin/rsnapshot weekly
3 3 * * * /usr/bin/rsnapshot daily

But all I get are daily backups for the past (7+4+24) days. [They
have various names starting with daily/weekly/monthly, but they're all
just 1 day apart.] Weekly backups be a 7 days apart and monthly
backups should be 4 weeks apart.

Here's an exmaple listing of a file that gets modified every few
minutes:

ls -lt */localhost/home/grante/.imapnotify.log
[...] May 20 03:22 daily.0/localhost/home/grante/.imapnotify.log
[...] May 19 04:13 daily.1/localhost/home/grante/.imapnotify.log
[...] May 18 04:11 daily.2/localhost/home/grante/.imapnotify.log
[...] May 17 04:17 daily.3/localhost/home/grante/.imapnotify.log
[...] May 16 04:14 daily.4/localhost/home/grante/.imapnotify.log
[...] May 15 04:12 daily.5/localhost/home/grante/.imapnotify.log
[...] May 14 04:11 daily.6/localhost/home/grante/.imapnotify.log
[...] May 13 04:13 weekly.0/localhost/home/grante/.imapnotify.log
[...] May 12 04:14 weekly.1/localhost/home/grante/.imapnotify.log
[...] May 11 04:14 weekly.2/localhost/home/grante/.imapnotify.log
[...] May 10 04:25 weekly.3/localhost/home/grante/.imapnotify.log
[...] May 9 04:17 monthly.0/localhost/home/grante/.imapnotify.log
[...] May 8 04:18 monthly.1/localhost/home/grante/.imapnotify.log
[...] May 7 04:16 monthly.2/localhost/home/grante/.imapnotify.log
[...] May 6 04:16 monthly.3/localhost/home/grante/.imapnotify.log
[...] May 5 04:17 monthly.4/localhost/home/grante/.imapnotify.log
[...] May 3 19:31 monthly.5/localhost/home/grante/.imapnotify.log
[...] May 3 03:55 monthly.6/localhost/home/grante/.imapnotify.log
[...] May 2 03:51 monthly.7/localhost/home/grante/.imapnotify.log
[...] May 1 03:51 monthly.8/localhost/home/grante/.imapnotify.log
[...] Apr 30 03:47 monthly.9/localhost/home/grante/.imapnotify.log
[...] Apr 29 03:46 monthly.10/localhost/home/grante/.imapnotify.log
[...] Apr 28 03:42 monthly.11/localhost/home/grante/.imapnotify.log
[...] Apr 27 03:42 monthly.12/localhost/home/grante/.imapnotify.log
[...] Apr 26 03:34 monthly.13/localhost/home/grante/.imapnotify.log
[...] Apr 25 03:28 monthly.14/localhost/home/grante/.imapnotify.log
[...] Apr 24 03:25 monthly.15/localhost/home/grante/.imapnotify.log
[...] Apr 23 03:20 monthly.16/localhost/home/grante/.imapnotify.log
[...] Apr 22 03:20 monthly.17/localhost/home/grante/.imapnotify.log
[...] Apr 21 03:22 monthly.18/localhost/home/grante/.imapnotify.log
[...] Apr 20 03:21 monthly.19/localhost/home/grante/.imapnotify.log
[...] Apr 19 03:21 monthly.20/localhost/home/grante/.imapnotify.log
[...] Apr 18 03:15 monthly.21/localhost/home/grante/.imapnotify.log
[...] Apr 17 03:13 monthly.22/localhost/home/grante/.imapnotify.log
[...] Apr 16 03:12 monthly.23/localhost/home/grante/.imapnotify.log

Why don't I get weekly/monthly backup?

I want daily backups going back 7 days, weekly backups going back 4
weeks, then montly backups going back 24 months [where "month" is
defined as 4 weeks]. Instead, what I get is daily backups going back
35 days.


--
Steven M. Wilson, Systems and Network Manager
Markey Center for Structural Biology
Purdue University
(765) 496-1946


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

2011/5/20 Grant Edwards <grant.b.edwards < at > gmail.com>:
  3 1 * * *           /usr/bin/rsnapshot monthly
  3 2 * * *           /usr/bin/rsnapshot weekly
  3 3 * * *           /usr/bin/rsnapshot daily

man 5 crontab

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On 2011-05-20, Steve Wilson <stevew < at > purdue.edu> wrote:
Grant,

I believe the problem is with your crontab entries. You should only be
running "weekly" once per 7 days and "monthly" once per month. cron is
running these every day. The man page gives this example crontab:
50 23 * * * /usr/local/bin/rsnapshot daily
40 23 * * 6 /usr/local/bin/rsnapshot weekly
30 23 1 * * /usr/local/bin/rsnapshot monthly

Doh!

That's embarassing. I kept reading and re-reading the stuff about
interval specs and completely missed my broken crontab entries.

Hope that helps.

Indeed it does.

--
Grant Edwards grant.b.edwards Yow! HELLO, everybody,
at I'm a HUMAN!!
gmail.com


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

Am 20.05.2011 22:23, schrieb Grant Edwards:
I've read the docs and looked at the sample config, and I still have
absolutely no clue how to configure intervals to get rsnapshot to work
right.

Here's my config file:

config_version 1.2
snapshot_root /mybook2/backups
no_create_root 1
cmd_cp /bin/cp
cmd_rm /bin/rm
cmd_rsync /usr/bin/rsync
cmd_logger /usr/bin/logger
cmd_du /bin/du
cmd_rsnapshot_diff /usr/bin/rsnapshot-diff
verbose 2
loglevel 3
lockfile /var/run/rsnapshot.pid
link_dest 1
backup /home/ localhost/
backup /etc/ localhost/
interval daily 7
interval weekly 4
interval monthly 24

According to the docs, that means keep 7 daily backups, then 4 weekly
backups, then 24 monthly (28-day months) backups. The crontab entries
look like this:

3 1 * * * /usr/bin/rsnapshot monthly
3 2 * * * /usr/bin/rsnapshot weekly
3 3 * * * /usr/bin/rsnapshot daily

No, the crontab entry is not right, do something like this:

# Daily backup every day at 00:00
0 0 * * * /usr/bin/rsnapshot daily
# Backup on monday morning at 04:00
0 4 * * 0 /usr/bin/rsnapshot weekly
# Backup at the first of the month at 06:00
0 6 1 * * /usr/bin/rsnapshot monthly

Do a "man 5 crontab" to see the exact syntax.
But all I get are daily backups for the past (7+4+24) days. [They
have various names starting with daily/weekly/monthly, but they're all
just 1 day apart.] Weekly backups be a 7 days apart and monthly
backups should be 4 weeks apart.
Yep, that's right, it's because you do the backup daily for all
(although I'd estimate that the backup is for the last 24 days only, as
daily and weekly is covered by monthly). "monthly" is a name only, you
could also name it "foobar" and it would do the same. What counts is
what you configure in the crontab.

Best Regards,
Hermann

--
hermann < at > qwer.tk
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On 2011-05-20, Grant Edwards <grant.b.edwards < at > gmail.com> wrote:
On 2011-05-20, Steve Wilson <stevew < at > purdue.edu> wrote:
Grant,

I believe the problem is with your crontab entries. You should only be
running "weekly" once per 7 days and "monthly" once per month. cron is
running these every day. The man page gives this example crontab:
50 23 * * * /usr/local/bin/rsnapshot daily
40 23 * * 6 /usr/local/bin/rsnapshot weekly
30 23 1 * * /usr/local/bin/rsnapshot monthly

Doh!

That's embarassing. I kept reading and re-reading the stuff about
interval specs and completely missed my broken crontab entries.

Hope that helps.

Indeed it does.

OK, thinking back on it, what tripped me up was my unshakable
assumption that the "interval" configuration settings for the backups
configured the intervals of the backups.

After reading the docs and the sample config, my understanding was
that

interval daily 7
interval weekly 4
interval monthly 24

meant that a weekly backup would be done once for every 7th daily
backup, and a monthly backup would be done once every 4th weekly
backup.

The fact that there were separate crontab entries for the three should
have provided a clue that the intervals were control by crontab and
not by the interval settings. I remember thinking it odd that since
rsnaphost knew what the intervals were by counting off days/weeks I
should only have to run exactly one invokation of per day.

I now see from a previous thread that I'm not the first one to
misunderstand this, and the "interval" setting is going to be called
something else in the future.

--
Grant Edwards grant.b.edwards Yow! Are we live or on
at tape?
gmail.com


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On Fri, May 20, 2011 at 4:44 PM, Hermann Himmelbauer <dusty < at > qwer.tk> wrote:

No, the crontab entry is not right, do something like this:

# Daily backup every day at 00:00
0 0 * * * /usr/bin/rsnapshot daily
# Backup on monday morning at 04:00
0 4 * * 0 /usr/bin/rsnapshot weekly
# Backup at the first of the month at 06:00
0 6 1 * * /usr/bin/rsnapshot monthly

Do the monthies just *before* the weeklies, and the weeklies just
*before* the dailies. Those operations are simply directory renamings
and take moments, but if the daily is still running at 4:00 or 6:00
AM, the weekly or montlies will be skipped due to lockfiles.


# Daily backup every day at midnight
0 0 * * * /usr/bin/rsnapshot daily
# Rotate weeklies on Sunday night at 11:00 PM
0 23 * * 6 /usr/bin/rsnapshot weekly
# Rotate montlies on the first of the month at 10:00 pm
0 22 1 * * /usr/bin/rsnapshot monthly

In fact, if the dailies are taking a while, and you're running
multiple target hosts, it can even make sense to set up a separate
"/etc/cron.rsnapshot" to contain the cron jobs, and run things out of
that on a daily basis. with "run-parts". This keeps lengthy backup
procedures, such as new hosts, from blocking the whole backup
procedure, You can get some very helpful resource limiting this way:
the new, badly configured, 300 Gig repository filled with spew can
keep your backup system busy for a day, but the next night, the next
run of "run-parts" gets the backups to proceed against the next few
targets anway.



Do a "man 5 crontab" to see the exact syntax.
But all I get are daily backups for the past (7+4+24) days.  [They
have various names starting with daily/weekly/monthly, but they're all
just 1 day apart.] Weekly backups be a 7 days apart and monthly
backups should be 4 weeks apart.
Yep, that's right, it's because you do the backup daily for all
(although I'd estimate that the backup is for the last 24 days only, as
daily and weekly is covered by monthly). "monthly" is a name only, you
could also name it "foobar" and it would do the same. What counts is
what you configure in the crontab.

Best Regards,
Hermann

--
hermann < at > qwer.tk
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On Fri, May 20, 2011 at 08:23:59PM +0000, Grant Edwards wrote:
I've read the docs and looked at the sample config, and I still have
absolutely no clue how to configure intervals to get rsnapshot to work
right.

interval daily 7
interval weekly 4
interval monthly 24

According to the docs, that means keep 7 daily backups, then 4 weekly
backups, then 24 monthly (28-day months) backups. The crontab entries
look like this:

3 1 * * * /usr/bin/rsnapshot monthly
3 2 * * * /usr/bin/rsnapshot weekly
3 3 * * * /usr/bin/rsnapshot daily

There's your problem. You're running the "monthly" backups at 01:03
every day, weeklies at 02:03 every day, and dailies at 03:03 every day.
Try something like this ...

# 00:00 every day
0 0 * * * /usr/bin/rsnapshot daily
# 23:45 on Saturday
45 23 * * 6 /usr/bin/rsnapshot weekly
# 23:30 on the 1st of the month
30 23 1 * * /usr/bin/rsnapshot monthly

I want daily backups going back 7 days, weekly backups going back 4
weeks, then montly backups going back 24 months [where "month" is
defined as 4 weeks]. Instead, what I get is daily backups going back
35 days.

Specifying "every 28 days" isn't possible using cron. I define a month
in my backups as, well, a month. Some months are longer than others, so
I have *five* "weekly" backups.

--
David Cantrell | Godless Liberal Elitist

engineer: n. one who, regardless of how much effort he puts in
to a job, will never satisfy either the suits or the scientists

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

On 2011-05-23, David Cantrell <david < at > cantrell.org.uk> wrote:
On Fri, May 20, 2011 at 08:23:59PM +0000, Grant Edwards wrote:
I've read the docs and looked at the sample config, and I still have
absolutely no clue how to configure intervals to get rsnapshot to work
right.

interval daily 7
interval weekly 4
interval monthly 24

According to the docs, that means keep 7 daily backups, then 4 weekly
backups, then 24 monthly (28-day months) backups. The crontab entries
look like this:

3 1 * * * /usr/bin/rsnapshot monthly
3 2 * * * /usr/bin/rsnapshot weekly
3 3 * * * /usr/bin/rsnapshot daily

There's your problem. You're running the "monthly" backups at 01:03
every day, weeklies at 02:03 every day, and dailies at 03:03 every day.
Try something like this ...

# 00:00 every day
0 0 * * * /usr/bin/rsnapshot daily
# 23:45 on Saturday
45 23 * * 6 /usr/bin/rsnapshot weekly
# 23:30 on the 1st of the month
30 23 1 * * /usr/bin/rsnapshot monthly

I want daily backups going back 7 days, weekly backups going back 4
weeks, then montly backups going back 24 months [where "month" is
defined as 4 weeks]. Instead, what I get is daily backups going back
35 days.

Specifying "every 28 days" isn't possible using cron.

Yup, I knew that. I thought the interval configuration settings
configured the intervals.

--
Grant





------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss