Backup Conversions: Page 2 of 2

To some extent this is further justification for disk archiving, as we describe in our article "Backup vs. Archive". A disk-based archive resolves the retention issues and keeping the old software product under maintenance. This is especially true if your archive is stored in a non-proprietary format as a disk archive should allow you to do.

Why don't backup software vendors make a conversion utility? Clearly most of the popular tape formats can be read, there are more than a few utilities that will for one purpose or another read a variety of tape vendor's tapes. The harder task is to move all those backup policies and jobs from one environment to another, but again utilities exist that read those settings as well and although I don't know anyone that converts custom scripts, it can be done.

While I'll admit that a conversion or import utility would not be a small undertaking, it would certainly eliminate the biggest obstacle most customers face in switching backup applications -- the time and effort required to do so.

Ideally when installing a new application it should offer to import all the tape, indexes, jobs and policies of the prior application, then give you the option of what to keep and what to throw out. Even further intelligence can be added to tell you what policies you don't use any more, are redundant or are in conflict with other polices. This would allow you to use your conversion time to do spring cleaning.

I agree with backup software suppliers that customers want more from their backup applications, but until switching backup applications is about as painful as switching word processors customer conversion is going to come at a slow pace.