| October 26, 2009 12:16 pm

One of the upsides of open source software is that it largely sales itselfImagine how awesome it would be if this announcement read: “Time Drive has been completely rewritten from scratch (yet again) to take better advantage of the paradigms of modern computing!  Version 0.3 has hundreds of updates and new features which will make your life easier and more fulfilled!”

There’s just one little problem … such an announcement wouldn’t necessarily be true.  (Marketing hyperbole, I never knew thee!)

The truth is this: Time Drive is a simple backup program that does a good job of backing up your data.  It offers a nice list of potential backup options ranging from an attached hard drive to a computer over the network or across the internet.  It makes it easy to search for and restore a lost file.

In short, Time Drive seeks to change the world by making an act of computer maintenance more convenient.  I’d like to think that it Just Works.

But the real test of a program isn’t how well it works, but how easy it is to fix when broken.  A good program does what you want, but a better program helps you get back on track when things go wrong.  Back when I was looking at other backup programs available for Linux, this was my number one frustration.  Most of the applications would work (for the most part), but I could never troubleshoot or repair problems when they happened.  There just wasn’t enough information available.

For an example, let’s take SBackup.  It’s a lovely little program,  with one horrible flaw.  You have absolutely no way of knowing if it is working.  It doesn’t keep log files, it doesn’t notify you if a backup job failed.  It doesn’t let you know if it is running.  Its simplicity is actually symptomatic of a flaw: it’s incomplete.

These were problems that I desperately wanted to avoid with Time Drive.  And now that I’m announcing version 0.3 of the program, I’d like to think that I have.  So, instead of marketing hyperbole and false promises, here’s the real announcement:

Time Drive 0.3 includes a number of refinements that make it easy to both backup your data and to figure out why a backup might have failed.  It’s better, easier and more refined.  In the rest of this post, I’ll explain why.

Better

There’s a reason why Time Drive works with the Ubuntu notifications system and has progress bar notifications for nearly everything.  From the very first, I wanted the program to notify the user of what it was doing.  But in versions 0.1 and 0.2, there was an essential part missing: some kind of program log.  It was a big omission, and several people complained rather vocally about it.

Logs and Notifications

And it’s the first thing that was added to version 0.3.  Time Drive now logs its activities and will notify you of errors that happen behind the scenes.  If a backup job fails silently, you can put on your detective hat and go find out why.  If your internet connection cuts out while using cron to automatically backup your computer, you’ll get a warning the next time that you run the program.  Backup statistics, problems, errors, even love notes; they’re all there.  To open the log, just click on the blue information button on the main user interface.

Time Drive 0.3 - Log

Progress Indicators for Absolutely Everything

In addition to the log, we fixed a second oversight.  Versions 0.1 and 0.2 lacked an indicator that told you how far a backup job had progressed.  In 0.3, that problem’s been solved.

Time Drive 0.3 - Backup Running Progress

Time Drive - CleanupEasier

Great.  Time Drive does a better job of letting you know about problems, but what about fixing them?  For example, what will version 0.3 do when a backup job fails, or your internet connection cuts out at the wrong time?  When these things happen, Duplicity leaves unneeded files on the backup drive.  (Files, by the way, which are a pain to remove.)  How does Time Drive make repair jobs easier?

Well … I’m glad that you asked.  Time Drive now has a cleanup function.  If it detects a mess or unneeded files, the program will automatically go about restoring things to right.  And if you happen to be one of those obsessively tidy people, you can manually run the same tool by going to the advanced settings pane for the corresponding folder.

Time Drive 0.3 - Manage Backups

More Refined

So much for better notifications and easier management of messes.  But what about the promised refinements?  Where can you look to find those?

For starters, take a look at the settings for remote connections.  All of the input boxes have been reworked for cleaner input.  While Time Drive and Duplicity have always supported non-standard port numbers, it wasn’t necessarily clear how how to configure them.  Now, it is.

More importantly, though, the user interface adapts to your choices.  If you choose to make a backup to an attached drive, you aren’t going to be asked for a server and port.  If you choose FTP, however, those options will be there.  Best of all, you no longer have to keep track of which types of connections require two slashes in the connection url and which one uses just one.  Time Drive will  do the configuration and accounting for you!

 Time Drive 0.3 - Refined Input Dialog

Looking Toward the Future

And those are only the changes that you will see.  There’s a lot more that has happened behind the scenes to make version 0.3 the best release of Time Drive ever.  You might call these “future enhancements.”  They include:

Additional Announcements

As you can see, Time Drive is managing to evolve and add new features at a pretty good clip.  But as we do so, it’s also time to face a pretty harsh reality.  An easy to install and compatible Windows version simply isn’t going to happen.

Producing a version of Time Drive for Windows has always been extraordinarily hard, there are just too many *nix dependencies.  To use it requires Cygwin, a compatible version of PyQt and a great deal of black magic and prayer.  Changes that are compatible with Mac OS X and Linux break the Windows version, and vice versa.  After months of wrestling with it, I’ve decided that It’s just not worth the headache.  So, from version 0.3 onward, we will not be targeting Windows as a development platform.

For those of you waiting with baited breath for a Windows release, my apologies.  But I should point out that Time Drive isn’t really needed on Windows.  There are a number of fantastic backup programs available.  The built-in backup is actually quite good in, and if that doesn’t suit your fancy there are some really fantastic commercial alternatives.

Conclusion

In summary, version 0.3 is a nice, incremental release of Time Drive.  It patches some important holes and does a much better job of notifying users of what’s going on.  It’s easier to manage your backups and clean up disasters.  Lastly, it’s more refined with a bunch of spectacular back end improvements.  So while version 0.3 may be an incremental improvement, we’ve got a foundation that will let us release even better versions in the future.  This announcement might not be filled with marketing speak and exaggerated claims, but you can bet that future announcements will do a used car salesman proud.

Comments

7 Responses to “Time Drive 0.3: Better, Easier, More Refined”

[…] More info about the new release can be found here. […]

Time Drive - outil de backup complet | WebDevOnLinux sent a pingback on October 27, 2009

[…] : http://blog.oak-tree.us/index.php/2009/10/26/time-drive-03 Time Drive – outil de backup complet A lire égalementVous pouvez continuer votre lecture sur […]

[…] this is where Time Drive has been for the better part of six months.  Ever since releasing version 0.3, there have been few changes to Time Drive.  Sure, both Philippe DeLodder (the other amazing Time […]

comboy wrote a comment on December 17, 2011

You are writing with much sense but:
1. No big DOWNLOAD NOW button here
2. Link to API doc does not work
3. When I finally got to http://www.oak-tree.us/time-drive/ download link does not work there either 🙁

Jan wrote a comment on March 8, 2012

great work! i have installed it and it seems to work as expected! Thank you for saving my files! 🙂

Rob Oakes wrote a comment on March 8, 2012

Hi Jan,

No problem. I’m glad that you’ve found it useful!

Cheers,

Rob

GlockG20 wrote a comment on May 17, 2012

OpenSuSE 11.4 x86-64

Doesn’t work, throws the following errors and I don’t know how to address them.

$: time-drive
/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)
Traceback (most recent call last):
File “/usr/local/bin/time-drive”, line 29, in
main()
File “/usr/local/bin/time-drive”, line 24, in main
window = MainWindow()
File “/usr/local/lib/python2.7/site-packages/timedrive/app.py”, line 35, in __init__
gui_utils.loadUi(self, “uiMainWindow.ui”)
File “/usr/local/lib/python2.7/site-packages/timedrive/utils/gui_utils.py”, line 45, in loadUi
uic.loadUi(utils.find_file(uiFile), self)
File “/usr/lib64/python2.7/site-packages/PyQt4/uic/__init__.py”, line 220, in loadUi
return DynamicUILoader().loadUi(uifile, baseinstance)
File “/usr/lib64/python2.7/site-packages/PyQt4/uic/Loader/loader.py”, line 71, in loadUi
return self.parse(filename, basedir)
File “/usr/lib64/python2.7/site-packages/PyQt4/uic/uiparser.py”, line 871, in parse
document = parse(filename)
File “/usr/lib64/python2.7/xml/etree/ElementTree.py”, line 1176, in parse
tree.parse(source, parser)
File “/usr/lib64/python2.7/xml/etree/ElementTree.py”, line 646, in parse
source = open(source, “rb”)
IOError: [Errno 2] No such file or directory: ‘None’

Care to comment?