Differences

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

--- sync:data_extraction [2021/06/02 03:37] – [Data Extraction From TSM] Scott Cunliffe
+++ sync:data_extraction [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 The source file information extract will vary depending on your backup software.
-==== Data Extraction From TSM ====
+==== Data Extraction From BackupExec ====
-Using the Tivoli Storage Manager administrative tool dsmadmc, the Volume data needs to be extracted from both the DRM and Volume tables and exported into csv file format.
-To get a report that is suitable for the TapeTrack Sync command, the following minimum arguments should be used:
+The CSV report in BackupExec is created by running a PowerShell script and output to CSV file.
-=== From the DRM table: ===
+Further details on the conversion process can be viewed at [[cookbook:backupexec|Backup Exec Cookbook]]
-From the DRM table, select the fields:
+==== Data Extraction From Commvault ====
-  * volume_name: Used to determine the [[object:volume|Volume-ID]] in TapeTrack.
-  * state: Used to determine the location the [[object:volume|Volume]] should be.
-  * stgpool_name: Used to set the [[object:volume|Volume]] [[object:volume|Description]].
-<sxh>
+The Storage Information Report is created via the Commvault GUI and output to CSV format, accessible from the reports tab.
-dsmadmc -dataonly=yes -id=userid -pa=password -tcpserveraddress=tsm01.gazillabyte.local \
-        -displaymode=table -outfile=TSM-DRM.csv -commadelimited "select volume_name,state,stgpool_name from drmedia"
-</sxh>
-=== From the Volume table: ===
+Further details on the conversion process can be viewed at [[cookbook:commvault|Commvault cookbook]]
-From the [[object:volume|Volume]] table, select the fields:
+==== Data Extraction From Data Protector ====
-  * volume_name: Used to determine the [[object:volume|Volume-ID]] in TapeTrack
-  * location: Used to determine the location the [[object:volume|Volume]] is.
+The onmirpt command is available on systems with the Data Protector User Interface component installed
-  * stgpool_name: Used to set the [[object:volume|Volume]] [[object:volume|Description]].
-<sxh>
+Use the omnirpt command to extract data to a text file using:
-dsmadmc -dataonly=yes -id=userid -pa=password -tcpserveraddress=tsm01.gazillabyte.local \
-        -displaymode=table -outfile=TSM-VOL.csv -commadelimited "select volume_name,location,stgpool_name from volumes"
+Output from omnirpt, while tab delimitered, can produce offset columns depending on string lengths. To ensure the column offsets are consistent the output is passed through TMSS10CSV2Fixed producing a fixed length text file.
-</sxh>
+Further details on the conversion process can be viewed at [[cookbook:dataprotector|Data Protector Cookbook]]
+==== Data Extraction From Netbackup Vault ====
+Using the administrative tool vmquery, the Volume data can be extracted into a text file.
+The text file is then converted to a CSV file to properly format the data, along with the dates, to allow correct loading into the Sync, using the command line program TMSS10SingleSpace.
+Full definition and implementation example for extraction of data and synchronization with Netbackup is at [[cookbook:netbackup|NetBackup Sync Cookbook]]
+==== Data Extraction From Networker ====
+Using the administrative tool mminfo, the Volume data needs to be extracted from the Networker save sets and exported into CSV file format.
+Full definition and implementation example for extraction of data and synchronization with Networker is at [[cookbook:networker|NetWorker Sync Cookbook]]
+==== Data Extraction From TSM ====
+Using the Tivoli Storage Manager administrative tool dsmadmc, the Volume data needs to be extracted from both the DRM and Volume tables and exported into csv file format.
+Full definition and implementation example for extraction of data and synchronization with TSM is at [[cookbook:tsm|Tivoli Storage Manager Sync Cookbook]].
 ==== Data Extraction For VEEAM ====
@@ Line 40: / Line 52: @@
 VEEAM differs from other backup software in that a direct ODBC connection is made using the definition file rather than extracting the data to file and then using a definition file to read it.
-Sample code placed at the beginning of the definition to connect to sample database veeam2.
+Full definition and implementation example for extraction of data and synchronization with VEEAM is at [[cookbook:veeam|VEEAM Sync Cookbook]].
-<sxh>
-# Connect to Veeam database
-SetODBC("DSN=veeam2");
-# Extract data
-SetSQL("SELECT [barcode],[media_pool_id],[last_write_time] FROM [VeeamBackup].[dbo].[Tape.tape_mediums]");
-</sxh>
-<- sync:fields| Sync Fields ^ sync:introduction|introduction ^  ->
+<- sync:sources|Sync Sources ^ sync:introduction|introduction ^ sync:fields| Sync Fields ->