![]() ![]() Unfortunately even its diffing ability in this situation was lacking. ![]() I found and tried Boar, a versioning system which attempts to work well for binary files. Git turns out to have a sensible maximum file limit, which was a pretty big “hey idiot… what are you doing” warning. Then I’d point CrashPlan at the associated repository which would be backed up in the background. One thought I had was that before launching the virtual machine in a batch file or script I’d commit the vdi it to a version control system. I really wanted some kind of diff-based approach to backing up the large file. I tried all kinds of hair-brained schemes to backup my virtualbox image in something resembling automatic. How can I have any guarantee that that image is in any kind of consistent state? Backing Up With A Versioning System This is, of course, problematic as CrashPlan is most likely running its backup while I’m actively working in my virtual machine. ![]() However, the dumb me was just pointing CrashPlan at the directory with my virtual machine images and hoping for the best. Here at work we use CrashPlan which seems to do a decent enough job automatically backing up the directories I tell it to. The most important thing I want to backup is my Ubuntu VirtualBox image. I needed to make sure my backup strategy was solid. This is the second time in a month this has happened. And now to the fun subject of virtual machine images! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |