Differences

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

--- sync [2021/06/02 00:35] – [What's in this document] Scott Cunliffe
+++ sync [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 13: / Line 13: @@
   * 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.
 ===== Supported Platforms =====
-  * Windows 7 and above.
+  * Windows.
-  * Linux Intel (32-Bit).
+  * Linux Intel, Arm, Z.
-  * Linux Arm.
+  * AIX.
+  * HPUX.
+  * Solaris (SPARC and Intel).
+  * iOS (via PASE).
+  * zOS (via USS).
 ===== Technical Support =====
@@ Line 24: / Line 30: @@
 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.
-===== Sync Guide =====
-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.
-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.
 ===== Prerequisite knowledge =====
@@ Line 39: / Line 39: @@
   * Experience with Windows DOS batch scripting, or UNIX shell scripting.
-===== Installation =====
+===== Sync Guide =====
+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.
+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.
-===== What's in this document =====
-This document will:
-  * 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.
-===== Installation =====
-  * [[sync:download|Downloading and Installing the software]]
-  * [[sync:prerequisites|Synchronization prerequisites]]
 ===== Quick-start =====
@@ Line 68: / Line 62: @@
     * [[cookbook:veeam|VEEAM]]
-====== What is synchronization? ======
+<-  ^ sync:introduction| - ^ sync:introduction|introduction ->
-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.
-Where the Customer and/or Media scope do not change this means that the synchronization program only needs to download this information once.
-Care should be taken not to randomize Volumes within a Customer and or Media scope as this will degrade the performance of the program.
-If Volume scope is randomized it is strongly recommended that the data source be sorted as a step prior to synchronization.</note>