TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • attribute_list_values • introduction • function_getting_help • function_help
cookbook:sync

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
cookbook:sync [2019/06/13 03:00] – Scott Cunliffecookbook:sync [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 3: Line 3:
 ===== TMSS10Sync Implementation ===== ===== TMSS10Sync Implementation =====
  
-The TapeTrack Sync uses, in its minimum format, uses an executable TMSS10Sync, an input file containing the information to syncronise and a definition file (ttidef) containg the information on how to read, or translate, the information in the input file.+The TapeTrack Sync uses, in its minimum format, uses an executable TMSS10Sync, an input file containing the information to synchronize and a definition file (ttidef) containing the information on how to read, or translate, the information in the input file.
  
 ==== TTIDEF Definition File Explained ==== ==== TTIDEF Definition File Explained ====
Line 11: Line 11:
 {{sync_no_translator.png}} {{sync_no_translator.png}}
  
-The solution to this problem is the implementation of a translator who speaks both languages.  The customer talks to the translator, who passes the information to the teller in English so the money can be paced into the correct account.+The solution to this problem is the implementation of a translator who speaks both languages.  The customer talks to the translator, who passes the information to the teller in English so the money can be placed into the correct account.
  
 {{sync_translator.png}} {{sync_translator.png}}
  
-This is similar the situation faced by TapeTrack Sync when importing information into the database. A text or CSV input file can contain Volume information in many formats so direct import is not possible in the raw format. +This is similar to the situation faced by TapeTrack Sync when importing information into the database. A text or CSV input file can contain Volume information in many formats so direct import is not possible in the raw format. 
  
 {{tmss10sync_no_translator.png}} {{tmss10sync_no_translator.png}}
Line 34: Line 34:
 === CSV Input File Format === === CSV Input File Format ===
  
-Sample CSV File - ''sample.csv''+Sample CSV File - ''sample.csv'' \\
 This file can be found in your Sync installation directory at TapeTrack\TapeTrack Sync\var\sample.csv This file can be found in your Sync installation directory at TapeTrack\TapeTrack Sync\var\sample.csv
  
-<sxh>+<code>
 GZB0001,LTO5,Full System Backup GZB0001,LTO5,Full System Backup
 GZB0002,LTO4,GL Backup GZB0002,LTO4,GL Backup
Line 48: Line 48:
 GZB0009,LTO2,Exchange Server Backup GZB0009,LTO2,Exchange Server Backup
 GZB0010,LTO5,Full System Backup GZB0010,LTO5,Full System Backup
-</sxh>+</code>
  
  
Line 56: Line 56:
   * Volume Description in column 3   * Volume Description in column 3
  
-Missing from the CSV file is the Customer-ID, which will set directly from within the definition file.+Missing from the CSV file is the Customer-IDand Media-ID, which will set directly from within the definition file.
  
-Lines in the definition file that start with # are comments for explanation and are not read by the Sync engine.+Lines in the definition file that start with #, or midline after the #, are comments for explanation and are not read by the Sync engine.
  
-Sample Definition File - default.ttidef+Sample Definition File - default.ttidef \\
 This file can be found in your Sync installation directory at TapeTrack\TapeTrack Sync\etc\sample.ttidef This file can be found in your Sync installation directory at TapeTrack\TapeTrack Sync\etc\sample.ttidef
  
-<sxh>+<code>
 # #
 # Object Type: TapeTrack Sync Definition File                                                   # Object Type: TapeTrack Sync Definition File                                                  
Line 74: Line 74:
 SetLiteral(MEDIA, "LTO");             # Set the Media-ID to a literal value of LTO SetLiteral(MEDIA, "LTO");             # Set the Media-ID to a literal value of LTO
 SetCSVDelimiter(",");                 # Instruct the parser that we have a CSV file and the file is delimited with commas SetCSVDelimiter(",");                 # Instruct the parser that we have a CSV file and the file is delimited with commas
-Extract(VOLUME, 1, 6, 0);             # Extract the Volume-ID from the 1st column of the CSV with a length of 6 bytes+Extract(VOLUME, 1, 7, 0);             # Extract the Volume-ID from the 1st column of the CSV with a length of 7 bytes
 Extract(USER1, 2, 10, 0);             # Extract a user field for translation Extract(USER1, 2, 10, 0);             # Extract a user field for translation
 Extract(DESCRIPTION, 3, 40, 0);       # Extract the Description field Extract(DESCRIPTION, 3, 40, 0);       # Extract the Description field
 RemoveSpaces(DESCRIPTION);            # Remove any white space from the LHS of the description RemoveSpaces(DESCRIPTION);            # Remove any white space from the LHS of the description
 # #
-# Add L suffixes to the Volume-ID based on Media Type and Generation+# Add L suffixes to the Volume-ID based on Media Generation
 # #
 AddTranslation2(VOLUME, USER1, "LTO1", "*L1"); AddTranslation2(VOLUME, USER1, "LTO1", "*L1");
Line 88: Line 88:
 AddTranslation2(VOLUME, USER1, "LTO6", "*L6"); AddTranslation2(VOLUME, USER1, "LTO6", "*L6");
 AddTranslation2(VOLUME, USER1, "LTO7", "*L7"); AddTranslation2(VOLUME, USER1, "LTO7", "*L7");
-</sxh> +</code>
  
 +{{tag> cookbook}}
  
cookbook/sync.1560394803.txt.gz · Last modified: 2025/01/21 22:07 (external edit)