Home Backup with Mondo Rescue

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

I'm playing with Mondo Rescue for backing up my hard drive. Here are some quick notes of the experience so far.

I ran a basic mondoarchive "gui" session, and accepted all defaults, except that I excluded /mnt from the backup. It asked for a max iso size, I didn't ever plan to burn these to anything, but I put in 700 MB because I didn't know what else to do. I backed up to hard drive (the unused hd on my system). It spent about 13 hours working, created 50 isos and then quit. I didn't see it quit, and from the log it looks like it gave up with the message "too many isos." No kidding.

Now I'm attempting to restore a single file. I typed mondorestore. The "gui" started up and told me to insert the boot disk. I just hit enter and it went to a menu asking what to restore from. I chose harddrive. It asked for the path to my isos. I gave it the path and it took off and after some work it showed me a file list from which I could select what I wanted to restore. I dug down and selected a single rpm file from my downloads directory (something that never should have been backed up, but oh well). It then asked me where to restore to, so I gave it a path on the (previously) unused hard drive. It's now chugging through all 50 isos looking for the file, telling me, "This may take some time." No kidding! OK, I was watching and it finished with an error in the middle of trying to do something with my large files:

# mondorestore
---FATALERROR--- Mommy!

However, it did restore the one file I asked it to!

I'm feeling pretty darn good about mondo at this point. It seems super easy to use, and does what I want. I think I'll be able to skip backing up some key directories, such as my music, and get a manageable set of stuff so it won't have to create too many isos and have these problems.

Things to try just to be sure:

  • Only back up some stuff on my hard drive (try to get way fewer isos).
  • Make sure the restore from the smaller backup works.
  • Try out the differential backup feature.

Comments

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