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

From Tranzman Documentation
Jump to: navigation, search
Line 1: Line 1:
 
+
Tranzman is capable of migrating TSM to NBU and also to recover TSM written data as files.Now within migrating data to NBU there are further two more classifications :-
 
 
 
 
 
 
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.
 
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.
 
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.
Line 10: Line 6:
  
  
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.
+
Below TSM 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%;;"   
 
|-
 
|-
Line 25: Line 21:
 
| Filesystem ( Windowd /*nix )
 
| Filesystem ( Windowd /*nix )
 
| <span style="font-size:21px">✔</span>
 
| <span style="font-size:21px">✔</span>
|
+
| [[ RecoverWinFS/*nxFS | <span style="font-size:21px">✔</span> ]]
| [[ RecoverWinFS/*nxFS | <span style="font-size:21px">✔</span> ]]  
+
|
 
|-
 
|-
 
| DB2
 
| DB2
 
| <span style="font-size:21px">✔</span>
 
| <span style="font-size:21px">✔</span>
|
+
| [[ RecoverDB2        |<span style="font-size:21px">✔</span> ]]
| [[ RecoverDB2        |<span style="font-size:21px">✔</span> ]]  
+
|
 
|-
 
|-
 
| MS-SQL
 
| MS-SQL
 
| <span style="font-size:21px">✔</span>
 
| <span style="font-size:21px">✔</span>
|
+
| [[ RecoverMSSQL    |<span style="font-size:21px">✔</span>    ]]
| [[ RecoverMSSQL    |<span style="font-size:21px">✔</span>    ]]  
+
|
 
|-
 
|-
 
| Oracle
 
| Oracle
 
| <span style="font-size:21px">✔</span>
 
| <span style="font-size:21px">✔</span>
 +
| [[ RecoverOracle      |<span style="font-size:21px">✔</span> ]]
 
|
 
|
| [[ RecoverOracle      |<span style="font-size:21px">✔</span> ]]
 
 
|-  
 
|-  
 
| Sybase
 
| Sybase
 
| <span style="font-size:21px">✔</span>
 
| <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>
 
| <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>
 
| <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>
 
| <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>
 
| <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>
 
| <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>
 
| <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 08:48, 7 August 2020

Tranzman is capable of migrating TSM to NBU and also to recover TSM 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 TSM specific Recovery table shows different backup types and their supported recovery methods.You can click on Tick.JPG to jump straight to restore steps or by selecting specific backup product on the sidebar under Recovery Documentation.

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.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.