A Differential Backup with Mondo

This was originally posted on my family blog on 4/7/06. I will be slowly moving the geeky stuff from there to this blog.

I broke out the mondo man page. To verify my little backup, and see what has changed since I made it, I ran this:

mondoarchive -V -i -I "/home/bryan/Documents" -d '/mnt/home/backup3' -g -s '700m'

I had made a little change in a text file, and it flagged it and told me. I just noticed that it says the -I switch is ignored if you are just verifying. Oh well.

Now, to do the actual differential backup I ran this command:

mondoarchive -O -i -D -I "/home/bryan/Documents" -d '/mnt/home/backup3' -g -s '700m'

For backing up one little text file it still took a while because it seemed to re-generate the boot disk. I think I saw an option in the manual to not do that, but it was highly recommended that you don't use that option. Anyway, looking at the backup directory, it seems to have overwritten the full backup iso with the differential. The restore only restores the changed file (and some empty directories, hmm). So, don't save the differential in the same place as the original? How do I tell it which is the orignial backup to start from when doing the differential then?

OK, a little digging around and I discovered some emails that explain how the differential backups are done: Mondo Differential backup, Mondo Differential/Incremental BU?, and this one helped a bit too, Mondo Differential backups on two different sets. Basically, the file list and timestamp of the last backup is stored in /var/cache/mondo-archive/, so you can specify any destination you want and it knows what to base the differential off of. I still need to try this, but my 2 year old is pulling on my away at the moment.

Comments

Anonymous said…
Your links go all over the place, but none of them to the relevant article.
April 20, 2013 at 11:24 AM
Bryan said…
Wow, you're right. I guess sourceforge has change some things since I wrote this back in 2006. Sorry.
April 20, 2013 at 1:30 PM
Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more