Difference between revisions of "DP/DataProtector Recovery"
From Tranzman Documentation
Line 26: | Line 26: | ||
|- | |- | ||
| DB2 | | DB2 | ||
− | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ RecoverDB2 |<span style="font-size:21px">✔</span> ]] | | [[ RecoverDB2 |<span style="font-size:21px">✔</span> ]] | ||
| | | | ||
Line 36: | Line 36: | ||
|- | |- | ||
| Oracle | | Oracle | ||
− | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ RecoverOracle |<span style="font-size:21px">✔</span> ]] | | [[ RecoverOracle |<span style="font-size:21px">✔</span> ]] | ||
| | | |
Revision as of 12:57, 7 August 2020
Tranzman is capable of migrating Data Protector to NBU and also to recover Data Protector written data as files.Now within migrating data to NBU there are further two more classifications :- 1.Tranzman converts the data to NBU format but everything gets converted to files and then traditional DB/Application restore methods are followed. 2.Tranzman converts the data to NBU format and also to the specific policy types i.e. End user will just follow the NBU restore methods to restore different types of data.
So as described in the Overview section overall we have basically three ways of recovering/migrating data.
Recovery Type → | Recovery As Files | Migrate to NBU (File Restore) | Migrate to NBU (Native Restore) |
Backup Type ↓ | |||
Filesystem ( Windowd /*nix ) | ✔ | ✔ | |
DB2 | ✔ | ✔ | |
MS-SQL | ✔ | ✔ | |
Oracle | ✔ | ✔ | |
Sybase | ✔ | ✔ | |
Lotus Domino | ✔ | ✔ | |
SAP R3 | ✔ | ✔ | |
SAP HANA | ✔ | ✔ | |
SAP MaxDB | ✔ | ✔ | |
MS-SharePoint | ✔ | ✔ | |
VMWare | ✔ | ✔ |