Differences

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

--- sync [2021/06/01 22:33] – [How does synchronization work?] Scott Cunliffe
+++ sync [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Sync Introduction ======
+====== TapeTrack Sync ======
+TapeTrack's Synchronization Suite is a powerful toolkit that allows you to synchronize fields within TapeTrack based upon the values of fields within your backup or tape management software.  This allows you to keep data in TapeTrack up to date with the Volumes status' in your backup software using an automated process.
-This guide has been written to assist those responsible for tape management with the process of integrating their backup software or tape management system with the TapeTrack Media Management Software.
+It provides the following functions:
+  * Adding new Volumes.
+  * Setting Volume locations.
+  * Updating Volume descriptions.
+  * Setting Scratch status.
+  * Setting Next Move Dates.
+  * Importing Last Write Date.
+  * Add or remove Encrypted flags.
+  * Set Data Cluster.
+  * Add Volumes to a Container.
+  * Alerting when tapes are not in the library that should be.
+  * Alerting when tapes are in the library that should not be.
-For those who have their own TapeTrack Framework Server, these instructions relate to connecting to your own system, while, for those who use TapeTrack via a relationship with their data protection provider, these instructions relate to connecting into your vendor's system.
+===== Supported Platforms =====
+  * Windows.
+  * Linux Intel, Arm, Z.
+  * AIX.
+  * HPUX.
+  * Solaris (SPARC and Intel).
+  * iOS (via PASE).
+  * zOS (via USS).
+===== Technical Support =====
+TapeTrack Software is commercially supported by a full time help desk staff.
+If you are experiencing problems or want some advice on how to configure or use the product, please see the [[common:support_details|Accessing Technical Support]] page.
 ===== Prerequisite knowledge =====
@@ Line 13: / Line 38: @@
   * Experience with the backup software you are synchronizing.
   * Experience with Windows DOS batch scripting, or UNIX shell scripting.
-===== What's in this document =====
-This document will:
+===== Sync Guide =====
-  * Describe what synchronization is from a TapeTrack perspective,
-  * Outline the benefits of synchronizing TapeTrack with your backup software,
-  * Outline the prerequisites and components required for synchronization,
-  * Provide a reference for the synchronization definition language, and,
-  * Provide examples of integration with various backup software solutions.
-===== Quick-start =====
-The goal of this document is to be comprehensive reference. In the event that the reader is under time constraints, the following sections should be sufficient to implement synchronization:
+This guide has been written to assist those responsible for tape management with the process of integrating their backup software or tape management system with the TapeTrack Media Management Software.
-  * [[sync:download|Downloading and Installing the software]]
-  * [[sync:prerequisites|Synchronization prerequisites]]
-  * Implement synchronization based upon the example that matches your backup solution.
-====== What is synchronization? ======
+For those who have their own TapeTrack Framework Server, these instructions relate to connecting to your own system, while, for those who use TapeTrack via a relationship with their data protection provider, these instructions relate to connecting into your vendor's system.
-TapeTrack's Synchronization Suite is a powerful toolkit that allows you to [[cli:sync_fields|set fields]] within TapeTrack based upon the values of fields within your backup or tape management software.
-====== How does synchronization work? ======
-The logic flow of synchronization is as follows:
-  * Load the definition file to instruct the program on where to get the data and how to interpret the data.
-  * Logon to the TapeTrack Framework Server
-  * Read each record from the data source, establish each of the fields to be synchronized for each record.
-  * On the first record, or on any record where the Customer and/or Media scope change, download a cache of Volume information from the TapeTrack Framework Server.
-  * Where the Volume information has changed apply the update to the TapeTrack Server.
-  * On the last record from the data source print statistics about the update session.
-<note tip>To reduce the overhead of retrieving records, when the Customer and/or Media scope change all information on all Volumes within the current scope is downloaded and loaded into a cache.
+===== Quick-start =====
-Where the Customer and/or Media scope do not change this means that the synchronization program only needs to download this information once.
+The goal of this document is to be comprehensive reference. In the event that the reader is under time constraints, the following sections should be sufficient to implement synchronization:
+  * [[sync:download|Downloading and Installing the software]]
-Care should be taken not to randomize Volumes within a Customer and or Media scope as this will degrade the performance of the program.
+  * [[sync:prerequisites|Synchronization prerequisites]]
+  * Implement synchronization based upon the example that matches your backup solution.
-If Volume scope is randomized it is strongly recommended that the data source be sorted as a step prior to synchronization.</note>
+    * [[cookbook:backupexec|Backup Exec]]
+    * [[cookbook:commvault|Commvault]]
+    * [[cookbook:dataprotector|Data Protector]]
+    * [[cookbook:netbackup|NetBackup]]
+    * [[cookbook:networker|NetWorker]]
+    * [[cookbook:tsm|Tivoli Storage Manager]]
+    * [[cookbook:veeam|VEEAM]]
-[[sync:introduction|link]]
+<-  ^ sync:introduction| - ^ sync:introduction|introduction ->