TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • windowspdf • upgrade_utilities
cookbook:networker

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:networker [2020/02/19 01:30] – [Example Command Line Arguments] Scott Cunliffecookbook:networker [2025/01/23 03:50] (current) – [Example Synchronization Definition] Gerard Nicol
Line 5: Line 5:
 ===== Data Extraction From Networker ===== ===== Data Extraction From Networker =====
  
-The first step in Syncronizing your Networker Library with TapeTrack is to extract the Volume data from your Networker instance.+The first step in Synchronizing your Networker Library with TapeTrack is to extract the Volume data from your Networker instance.
  
 Using the administrative tool mminfo, the Volume data needs to be extracted from the Networker save sets and exported into CSV file format. Using the administrative tool mminfo, the Volume data needs to be extracted from the Networker save sets and exported into CSV file format.
Line 16: Line 16:
 To get a report that is suitable for the TapeTrack Sync command, the following minimum arguments should be used: To get a report that is suitable for the TapeTrack Sync command, the following minimum arguments should be used:
  
-<sxh plain;>+<code plain;>
 mminfo -xc, -a -r "volume,barcode,family,type,location,pool" > report.csv mminfo -xc, -a -r "volume,barcode,family,type,location,pool" > report.csv
-</sxh>+</code>
  
 ==== Example mminfo output ==== ==== Example mminfo output ====
  
-<sxh plain;>+=== Output With Suffix === 
 + 
 +<code plain;>
 volume,barcode,family,type,location,pool volume,barcode,family,type,location,pool
 000000L6,000000L6,tape,LTO,Offsite,weekly_full 000000L6,000000L6,tape,LTO,Offsite,weekly_full
Line 32: Line 34:
 000006L6,000006L6,tape,LTO,Offsite,weekly_full 000006L6,000006L6,tape,LTO,Offsite,weekly_full
 000007L6,000007L6,tape,LTO,Offsite,weekly_full 000007L6,000007L6,tape,LTO,Offsite,weekly_full
-</sxh>+</code>
  
 +=== Output Without Suffix ===
 +
 +<code plain;>
 +volume,barcode,family,type,location,pool
 +000000,000000,tape,LTO,Offsite,weekly_full
 +000001,000001,tape,LTO,Offsite,weekly_full
 +000002,000002,tape,LTO,Offsite,weekly_full
 +000003,000003,tape,LTO,Offsite,weekly_full
 +000004,000004,tape,LTO,Offsite,weekly_full
 +000005,000005,tape,LTO,Offsite,weekly_full
 +000006,000006,tape,LTO,Offsite,weekly_full
 +000007,000007,tape,LTO,Offsite,weekly_full
 +</code>
 ==== Post-processing ==== ==== Post-processing ====
  
Line 41: Line 56:
 It possible for NetWorker barcodes to be missing the LTO L-Suffix. It possible for NetWorker barcodes to be missing the LTO L-Suffix.
  
-It is always recommended that where possible volumes be loaded into TapeTrack with their L-Suffix, and this suffix can be established by:+It is always recommended that where possible volumes are loaded into TapeTrack with their L-Suffix, and this suffix can be established by:
   - The Media-ID value if it includes the suffix.   - The Media-ID value if it includes the suffix.
   - Adding an appropriate suffix to the Media-ID based upon the value of the Media Type field.   - Adding an appropriate suffix to the Media-ID based upon the value of the Media Type field.
Line 49: Line 64:
 ===== Synchronization ===== ===== Synchronization =====
  
-Synchronization with TapeTrack is performed by calling the [[cli:TMSS10Sync|TMSS10Sync]] command line program, along with:+Synchronization with TapeTrack is performed by calling the [[cli:TMSS10Sync|TMSS10Sync]] command-line program, along with:
  
   - The CSV file produced by pre-processing the mminfo output.   - The CSV file produced by pre-processing the mminfo output.
-  - Command line arguments that instruct the program how to process volumes. +  - Command-line arguments that instruct the program how to process volumes. 
   - A synchronization definition file that instructs the program how to interpret the mminfo output.   - A synchronization definition file that instructs the program how to interpret the mminfo output.
 +
 +{{networker_sync.png}}
  
 ==== Example Command Line Arguments ==== ==== Example Command Line Arguments ====
  
-<sxh>+<code>
 TMSS10Sync -d Volume.ttidef -a -S user:-password@server < report.csv  TMSS10Sync -d Volume.ttidef -a -S user:-password@server < report.csv 
-</sxh>+</code>
  
 Where: Where:
Line 70: Line 87:
 ==== Example Synchronization Definition ==== ==== Example Synchronization Definition ====
  
-<sxh plain;>+<code plain;>
 # #
 # Set the Customer and Media as literal values as they never change # Set the Customer and Media as literal values as they never change
Line 79: Line 96:
 # Set the delimiter to a CSV # Set the delimiter to a CSV
 # #
-SetCSVDelimiter(",")+SetCSVDelimiter(",");
 # #
 # Skip any line that begins with string volume (header) # Skip any line that begins with string volume (header)
Line 100: Line 117:
 AddTranslation(REPOSITORY, *, "LIBR"); AddTranslation(REPOSITORY, *, "LIBR");
  
-</sxh>+</code>
  
  
cookbook/networker.1582075802.txt.gz · Last modified: 2025/01/21 22:07 (external edit)