Difference between revisions of "DP/DataProtector Recovery"
From Tranzman Documentation
| Line 48: | Line 48: | ||
|- | |- | ||
| style="text-align: center;|SAP R3 | | style="text-align: center;|SAP R3 | ||
| − | | style="text-align: center;|[[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] | + | | style="text-align: center;|[[ Recovery as Normal Files(SAP R3) | <span style="font-size:21px">✔</span> ]] |
| style="text-align: center;|[[ Recover SAP/R3 |<span style="font-size:21px">✔</span> ]] | | style="text-align: center;|[[ Recover SAP/R3 |<span style="font-size:21px">✔</span> ]] | ||
| | | | ||
Revision as of 14:34, 30 October 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.
| Backup Type / Recovery Type | Recovery As Files | Migrate to NBU (File Restore) | Migrate to NBU (Native Restore) |
| Filesystem ( Windowd /*nix ) | ✔ | ✔ | |
| DB2 | ✔ | ✔ | |
| MS-SQL | ✔ | ✔ | |
| Oracle | ✔ | ✔ | |
| Sybase | ✔ | ✔ | |
| Lotus Domino | ✔ | ✔ | |
| SAP R3 | ✔ | ✔ | |
| SAP HANA | ✔ | ✔ | |
| SAP MaxDB | ✔ | ✔ | |
| MS-SharePoint | ✔ | ✔ | |
| VMWare | ✔ | ✔ |
 |
Note: It is very important that whenever any of the recovery steps are initiated, for the Tranzman Appliance and all relevant servers be synchronised to the correct time, data and timezone. Failure to do this will potentially result in data not being found by the appliance during the restore process. |