SCSI Media Changer and Backup Device Control System

mtx is a set of low level driver programs to control features of SCSI backup related devices such as autoloaders, tape changers, media jukeboxes, and tape drives. It can also report much data, including serial numbers, maximum block sizes, and TapeAlert(tm) messages that most modern tape drives implement (to tell you the exact reason why a backup or restore failed), as well as do raw SCSI READ and WRITE commands to tape drives (not important on Linux, but important on Solaris due to the fact that the Solaris tape driver supports none of the additional features of tape drives invented after 1988). mtx is designed to be a low level driver in a larger scripted backup solution, such as Amanda or BRU Professional. mtx is not supposed to itself be a high level interface to the SCSI devices that it controls.

This version has the following features:

This program supposedly supports FreeBSD, Solaris, Linux, and IRIX. Tru64 Unix and VMS are probably irretrievably broken at this time. This program has been tested under FreeBSD, Solaris, and Linux, and there only with a limited set of hardware:

Source Code

The current source code is: RPMs may be available from the following place: A .spec file is now included in the 'mtx' distribution for building your own RPM's.

Note that RPMs are courtesy of Kenneth Porter, who should be contacted regarding rpm-related problems.

Leonard Zhubkoff's original (obsolete) source code is:

Always check the directory ftp://ftp.estinc.com/pub/unsupported/ before believing anything that you read here.

Known Bugs And Limitations

Philosophy

The Unix philosophy is "many small tools chained together". mtx supplies those small tools so that you can create your own backup and recovery tools by chaining mtx pieces together, whether it be with /bin/sh, Perl, Python, or CAML.

Future

mtx 1.2 will continue to have enhancements done to its core functionality as long as there is demand.

mtx 2.0 is once again back into planning stages. The biggest change envisioned for mtx 2.0 is a major change in the way that it handles the low-level device interface to allow multiple interfaces. The main reason for this is to allow NDMP loader support (not that I have a NDMP loader at present, but the NDMP standard definitely allows for them to exist!). This should also make it possible to program a distributed backup system using mtx 2.0.

Some other things envisioned for mtx 2.0:

Support

See Also:


Maintained by Eric Lee Green
Hosted by VA Linux's SourceForge

Last modified: Mon Apr 23 12:39:08 MST 2001