Difference between revisions of "Recoverydocs"
From Tranzman Documentation
Line 10: | Line 10: | ||
|+See below table for Tranzman supportability matrix for data recovery and transition.Click on [[File:Tick.JPG | border|25x25px]] to jump straight to restore steps or by selecting specific backup product on the sidebar under Recovery Documentation. | |+See below table for Tranzman supportability matrix for data recovery and transition.Click on [[File:Tick.JPG | border|25x25px]] to jump straight to restore steps or by selecting specific backup product on the sidebar under Recovery Documentation. | ||
|- | |- | ||
− | | style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Recovery Type <span style="font-size:21px">→</span> | + | !rowspan="2"| style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Recovery Type <span style="font-size:21px">→</span> |
| Recovery As Files | | Recovery As Files | ||
| Migrate to NBU (File Restore) | | Migrate to NBU (File Restore) |
Revision as of 13:25, 7 August 2020
<< Left to Comment -? What Tranzman can do ? >>
- Recovery As Files -> Restore everything(structured/unstructured data) to a share mounted on appliance as files and use traditional DB/Application restore methods to restore data.
- Migrate to NBU(File Restore) -> Restore everything(structured/unstructured data) to NBU as files(Standard/Windows backup type) and use traditional DB/Application restore methods to restore data.
- Migrate to NBU(Native Restore) -> Restore everything(structured/unstructured data) to NBU as repective backup types and use NBU restore methods to restore data.
style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Recovery Type → | Recovery As Files | Migrate to NBU (File Restore) | Migrate to NBU (Native Restore) | Migrate to Commvault |
---|---|---|---|---|
Data Protector | ✔ | ✔ | ✔ | × |
IBM TSM/ Spectrum Protect | ✔ | ✔ | ✔ | × |
VERITAS Backup Exec | ✔ | × | × | × |
Note: For Migrate to NBU(Native Restore) please refer to VERITAS Documentation. |