Difference between revisions of "DP/DataProtector Recovery"
| Line 17: | Line 17: | ||
|- | |- | ||
| style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type <span style="font-size:21px">↓</span> | | style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type <span style="font-size:21px">↓</span> | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | |- | ||
| + | | Filesystem(Win/*nix) | ||
| | | | ||
| | | | ||
Revision as of 15:05, 6 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.
Below DataProtector specific Recovery table shows different backup types and their supported recovery methods.
| Recovery Type → | Recovery As Files | Migrate to NBU (File Restore) | Migrate to NBU (Native Restore) |
| Backup Type ↓ | |||
| Filesystem(Win/*nix) |
Steps to Recover Data Protector Backups as Files
Steps to Recover Data Protector Backups as NBU Restored Files
 |
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. |