Thanks for the explanation. Let me see if I have this correct.
If daily takes the
oldest hourly when rotating, then if I run daily at the end of the day, it contains a snapshot of how the servers were at the
beginning of the day, correct? I was confused as I figured running daily at the end of the day would give me a snapshot of how the servers were at the end of the day.
Now when I run my weekly, it will shuffle my oldest daily over to weekly, so that weekly.0 will contain a snapshot of how the servers looked at the beginning of the week? And at the end of the month, I will run monthly, and it will take my oldest weekly and move it over the monthly.0, so that monthly.0 is a snapshot of my servers at the beginning of the month?
This is all a foreign way of thinking for me. I'm thinking that if I do a daily at the end of the day, it should give me a snapshot for the end of that day.
My current crontab is as follows
0 */12 * * * root /usr/bin/rsnapshot hourly
15 23 * * * root /usr/bin/rsnapshot daily
45 22 * * 1 root /usr/bin/rsnapshot weekly
00 22 1-7 * 1 root /usr/bin/rsnapshot monthly #first monday of the month for future HD rotation plan
Scott Hess wrote: On 2/8/06, Michel Gallant <support < at > mindsweep.ca> ([email]support < at > mindsweep.ca[/email]) wrote:
Just another quick question. My backups take around 2 hours to run,
about 30 minutes for the cp -al phase, then abount 1.5 hours for the
various rsyncs through rsyncd and ssh from remote servers. I assume
that this is reasonable for about 160GB of many small files. What
should I look out for when scheduling my backups? I assume that if I
ensure that my dailies run about 2.5 hours after my hourlies, and that
my weeklies run about 2.5 hours after my dailies, etc, I should be ok,
correct?
Note that only the hourly does the rsync. So a daily looks like:
- delete the oldest daily (probably on the order of your cp -al).
- mv newer dailies up.
- mv oldest hourly to daily.0.
Likewise for weeklies, monthlies, etc. So I schedule my _longest_
cycle first. Say we're at a point where we're going to do weekly,
daily, and hourly. In that case, I do weekly first, so delete the
oldest weekly and shift things. Then the daily doesn't have an
oldest, so there's nothing to delete, likewise with hourly. Though
you can't really rely on this (on nights with no weekly, the daily
will have to do the big delete, so you can't go back-to-back).
Another solution which people have used is to have a single script
which figures out the right thing to do based on time, and then runs
the weekly, daily, hourly one right after the other if appropriate.
-scott
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
[url=http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642]http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642[/url]
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
