sync
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sync [2021/06/01 22:41] – [Quick-start] Scott Cunliffe | sync [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Sync Introduction | + | ====== |
| + | TapeTrack' | ||
| - | This guide has been written to assist those responsible for tape management with the process of integrating their backup software | + | It provides |
| + | * 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 | + | ===== Supported Platforms ===== |
| + | * Windows. | ||
| + | * Linux Intel, Arm, Z. | ||
| + | * AIX. | ||
| + | * HPUX. | ||
| + | * Solaris (SPARC and Intel). | ||
| + | * iOS (via PASE). | ||
| + | * zOS (via USS). | ||
| + | |||
| + | ===== Technical Support ===== | ||
| + | |||
| + | TapeTrack | ||
| + | |||
| + | If you are experiencing problems or want some advice on how to configure or use the product, please see the [[common: | ||
| ===== Prerequisite knowledge ===== | ===== Prerequisite knowledge ===== | ||
| Line 13: | Line 38: | ||
| * Experience with the backup software you are synchronizing. | * Experience with the backup software you are synchronizing. | ||
| * Experience with Windows DOS batch scripting, or UNIX shell scripting. | * 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 | + | This guide has been written to assist those responsible for tape management with the process |
| - | * Outline | + | |
| - | * Provide a reference for the synchronization definition language, and, | + | 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 |
| - | * Provide examples of integration | + | |
| + | |||
| + | |||
| ===== Quick-start ===== | ===== Quick-start ===== | ||
| Line 31: | Line 58: | ||
| * [[cookbook: | * [[cookbook: | ||
| * [[cookbook: | * [[cookbook: | ||
| + | * [[cookbook: | ||
| + | * [[cookbook: | ||
| + | * [[cookbook: | ||
| - | ====== What is synchronization? | + | <- ^ sync:introduction| - ^ sync: |
| - | + | ||
| - | TapeTrack' | + | |
| - | + | ||
| - | ====== 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.</ | + | |
| - | + | ||
| - | [[sync: | + | |
sync.1622587306.txt.gz · Last modified: 2025/01/21 22:07 (external edit)
