Difference between revisions of "DP/DataProtector Recovery"
From Tranzman Documentation
| Line 21: | Line 21: | ||
|- | |- | ||
| Filesystem ( Windowd /*nix ) | | Filesystem ( Windowd /*nix ) | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ RecoverWinFS/*nxFS | <span style="font-size:21px">✔</span> ]] | | [[ RecoverWinFS/*nxFS | <span style="font-size:21px">✔</span> ]] | ||
| | | | ||
| Line 31: | Line 31: | ||
|- | |- | ||
| MS-SQL | | MS-SQL | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ RecoverMSSQL |<span style="font-size:21px">✔</span> ]] | | [[ RecoverMSSQL |<span style="font-size:21px">✔</span> ]] | ||
| | | | ||
| Line 41: | Line 41: | ||
|- | |- | ||
| Sybase | | Sybase | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ RecoverSybase |<span style="font-size:21px">✔</span> ]] | | [[ RecoverSybase |<span style="font-size:21px">✔</span> ]] | ||
| | | | ||
|- | |- | ||
| Lotus Domino | | Lotus Domino | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ RecoverDomino |<span style="font-size:21px">✔</span> ]] | | [[ RecoverDomino |<span style="font-size:21px">✔</span> ]] | ||
| | | | ||
|- | |- | ||
| SAP R3 | | SAP R3 | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ Recover SAP/R3 |<span style="font-size:21px">✔</span> ]] | | [[ Recover SAP/R3 |<span style="font-size:21px">✔</span> ]] | ||
| | | | ||
|- | |- | ||
| SAP HANA | | SAP HANA | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ Recover HANA |<span style="font-size:21px">✔</span>]] | | [[ Recover HANA |<span style="font-size:21px">✔</span>]] | ||
| | | | ||
|- | |- | ||
| SAP MaxDB | | SAP MaxDB | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ Recover SAPMaxDB |<span style="font-size:21px">✔</span>]] | | [[ Recover SAPMaxDB |<span style="font-size:21px">✔</span>]] | ||
| | | | ||
|- | |- | ||
| MS-SharePoint | | MS-SharePoint | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ Recover SharePoint |<span style="font-size:21px">✔</span>]] | | [[ Recover SharePoint |<span style="font-size:21px">✔</span>]] | ||
| | | | ||
|- | |- | ||
| VMWare | | VMWare | ||
| − | | <span style="font-size:21px">✔</span> | + | | [[ Recovery as Normal Files | <span style="font-size:21px">✔</span> ]] |
| [[ Recover VMWare |<span style="font-size:21px">✔</span>]] | | [[ Recover VMWare |<span style="font-size:21px">✔</span>]] | ||
| | | | ||
Revision as of 12:56, 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 | ✔ | ✔ |
 |
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. |