New Projects - Fresh from the Labs
Ever made a mistake, deleted or overwritten something, and wanted to go back a day? This might be the tool for you. According to the project's Freshmeat entry:
Back In Time is a simple backup system for Linux (GNOME and KDE4) inspired by the flyback project and TimeVault. The backup is done by taking snapshots of a specified set of directories. All you have to do is configure where to save the snapshot, what directories to back up, and when a backup should be done (manually, every hour, every day, every week or every month). It acts as a user-mode backup system. This means you can back up and restore only folders to which you have write access.
If you check out the Web site's download page, it has instructions to integrate repositories for Ubuntu and Fedora, where you can install the packages straight from your system's package manager. If you don't have either of these distros though (or prefer to compile it), the source is available too. The link where these are found is misleadingly marked “You can download older versions here” on the main downloads page (you actually can get the latest source tarballs from this section too, newer than the main binaries).
If you're going with the binaries, you'll have to install the available common package first, and then install either the GNOME or KDE4 package, depending on your preference. If you choose to run with the source tarball, installation is surprisingly easy. Download the tarball, extract it, and open a terminal in the folder. Enter the command:
$ sudo ./install-common.sh
This first step installs the base of the program (not the GUI) and requires that you have Python and rsync installed.
If you want to run with GNOME, enter:
$ sudo ./install-gnome.sh
It now will be ready to run under GNOME and requires python-glade2, python-gnome2 and meld.
For KDE, enter:
$ sudo ./install-kde4.sh
The KDE option requires x11-utils, python-kde4 (>= 4.1) and kompare. Once the installation is finished, you can run the program by entering:
Once you're inside, Back In Time is a pretty basic affair. On a first-time run, it starts off with the Settings Dialog, where you define where the backup snapshots are saved, what folders to back up and how often to do it (among other features).
Start with where to back up. You'll see the General tab first, and the first field will let you choose where to save the snapshots of what you want backed up. Below that is the drop-down box for how often you want snapshots updated, which has the choices of disabled (you'll have to do it yourself), every five minutes, ten minutes, hour, day, week or month. I've got mine set to every ten minutes. It checks to see whether there are any folder differences, and if so, it takes another snapshot.
Click on the Include tab, and you can define what actual folders you want backed up in your snapshots. I've got my desktop being backed up in snapshots, which are in the form of separate folders in my home directory, under backups. Every time there's a change, a new folder is made, each with a different date and time code, allowing me to backtrack accurately if I need to retrieve something. Other tabs include more advanced options, such as excluding certain files and the like, but I'll let you explore that yourself.
All in all, Back In Time is a very simple application that is best used on smaller folders that you work with a lot. As a musician with my own recordings, I have a lot of music files being constantly altered, and quite often, I make silly mistakes that result in files being irretrievable. Back In Time is invaluable for such circumstances. If you're chasing something super-advanced with a lot of wizz-bang features that work system-wide, this probably isn't it, but for those who want something simple for use on a small scale, it's ideal.
John Knight is the New Projects columnist for Linux Journal.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Three More Lessons
- Django Models and Migrations
- August 2015 Issue of Linux Journal: Programming
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Huge Package Overhaul for Debian and Ubuntu
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile