sync:data_extraction
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sync:data_extraction [2021/06/02 03:43] – [Data Extraction For VEEAM] 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. | The source file information extract will vary depending on your backup software. | ||
| - | ===== Data Extraction From Networker ===== | + | ==== Data Extraction From BackupExec |
| - | Using the administrative tool mminfo, the Volume data needs to be extracted from the Networker save sets and exported into CSV file format. | ||
| - | To get a report | + | The CSV report |
| - | < | + | |
| - | mminfo -xc, -a -r " | + | |
| - | </ | + | |
| - | ===== 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. | + | Further details on the conversion process can be viewed at [[cookbook: |
| - | To get a report that is suitable for the TapeTrack Sync command, the following minimum arguments should be used: | + | ==== Data Extraction From Commvault ==== |
| - | === From the DRM table: === | + | The Storage Information Report is created via the Commvault GUI and output to CSV format, accessible from the reports tab. |
| - | From the DRM table, select the fields: | + | Further details on the conversion process can be viewed at [[cookbook:commvault|Commvault cookbook]] |
| - | * volume_name: | + | |
| - | * state: Used to determine the location the [[object: | + | |
| - | * stgpool_name: | + | |
| - | < | + | ==== Data Extraction From Data Protector ==== |
| - | dsmadmc -dataonly=yes -id=userid -pa=password -tcpserveraddress=tsm01.gazillabyte.local \ | + | |
| - | -displaymode=table -outfile=TSM-DRM.csv -commadelimited " | + | |
| - | </ | + | |
| - | === From the Volume table: === | + | The onmirpt command is available on systems with the Data Protector User Interface component installed |
| - | From the [[object: | + | Use the omnirpt command |
| - | * volume_name: | + | |
| - | * location: Used to determine the location the [[object: | + | |
| - | * stgpool_name: | + | |
| - | < | + | |
| - | dsmadmc -dataonly=yes -id=userid -pa=password -tcpserveraddress=tsm01.gazillabyte.local \ | + | |
| - | -displaymode=table -outfile=TSM-VOL.csv -commadelimited " | + | |
| - | </ | + | |
| - | ===== Data Extraction For VEEAM ===== | + | Output from omnirpt, while tab delimitered, |
| - | 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. | + | Further details on the conversion process can be viewed at [[cookbook: |
| - | Sample code placed | + | ==== 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: | ||
| + | ==== 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 | ||
| + | ==== 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 | ||
| + | |||
| + | ==== Data Extraction For VEEAM ==== | ||
| + | |||
| + | 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. | ||
| - | < | + | Full definition and implementation example for extraction of data and synchronization with VEEAM is at [[cookbook: |
| - | # Connect to Veeam database | + | |
| - | SetODBC(" | + | |
| - | # Extract | + | |
| - | SetSQL(" | + | |
| - | </ | + | |
| - | <- sync:fields| Sync Fields | + | <- sync:sources|Sync Sources |
sync/data_extraction.1622605415.txt.gz · Last modified: 2025/01/21 22:07 (external edit)
