Differences

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

--- cookbook:netbackup [2018/04/19 23:10] – Scott Cunliffe
+++ cookbook:netbackup [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 NetBackup Vault is a component of NetBackup that is used to set the Vault Location field in NetBackup. It may or may not be deployed.
-In the event that it is deployed TapeTrack Sync can use the Vault Location field set in NetBackup to determine the expected location of each tape volume. If Vault is not deployed, TapeTrack can determine the expected location based upon other fields such as the tape expiration date.
+In the event that it is deployed TapeTrack Sync can use the Vault Location field set in NetBackup to determine the expected location of each [[object:volume|Volume]]. If Vault is not deployed, TapeTrack can determine the expected location based upon other fields such as the [[object:volume|Volume]] expiration date.
 <note tip>
-The expiration date value in NetBackup appears to be dynamically generated when reports are run based upon the dates of each image stored on a tape volume. For this reason, reports such as vmquery do not accurately return a valid expiry date value.
+The expiration date value in NetBackup appears to be dynamically generated when reports are run based upon the dates of each image stored on a [[object:volume|Volume]]. For this reason, reports such as vmquery do not accurately return a valid expiry date value.
 </note>
+===== Data Extraction From Netbackup Vault =====
+The first step in Synchronizing your Netbackup Vault Library with TapeTrack is to extract the Volume data from your Netbackup Vault instance.
+Using the administrative tool vmquery, the Volume data can be extracted into a text file.
+{{vmquery_extract.png}}
 ===== The vmquery command =====
+<note important>NetBackup's vmquery must be installed and in current path to access the Volume information.\\
+\\
+If vmquery is not installed please refer to your NetBackup administrator.</note>
 The vmquery main page describes the command as:
-> Query the Enterprise Media Manager database, or assign and unassign volumes
+> Query the Enterprise Media Manager database, or assign and un-assign volumes
 To get a report that is suitable for the TapeTrack Sync command, the following minimum arguments should be used:
-<sxh plain;>
+<code plain;>
-vmquery -W -a > Inventory.txt
+vmquery -W -a > Report.txt
-</sxh>
+</code>
 Where:
   * ''-W'' sets the report to wide format with space delimiters.
@@ Line 34: / Line 45: @@
 ==== Example vmquery output ====
-<sxh plain;>
+<code plain;>
 MediaID OpticalPartner MediaType Barcode BarcodePartner RobotHost RobotType RobotNum RobotSlot Side/Face VolumeGroup Pool PoolNum PrevPool NumOfMounts MaxMounts NumOfCleanings CreateDatetime AssignedDatetime FirstMountDatetime LastMountDatetime ExpirationDatetime Status OffsiteLocation OffsiteSentDatetime OffsiteReturnDatetime OffsiteSlotID OffsiteSessionID Version DescriptionLength Description ContainerID
 -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ Line 47: / Line 58: @@
 E00008 - HCART    E00008 - bak901.corp.store.net TLD 1 8 - 000_00001_TLD NDMP_Incremental 9 - 6 0 - 11/02/2012 19:03 01/04/2013 05:00 12/10/2012 08:16 01/07/2013 05:01 00/00/0000 00:00 0 - 00/00/0000 00:00 00/00/0000 00:00 - - 50 22 Added by Media Manager -
 E00009 - HCART    E00009 - bak901.corp.store.net TLD 1 16 - 000_00001_TLD NDMP_Incremental 9 - 6 0 - 11/02/2012 19:03 01/07/2013 05:00 12/10/2012 08:24 01/08/2013 05:02 00/00/0000 00:00 0 - 00/00/0000 00:00 00/00/0000 00:00 - - 50 22 Added by Media Manager -
-</sxh>
+</code>
 ==== Post-processing ====
@@ Line 58: / Line 69: @@
-<sxh plain;>
+<code plain;>
-vmquery -W -a > Inventory.txt
+vmquery -W -a > Report.txt
-TMSS10SingleSpace -d "," -g "??/??/???? ??:??" < Inventory.txt > Inventory.csv
+TMSS10SingleSpace -d "," -g "??/??/???? ??:??" < Report.txt > Report.csv
-</sxh>
+</code>
+{{vmquery_extract_csv.png}}
 === Example TMSS10SingleSpace output===
-<sxh plain;>
+<code plain;>
 MediaID,OpticalPartner,MediaType,Barcode,BarcodePartner,RobotHost,RobotType,RobotNum,RobotSlot,Side/Face,VolumeGroup,Pool,PoolNum,PrevPool,NumOfMounts,MaxMounts,NumOfCleanings,CreateDatetime,AssignedDatetime,FirstMountDatetime,LastMountDatetime,ExpirationDatetime,Status,OffsiteLocation,OffsiteSentDatetime,OffsiteReturnDatetime,OffsiteSlotID,OffsiteSessionID,Version,DescriptionLength,Description,ContainerID
 -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
@@ Line 78: / Line 91: @@
 E00008,-,HCART,E00008,-,bak901.corp.store.net,TLD,1,8,-,000_00001_TLD,NDMP_Incremental,9,-,6,0,-,11/02/2012 19:03,01/04/2013 05:00,12/10/2012 08:16,01/07/2013 05:01,00/00/0000 00:00,0,-,00/00/0000 00:00,00/00/0000 00:00,-,-,50,22,Added,by,Media,Manager,-
 E00009,-,HCART,E00009,-,bak901.corp.store.net,TLD,1,16,-,000_00001_TLD,NDMP_Incremental,9,-,6,0,-,11/02/2012 19:03,01/07/2013 05:00,12/10/2012 08:24,01/08/2013 05:02,00/00/0000 00:00,0,-,00/00/0000 00:00,00/00/0000 00:00,-,-,50,22,Added,by,Media,Manager,-
-</sxh>
+</code>
 ==== Barcodes ====
-It is common for NetBackup barcodes to be missing the LTO L-Suffix, and also common for the Media Type field to have a HCART value that does not truly reflect the correct LTO generation.
+It is common for NetBackup Barcodes to be missing the LTO L-Suffix, and also common for the Media Type field to have a HCART value that does not truly reflect the correct LTO generation.
 If is always recommended that where possible volumes be 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.
-  - Adding an appropriate suffix based upon the range of the Media ID.
+  - Adding an appropriate suffix based upon the range of the Media-ID.
   - Using TapeTrack's Constructive Barcode feature.
@@ Line 96: / Line 109: @@
   - Command line arguments that instruct the program how to process volumes.
   - A synchronization definition file that instructs the program how to interpret the vmquery output.
+{{networker_sync.png}}
 ==== Example Command Line Arguments ====
-<sxh plain;>
+<code plain;>
-TMSS10Sync -d NBU.ttidef -a -S batch:-password@server < Inventory.csv
+TMSS10Sync -d Volume.ttidef -a -S batch:-password@server < Inventory.csv
-</sxh>
+</code>
 Where:
   * ''-d'' is the path to the Synchronization Definition File.
   * ''-a'' tells the program to add new tape volumes if they are encountered.
-  * ''-S'' tells the program what server to connect to.
+  * ''-S'' tells the program what [[cli:server_argument|Server]] to connect to.
   * ''Inventory.csv'' is the ''vmquery'' output that has been pre-processed through the [[cli:tmss10singlespace|TMSS10SingleSpace]] program
 ==== Example Synchronization Definition ====
-<sxh plain;>
+<code plain;>
 #
 # Set the Customer and Media as literal values as they never change
@@ Line 154: / Line 169: @@
 #
 AddTranslation(REPOSITORY, "*", "LIBR");
-</sxh>
+</code>
+<- :cookbook:dataprotector|Data Protector Sync Cookbook ^ :cookbook:introduction|Cookbook ^ :cookbook:networker|NetWorker Sync Cookbook->
+{{tag> cookbook}}