From: Scott H. <sc...@do...> - 2006-02-08 19:50:09
|
On 2/8/06, Michel Gallant <su...@mi...> 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 |