Understanding rSnapshot
The only job that does any data copy is the lowest common denominator.
If you have hourly jobs, then this is hourly.0.
If you are only doing daily's, then its daily.0
Everything else is just re-organisation, shifting the folders further and further back into time!
i.e Monthly.5 (6months old), is simply the same folder that was once called daily.0. And one called daily.4. And once called weekly.3. etc. Eventually is may become yearly.1 (two years old!!)
An example:
Monday, at 11pm runs a daily snapshot.
- This makes a snapshot of the source folders.
- It is called daily.0
Tuesday, 11pm, again the daily runs
- This moves daily.0 to daily.1
- It then makes a new daily.0, and as above, is a snapshot of the source folders
Come sunday, we have 7 backups, daily.0 through to daily.6.
Daily.6 is the oldest daily backup.
At 10pm, a weekly job runs. Daily.6 gets moved to weekly.0
Further to note, is what actually gets historically backed up.
This one is hard to explain.
If we have daily snapshots, then the oldest daily snapshot, daily.6, gets moved to weekly.0
This means that if a file was created in daily.3, and deleted in daily.4, then the file does not get included in the weekly backup.
As soon as the next cycle of daily backups comes around, daily.3 will get deleted, and the file is gone forever.
rSnapshot does not 'roll-up' all 7 days of snapshots and stash them away into the weekly snapshot. For that matter, I strongly doubt that any retention system would! ??
Realisticly, what kind of backup system would be able to actually store all changes, right down to the daily level?
i.e
Monday: daily.0. By sunday, this has become daily.6
weekly sunday, 10pm: daily.6 becomes weekly.0. Daily.6 will be from the previous monday
monthly, 1st day of month: weekly.4 becomes monthly.0. Monthly.0 will be that first monday.
When a weekly is taken on sunday, it will contain snapshot of the first monday from a week ago (the start of the 7day daily cycle).
When a monthly is taken, on the 1st, it will contain snapshot of the first week, from a month ago (the start of the 4 week weekly cycle)
When a yearly is taken, it will contain the first month, from a year ago.
This cycle is interupted if the comand is run manually, i.e if you ran 'rsnapshot weekly' 4 times, just before the 1st of the next month, then the next months snapshot would contain the weekly that you ran manually.
Michael.
On Mon, Jun 20, 2011 at 4:18 PM, Marc Weber <marco-oweber < at > gmx.de ([email]marco-oweber < at > gmx.de[/email])> wrote:
I find it hard to understand what the tool does. Do I have to start
reading code in order to understand what to do?
Docs say:
time, with each additional line getting successively larger. Thus, if
you add a yearly interval, it should go at the bottom, and if you add a
minutes interval, it should go before hourly. It's also worth noting
that the snapshots get pulled up from the smallest interval to the
largest. In this example, the daily snapshots get pulled from the oldest
hourly snapshot, not directly from the main filesystem.
What does "pulled" mean exactly? How does it relate to cron-jobs or
starting rsnapshot manually (cause I could be backing up to USB
storage which is plugged in occasionally only?)
So does an interval "manual" exist or such?
Marc Weber
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
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
