Differences

This shows you the differences between two versions of the page.

--- primer:introduction [2017/05/29 15:01] – Gerard Nicol
+++ primer:introduction [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Overview ======
+====== TapeTrack Primer ======
-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.
+The purpose of this section is to describe the history, design methodology and benefits of TapeTrack.
-===== What is 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.
-===== Who uses TapeTrack =====
-===== What is the history of TapeTrack =====
+===== What is TapeTrack? =====
-===== What are the TapeTrack Components =====
+TapeTrack is computer software designed specifically for the purpose of managing computer backup tapes.
+===== Why do you need TapeTrack? =====
+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:
+  - [[definitions:backup_software|Backup software]] focusses on writing data to tapes and only keeps an inventory of tapes that it knows about.
+  - [[defintions:robotic_library|Robotic Libraries]] only know about the tapes in their slots, and don't know which tapes are expected to be in the library.
+  - Tapes that are outside [[defintions:robotic_library|Robotic Libraries]] have no software at all to keep track of them in racking units.
+  - [[definitions:offsite_vendors|Off-site vendors]] know about the tapes they have (ideally) and sometimes they make mistakes.
+  - When ejecting tapes, sometimes the library misses tapes, or ejects tapes that aren't part of the batches that are being sent off-site.
+  - There is no way of tracking unbarcoded tapes before they are used.
+  - There is no one list of every ever tape owned by the enterprise.
+  - There is no history of the movements of each tape that includes which [[dictionary:operators|operators]] touched them.
+  - There is no way to ensure that each robotic library (or [[dictionary:virtual_library|virtual library]]) has enough [[dictionary:scratch_tape|scratch tapes]] to get through the backup workload.
+===== What is the TapeTrack Workflow =====
+{{:primer:tapetrack-lifecycle.png|500}}
+===== Who uses TapeTrack? =====
+TapeTrack is used by over 4,000 enterprises around the world.
+These enterprises fall into the following categories:
+  - Data protection companies who store backup tapes on the behalf of multiple other companies (a list of these companies can be found [[general:partners|here]]).
+  - The direct customers of data protection companies who use TapeTrack both manage their on-site tapes, and the tapes stored offsite with their vendor.
+  - Data Center customers who manage their own on-site and offsite tape inventories.
+  - 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.
+===== What is the history of TapeTrack? =====
+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 [[general:gazillabyte|GazillaByte LLC]].
+===== What is the design methodology of TapeTrack? =====
+TapeTrack is designed around the 5 Pillars of Tape Management:
+  - [[primer:asset_management|Asset Management]]: A complete list of every single tape.
+  - [[primer:chain_of_custody|Chain-of-Custody]]: Where each tape has been and who has touched it.
+  - [[primer:library_management|Library Management]]: Where each tape needs to be.
+  - [[primer:disaster_recovery|Disaster Recovery]]: Are all my critical tapes offsite?
+  - [[primer:quality_control|Quality Control]]: Am I managing my tapes properly?
+===== TapeTrack Jargon =====
+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  [[object:volume_target|Target]] [[object:repository|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 [[object:volume_target|Target]] [[object:repository|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 [[object:volume|Volume]] will move to the Next Repository.                                                                                                                                                                                                                                                                                         |
+| Next Repository   | The [[object:repository|Repository]] defined as the ''Next Repository'' for a given [[object:repository|Current Repository]].                                                                                                                                                                                                                                          |
+| Overdue           | A tape was put into a move status and the maximum allowable time for the [[object:repository|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 [[object:volume|Volumes]], and to confirm any pending incoming movements.                                                                                                                                     |
+| Synchronization   | The process of setting the Target location of a [[object:volume|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, [[object:volume|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.
+===== What are the TapeTrack Software Components? =====
+TapeTrack Software falls into the following categories:
+  * [[primer:server|TapeTrack Framework Server]].
+  * [[primer:clients|TapeTrack Windows Clients]].
+  * [[primer:cli|TapeTrack Command Line Clients]].
+  * [[primer:webservices|TapeTrack Web Services]].
+  * [[primer:mobile|TapeTrack Mobile Software]].
+  * [[primer:extensions|TapeTrack Extensions]].
+===== What are the TapeTrack Subsystems? =====
+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:
+  * Alerting.
+  * [[subsystem:barcode|Barcode Management]].
+  * [[subsystem:certification|Certification]].
+  * Consignment Control.
+  * Catalog Management.
+  * [[subsystem:disasterrecovery|Disaster Recovery]].
+  * Reporting.
+  * [[subsystem:simplemanagement|Simple Management]].
+  * [[master:slot_block|Slot Management]].
+  * [[subsystem:stockcontrol|Stock Control]].
+===== What are the TapeTrack Objects =====
+  * [[object:customer|Customer]].
+  * [[object:media|Media Type]].
+  * [[object:volume|Volume]].
+  * [[object:repository|Repository]].
+  * [[object:data_cluster|Data Cluster]].
+  * [[object:simple_management|Simple Management Rule]].
+  * [[object:user|User]].
+===== How often are new versions of TapeTrack Released? =====
+TapeTrack software is released quarterly, and the version numbers reflect these releases:
+  * Q1 Major Release is released in January of each year.
+  * Q2 Minor Release is released in April of each year.
+  * Q3 Minor Release is released in July of each year.
+  * 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 becomes more than 2 years behind the current release.