The purpose of this section is to describe the history, design methodology and benefits of TapeTrack.

It is not required reading, but it might provide users with some insight into how to get the best out of their use of the product; it effectively a FAQ of the non-technical questions we are asked from time-to-time.

TapeTrack is computer software designed specifically for the purpose of managing computer backup tapes.

TapeTrack is used by over 4,000 enterprises around the world.

These enterprises fall into the following categories:

1. Data protection companies who store backup tapes on the behalf of multiple other companies (a list of these companies can be found here).
2. The direct customers of data protection companies who use TapeTrack both manage their onsite tapes, and the tapes stored offsite with their vendor.
3. Data Center customers who manage their own on-site and offsite tape inventories.
4. Data Center customers who manage their own on-site inventories and use the services of a data protection company who do not offer TapeTrack services.

The first version of TapeTrack was released in 1999, and the product has been consistently developed and since that date with the input from a growing customer base.

The original developer of TapeTrack was Tape Management Services Pty Ltd, who then became TapeTrack Pty Ltd, and is now GazillaByte LLC.

TapeTack is designed around the 5 Pillars of Tape Management:

1. Asset Management (a complete list of every single tape)
2. Chain-of-Custody (where each tape as been and who has touched it)
3. Library Management (where each tape needs to be)
4. Disaster Recovery (are all my critical tapes off-site)
5. Quality Control (am I managing my tapes properly)

TapeTrack software is released quarterly, and the version numbers reflect these releases:

1. Q1 Major Release is released in January of each year.
2. Q2 Minor Release is released April of each year.
3. Q3 Minor Release is released July of each year.
4. Q4 Minor Release is released in October of each year.

We recommend that users upgrade at least once per year to the Major release and that no user become more than 2 years behind in their current release.