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 05:09] – 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 BackupExec | + | ==== Data Extraction From BackupExec ==== |
| - | The CSV report in BackupExec | ||
| - | ===== Data Extraction From Commvault | + | The CSV report in BackupExec is created by running a PowerShell script and output to CSV file. |
| + | |||
| + | Further details on the conversion process can be viewed at [[cookbook: | ||
| + | |||
| + | ==== Data Extraction From Commvault ==== | ||
| The Storage Information Report is created via the Commvault GUI and output to CSV format, accessible from the reports tab. | The Storage Information Report is created via the Commvault GUI and output to CSV format, accessible from the reports tab. | ||
| Line 17: | Line 20: | ||
| Further details on the conversion process can be viewed at [[cookbook: | Further details on the conversion process can be viewed at [[cookbook: | ||
| - | ===== Data Extraction From Data Protector | + | ==== Data Extraction From Data Protector ==== |
| The onmirpt command is available on systems with the Data Protector User Interface component installed | The onmirpt command is available on systems with the Data Protector User Interface component installed | ||
| Line 27: | Line 30: | ||
| Further details on the conversion process can be viewed at [[cookbook: | Further details on the conversion process can be viewed at [[cookbook: | ||
| - | ===== Data Extraction From Netbackup Vault ===== | + | ==== Data Extraction From Netbackup Vault ==== |
| Using the administrative tool vmquery, the Volume data can be extracted into a text file. | Using the administrative tool vmquery, the Volume data can be extracted into a text file. | ||
| Line 34: | Line 37: | ||
| Full definition and implementation example for extraction of data and synchronization with Netbackup is at [[cookbook: | Full definition and implementation example for extraction of data and synchronization with Netbackup is at [[cookbook: | ||
| - | ===== Data Extraction From Networker | + | ==== 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. | 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: | Full definition and implementation example for extraction of data and synchronization with Networker is at [[cookbook: | ||
| - | ===== Data Extraction From TSM ===== | + | ==== 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. | 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. | ||
| Line 45: | Line 48: | ||
| Full definition and implementation example for extraction of data and synchronization with TSM is at [[cookbook: | Full definition and implementation example for extraction of data and synchronization with TSM is at [[cookbook: | ||
| - | ===== Data Extraction For VEEAM ===== | + | ==== 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. | 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. | ||
| Line 51: | Line 54: | ||
| Full definition and implementation example for extraction of data and synchronization with VEEAM is at [[cookbook: | Full definition and implementation example for extraction of data and synchronization with VEEAM is at [[cookbook: | ||
| - | <- sync:fields| Sync Fields | + | <- sync:sources|Sync Sources |
sync/data_extraction.1622610595.txt.gz · Last modified: 2025/01/21 22:07 (external edit)