Difference between revisions of "TSM/Tivoli Storage Manager or IBM Spectrum Protect Recovery"

From Tranzman Documentation
Jump to: navigation, search
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
Tranzman is capable of migrating TSM to NBU and also to recover TSM written data as files.And with 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.
  
  
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 :-
+
So we have basically three ways of recovering/migrating data from TSM.
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.You can 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.
 
 
{| class="wikitable" style="border:5px double maroon" font-family:Arial, Helvetica, sans-serif !important align=center cellpadding=40px width=100%;;"   
 
{| class="wikitable" style="border:5px double maroon" font-family:Arial, Helvetica, sans-serif !important align=center cellpadding=40px width=100%;;"   
 +
|+Below DataProtector specific Recovery table shows different backup types and their supported recovery methods.Click on <span style="font-size:21px;color:DarkRed">✔</span> to jump straight to the restore steps.
 
|-
 
|-
| style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Recovery Type <span style="font-size:21px">→</span>
+
| style="font-weight:bold; text-align: center; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type / Recovery Type  
| Recovery As Files
+
|style="text-align: center;| Recovery As Files
| Migrate to NBU (File  Restore)
+
|style="text-align: center;| Migrate to NBU (File  Restore)
| Migrate to NBU (Native Restore)
+
|style="text-align: center;| Migrate to NBU (Native Restore)
 
|-
 
|-
| style="font-weight:bold; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type <span style="font-size:21px"></span>
+
| style="text-align: center;|Filesystem ( Windowd /*nix )
 +
| style="text-align: center;|[[ Recovery as Normal Files(FileSystem) | <span style="font-size:21px">✔</span> ]]
 +
| style="text-align: center;|[[ RecoverWinFS/*nxFS | <span style="font-size:21px"></span> ]]
 
|  
 
|  
 +
|-
 +
| style="text-align: center;|DB2
 +
| style="text-align: center;| [[ Recovery as Normal Files(DB2) | <span style="font-size:21px">✔</span> ]]
 +
| style="text-align: center;|[[ RecoverDB2        |<span style="font-size:21px">✔</span> ]]
 
|  
 
|  
 +
|-
 +
| style="text-align: center;| MS-SQL
 +
| style="text-align: center;|[[ Recovery as Normal Files(MSSQL) | <span style="font-size:21px">✔</span> ]]
 +
| style="text-align: center;|[[ RecoverMSSQL    |<span style="font-size:21px">✔</span>    ]]
 
|  
 
|  
 
|-
 
|-
| Filesystem ( Windowd /*nix )
+
| style="text-align: center;|Oracle
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(Oracle) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;|[[ RecoverOracle      |<span style="font-size:21px">✔</span> ]]
| [[ RecoverWinFS/*nxFS | <span style="font-size:21px">✔</span> ]]  
 
|-
 
| DB2
 
| <span style="font-size:21px">✔</span>
 
|
 
| [[ RecoverDB2        |<span style="font-size:21px">✔</span> ]]  
 
|-
 
| MS-SQL
 
| <span style="font-size:21px">✔</span>
 
 
|
 
|
| [[ RecoverMSSQL    |<span style="font-size:21px">✔</span>    ]]
 
|-
 
| Oracle
 
| <span style="font-size:21px">✔</span>
 
|
 
| [[ RecoverOracle      |<span style="font-size:21px">✔</span> ]]
 
 
|-  
 
|-  
| Sybase
+
| style="text-align: center;|Sybase
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(Sybase) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;|[[ RecoverSybase      |<span style="font-size:21px">✔</span> ]]
| [[ RecoverSybase      |<span style="font-size:21px">✔</span> ]]  
+
|
 
|-
 
|-
| Lotus Domino
+
| style="text-align: center;|Lotus Domino
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(Lotus Domino) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;|[[ RecoverDomino      |<span style="font-size:21px">✔</span> ]]
| [[ RecoverDomino      |<span style="font-size:21px">✔</span> ]]  
+
|
 
|-
 
|-
| SAP R3
+
| style="text-align: center;|SAP R3
| <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> ]]
| [[ Recover SAP/R3      |<span style="font-size:21px">✔</span> ]]  
+
|
 
|-
 
|-
| SAP HANA
+
| style="text-align: center;|SAP HANA
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(SAP HANA) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;|[[ Recover HANA        |<span style="font-size:21px">✔</span>]]
| [[ Recover HANA        |<span style="font-size:21px">✔</span>]]  
+
|
 
|-
 
|-
| SAP MaxDB
+
| style="text-align: center;|SAP MaxDB
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(SAP MaxDB) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;| [[ Recover SAPMaxDB    |<span style="font-size:21px">✔</span>]]
| [[ Recover SAPMaxDB    |<span style="font-size:21px">✔</span>]]  
+
|
 
|-
 
|-
| MS-SharePoint
+
| style="text-align: center;|MS-SharePoint
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(MS-SharePoint) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;|[[ Recover SharePoint  |<span style="font-size:21px">✔</span>]]
| [[ Recover SharePoint  |<span style="font-size:21px">✔</span>]]  
+
|
 
|-
 
|-
| VMWare
+
| style="text-align: center;|VMWare
| <span style="font-size:21px">✔</span>
+
| style="text-align: center;|[[ Recovery as Normal Files(VMware) | <span style="font-size:21px">✔</span> ]]
|
+
| style="text-align: center;|[[ Recover VMWare      |<span style="font-size:21px">✔</span>]]
| [[ Recover VMWare      |<span style="font-size:21px">✔</span>]]  
+
|
 
|-
 
|-
 
|}
 
|}
 
  
  

Latest revision as of 15:05, 16 December 2020

Tranzman is capable of migrating TSM to NBU and also to recover TSM written data as files.And with 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 we have basically three ways of recovering/migrating data from TSM.


Below DataProtector specific Recovery table shows different backup types and their supported recovery methods.Click on to jump straight to the restore steps.
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.png 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.