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 is 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.
Each enterprise has unique tape infrastructure, and has developed unique tape management processes, but generally speaking, you need TapeTrack because each of the components involved in the tape management process only provide very narrow functionality:
TapeTrack is used by over 4,000 enterprises around the world.
These enterprises fall into the following categories:
The first version of TapeTrack was released in 1999, and the product has been continually developed since that date with 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.
TapeTrack is designed around the 5 Pillars of Tape Management:
TapeTrack has a whole bunch of terms that you should familiarize yourself with.
Term | Description |
---|---|
Adapter | An ODPAPI web service interface, represented by a URL address. The TapeTrack ODPAPI Adapter allows TapeTrack App software or user written queries to interface with TapeTrack via a convenient REST interface. |
Confirmation | The process of telling TapeTrack that a tape is now in its Target Repository. |
Current Location | The location where a tape is believed to be, or in the case of a moving tape, the starting point at which the tape may be (i.e. the tape is somewhere between the Current and the Target location). |
Client | A TapeTrack software component used for interfacing with the TapeTrack Framework Server. |
Mirroring | The process of replicating selected TapeTrack objects from one TapeTrack Framework Server to another. This is often used by data centers who run their own TapeTrack system globally and wish to keep their offsite vendor's TapeTrack up to date in a local location. |
Movement | The process of requesting a tape be moved from one location to another (updating the Target Repository). |
Move Status | A tape that has been identified as having to move from one location to another (i.e. the Target location does not equal the Current location). |
Next Move Date | The date at which a Volume will move to the Next Repository. |
Next Repository | The Repository defined as the Next Repository for a given Current Repository. |
Overdue | A tape was put into a move status and the maximum allowable time for the Target Repository, or the tape specifically (if specified) has elapsed (i.e. a tape is moving from the TS3500 to the on-site racking, the on-site racking has a threshold move allowance of 10 hours, and the tape was put into a move status more than 10 hours ago). |
Reconciliation | The process of comparing an external inventory (such as an offsite vendor list or ATL query output for the purpose of ensuring that there are no missing Volumes, and to confirm any pending incoming movements. |
Synchronization | The process of setting the Target location of a Volume based upon a the value of a field, or combination of fields in an external backup product. |
Target Location | The location that a tape should ultimately/ideally be found in. |
Volume | An individual asset that is tracked within the TapeTrack software, examples include LTO cartridge, CD, DVD, hard drive etc. |
An example sentence using TapeTrack Jargon:
When I came in this morning, Volume 000001L5 had a current location of the SL8500 Library, but then the Synchronization task ran against TSM, and updated the target location (putting the tape into a Move Status from the SL8500 to Iron Mountain). Later that day, when the Reconciliation task ran, we noticed that the tape was not yet confirmed at Iron Mountain, and as a result had been marked as Overdue. We contacted Iron Mountain and confirmed that the tape has arrived but had not been scanned into SecureSync. We later re-ran the reconciliation and the tape was confirmed as being at Iron Mountain.
TapeTrack Software falls into the following categories:
While TapeTrack is designed around the 5 Pillars of Tape Management, it is comprised of many interconnecting sub-systems. These subsystems work together to automate the process of tape management.
These sub-systems are:
TapeTrack software is released quarterly, and the version numbers reflect these releases:
We recommend that users upgrade at least once per year to the Major release and that no user becomes more than 2 years behind the current release.