Tranzman Documentation - User contributions [en]

Finalize

2020-10-01T09:08:28Z

Admin:

== Headline ==

Finalize in Tranzman refers to the stage where all catalog components have been migrated and the environments can be finalised i.e. During this process objects are deactivated on the origin
and activated on the destination. Objects here refer to the Media Servers, Storage Servers, Robotic Devices , Storage units , Policies and Clients.

Follow the below steps to perform Finalize.

===Step 1===
Click on Actions->Finalize and you should see two sections of Origin and Destination.
We have to finalize origin backup environment first.Basically we have to stop the functioning of the origin backup environment.
Briefly, just make sure you have the ticks in the Check column. Click on the play button

===Step 2===
So initialization is done.You can see up to CreateWorkloads all have ticks. You can still rerun them if you see a problem.Next, we need to ensure there is a tick here for Hosts Reachable.

===Step 3===

[[ Pre-Assessment| Jump to Pre-Assessment ]]

[[ Migration Components | Return to Select Migration Components ]]

TSM/Tivoli Storage Manager or IBM Spectrum Protect Recovery

2020-09-03T10:31:05Z

Admin:

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.

{| 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 ✔ to jump straight to the restore steps.
|-
| style="font-weight:bold; text-align: center; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type / Recovery Type
|style="text-align: center;| Recovery As Files
|style="text-align: center;| Migrate to NBU (File Restore)
|style="text-align: center;| Migrate to NBU (Native Restore)
|-
| style="text-align: center;|Filesystem ( Windowd /*nix )
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverWinFS/*nxFS | ✔ ]]
|
|-
| style="text-align: center;|DB2
| style="text-align: center;| [[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverDB2 |✔ ]]
|
|-
| style="text-align: center;| MS-SQL
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverMSSQL |✔ ]]
|
|-
| style="text-align: center;|Oracle
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverOracle |✔ ]]
|
|-
| style="text-align: center;|Sybase
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverSybase |✔ ]]
|
|-
| style="text-align: center;|Lotus Domino
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverDomino |✔ ]]
|
|-
| style="text-align: center;|SAP R3
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover SAP/R3 |✔ ]]
|
|-
| style="text-align: center;|SAP HANA
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover HANA |✔]]
|
|-
| style="text-align: center;|SAP MaxDB
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;| [[ Recover SAPMaxDB |✔]]
|
|-
| style="text-align: center;|MS-SharePoint
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover SharePoint |✔]]
|
|-
| style="text-align: center;|VMWare
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover VMWare |✔]]
|
|-
|}

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''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.
|
|}

DP/DataProtector Recovery

2020-09-03T09:54:24Z

Admin:

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.

{| 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 ✔ to jump straight to the restore steps.
|-
| style="font-weight:bold; text-align: center; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type / Recovery Type
|style="text-align: center;| Recovery As Files
|style="text-align: center;| Migrate to NBU (File Restore)
|style="text-align: center;| Migrate to NBU (Native Restore)
|-
| style="text-align: center;|Filesystem ( Windowd /*nix )
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverWinFS/*nxFS | ✔ ]]
|
|-
| style="text-align: center;|DB2
| style="text-align: center;| [[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverDB2 |✔ ]]
|
|-
| style="text-align: center;| MS-SQL
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverMSSQL |✔ ]]
|
|-
| style="text-align: center;|Oracle
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverOracle |✔ ]]
|
|-
| style="text-align: center;|Sybase
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverSybase |✔ ]]
|
|-
| style="text-align: center;|Lotus Domino
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverDomino |✔ ]]
|
|-
| style="text-align: center;|SAP R3
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover SAP/R3 |✔ ]]
|
|-
| style="text-align: center;|SAP HANA
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover HANA |✔]]
|
|-
| style="text-align: center;|SAP MaxDB
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;| [[ Recover SAPMaxDB |✔]]
|
|-
| style="text-align: center;|MS-SharePoint
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover SharePoint |✔]]
|
|-
| style="text-align: center;|VMWare
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover VMWare |✔]]
|
|-
|}

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''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.
|
|}

DP/DataProtector Recovery

2020-09-03T09:54:13Z

Admin:

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.

{| 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 ✔ to jump straight to the restore steps.
|-
| style="font-weight:bold; text-align: center; font-family:Arial, Helvetica, sans-serif !important;;" | Backup Type / Recovery Type
|style="text-align: center;| Recovery As Files
|style="text-align: center;| Migrate to NBU (File Restore)
|style="text-align: center;| Migrate to NBU (Native Restore)
|-
| style="text-align: center;|Filesystem ( Windowd /*nix )
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverWinFS/*nxFS | ✔ ]]
|
|-
| style="text-align: center;|DB2
| style="text-align: center;| [[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverDB2 |✔ ]]
|
|-
| style="text-align: center;| MS-SQL
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverMSSQL |✔ ]]
|
|-
| style="text-align: center;|Oracle
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverOracle |✔ ]]
|
|-
| style="text-align: center;|Sybase
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverSybase |✔ ]]
|
|-
| style="text-align: center;|Lotus Domino
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ RecoverDomino |✔ ]]
|
|-
| style="text-align: center;|SAP R3
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover SAP/R3 |✔ ]]
|
|-
| style="text-align: center;|SAP HANA
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover HANA |✔]]
|
|-
| style="text-align: center;|SAP MaxDB
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;| [[ Recover SAPMaxDB |✔]]
|
|-
| style="text-align: center;|MS-SharePoint
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover SharePoint |✔]]
|
|-
| style="text-align: center;|VMWare
| style="text-align: center;|[[ Recovery as Normal Files | ✔ ]]
| style="text-align: center;|[[ Recover VMWare |✔]]
|
|-
|}

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''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.
|
|}

Finalize

2020-09-02T13:10:06Z

Admin: Created page with " == Headline == Finalize in Tranzman refers to the stage where all catalog components have been migrated and the environments can be finalised i.e. During this process object..."

Manage Hosts

2020-09-02T12:52:21Z

Admin:

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' This section is Applicable to migrations which involves NetBackup versions 8.1 and later.
|
|}

== Headline ==

NetBackup uses security certificates to authenticate NetBackup hosts. The security certificates conform to the X.509 Public Key Infrastructure (PKI) standard. A master server acts as the Certificate Authority (CA) and issues digital certificates to hosts.
NetBackup 8.1 and later hosts can communicate with each other only in a securemode. NetBackup 8.1 hosts and later must have a Certificate Authority (CA) certificate and a host ID-based certificate for successful communication.For more details please refer to the NetBackup Security and Encryption guide.

So for catalog migrations between NetBackup 8.1 and later , CA Certificate and host ID certificates need to be deployed to all the NBU hosts from the destination master server.
Tranzman has a brilliant feature named Host Management which does these deployments.Additionaly it also helps you to check the NBU connectivity within hosts so before switching to destination master server
in production any connectivity issue could be highlighted and fixed.

You can access the Host Management from Tranzman UI under Actions->Host Management.Certificates is a vast thing in itself so to understand it better you do need to have some basic information information on how certificates actually work in NetBackup.

Follow the below steps to deploy the certificates from the destination master server to the NBU hosts :-

===Step 1===
Click on Actions->Host Management.Now as we are already in the data transfer stage all the NBU hosts should be discovered and should be displayed on the Host Management Page under Client Mangement.
e.g. Figure 1 shows all the NBU hosts including media servers.

[[File:HostManagement1.JPG | border|1100x800px]]
Figure1

===Step 2===
Select all the eligible NBU hosts then Actions -> Run origin connectivity test as shown in the below screenshot(Figure2) and hit [[File:Commit.JPG | border|100x100px]].
You would see couple of jobs being triggered named CheckConn under Views->Activity Monitor. Wait for them to complete and the respective columns on the Host Management page should get populated with
[[File:GreenTick.JPG | border|20x15px]] rather than [[File:RedTick.JPG | border|20x20px]].

[[File:HostMgmtConnectivityTest.JPG | border|1100x800px]]
Figure2

===Step 3===
A successful connectivity test from origin should move the media servers to the Media Server Management tab(as shown in Figure 3) and only backup clients should be seen under Client Management(Figure 4).
As it can be seen most of the columns are populated in Figure 4 , please refer to the below table to check what the respective column means in host management. Any unexpected [[File:RedTick.JPG | border|20x20px]] in any column should be fixed before proceeding to next steps.

{|class="wikitable" style="border:5px double maroon" font-family:Arial, Helvetica, sans-serif !important align=center cellpadding=40px width=30%;;"
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Name
| style="font-weight:normal;" | Name of the NBU host
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Actions
| style="font-weight:normal;" | Selected actions for the NBU host
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Version
| style="font-weight:normal;" | Version of NetBackup
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Active
| style="font-weight:normal;" | State of Host (Active only if backup has ran in last 7 days)
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Host props
| style="font-weight:normal;" | NBU Host properties
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Master
| style="font-weight:normal;" | Current Master Server for NBU host
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Accelerator
| style="font-weight:normal;" | Accelerator Enabled/Disabled
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | Last scan
| style="font-weight:normal;" | Time since last host management scan has been done
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | bpcd test
| style="font-weight:normal;" |
|-
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | config test
| style="font-weight:normal;" | NBU bpgetconfig test
|- style="font-weight:normal;"
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | 1556 port
| pbx port
|- style="font-weight:normal;"
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | 13724 port
| vnetd port
|- style="font-weight:normal;"
| style="font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;" | 13782 port
| bpcd port
|}

[[File:HostMgmtConnectivityTestOriginResultMedia.JPG | border|1100x800px]]
Figure3

[[File:HostMgmtConnectivityTestOriginResultClient.JPG | border|1100x800px]]
Figure4

===Step 4===

Now as shown in Figure 2 there are different actions which can be performed on NBU hosts.
Below table shows all the Actions that can be performed on the NBU hosts.

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Do not select Update accelerator track-log destination, Remove origin from host properites,Make destination the master in host properties unless you are certain to use the NBU host with destination master server.
Before running Push destination certificate ,reset the Netbackup security level for certificate deployment to Medium.
|
|}

{|class="wikitable" style="border:5px double maroon" font-family:Arial, Helvetica, sans-serif !important align=center cellpadding=50px width=50%;;"
|- style="font-weight:bold; text-align:center; font-size:15px; font-family:'Arial Black', Gadget, sans-serif !important;;"
| Action
| style="font-weight:normal; text-align:center;" | Description
|-
| style="font-size:15px; font-family:Arial, Helvetica, sans-serif !important;;" | Run origin connectivity test
| Runs a connectivity test for all the NBU hosts from the origin master server
|-
| style="font-size:15px; font-family:Arial, Helvetica, sans-serif !important;;" | Add destination to host properties
| Add the destination master server name to bp.conf (*nix )or registry(Windows) on selected NBU hosts.
|-
| style="font-size:15px; font-family:Arial, Helvetica, sans-serif !important;;" | Update accelerator track-log destination
| Updates the accelerator by forcing the new master server name in the track logs.
|-
| style="font-size:15px; font-family:Arial, Helvetica, sans-serif !important;;" | Push destination certificate
| It adds the CA Certificate and host ID certificate from the destination master server to the selected NBU hosts.
|-
| style="font-size:15px; font-family:Arial, Helvetica, sans-serif !important;;" | Run destination connectivity
| Runs a connectivity test for all the NBU hosts the destination master server
|-
| Remove origin from host properites
| Deletes the master server name from bp.conf (*nix) or registry(Windows) on selected NBU hosts
|-
| Make destination the master in host properties
| In case when there are both origin and destination master server name in bp.conf(*nix) or registry(Windows) selecting and running this option will promote the destination master server name over origin.
|}

Follow the above steps for any Action to be performed in Host Management and fix any unexpected [[File:RedTick.JPG | border|20x20px]].

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Connecitivity test in Actions always take precedence before any other Action, be it from the origin or destination master server.
|
|}

[[Finalize|Jump to Finalize]]

[[Monitoring |Return to Progress]]

Reporting and Logging

2020-09-02T12:49:19Z

Admin: /* Restore Logs */

== Headline ==

In terms of reporting and logging Tranzman has categorised them in to five sections which can be viewed from Views on Tranzman UI on the sidebar.

[[File:Sidebar.jpg|border|160x340px]]

===Reports===

Tranzman Appliance has a reporting feature which is classified further in to different sections.Statistics are displayed as different types of chart.User can choose to see those reports either as for individual
environments or for all environments.Click on Views -> Reports to access those charts.On the extreme top right corner there is a button named Selections which is used to control the display of the charts.

[[File:ReportsFullSelections.jpg|border|100x100px]] will display the charts against data selected for migration.

[[File:ReportsNoneSelections.jpg|border|100x100px]] will display the charts against non selected data.

[[File:ReportsBothSelections.jpg|border|100x100px]] will display the charts against both selected and non selected data.

Below picture shows the charts against the selected data.

[[File:SelectedDataReports.jpg|border|1100x800px]]

===Alerts===

Any errors or failures will be logged under Alerts.

[[File:Alerts.jpg|border|1100x800px]]

===Activity Monitor===

Activity Monitor section provides information of all the jobs that has run or are running on the Tranzman appliance.Jobs could be filtered by Environment,Action,State,Job Number.

[[File:ActivityMonitor.jpg|border|1100x800px]]

===Restore Logs===

Restore specific logs are shown in the Restore logs section. It provides information for :-
Image - ImageId used for restore
Path - Source data path
Device - NFS/CIFS mounted on Appliance for restore
New path - Destination path for restore
State - State of restore like new,completed,error etc.

{|style="padding: 5px; width: 85%;"
| style="width: 1%;"|[[File:Note.png|30px]]|| style="padding: 10px; width: 85%;"|'''Note:''' Restore Logs are shown only when Tranzman is used to restore the data as files i.e. when migration type is
"Recovery to Files"
|
|}

===Audit===

Auditing is enabled by default on tranzman and all the audit related logs could be viewed from Audit section.

[[File:AuditLogs.jpg|border|1100x800px]]

[[ Monitoring | Jump to the Dashboard to Monitor the transition ]]

Reporting and Logging

2020-09-02T12:46:52Z

Admin:

== Headline ==

In terms of reporting and logging Tranzman has categorised them in to five sections which can be viewed from Views on Tranzman UI on the sidebar.

[[File:Sidebar.jpg|border|160x340px]]

===Reports===

Tranzman Appliance has a reporting feature which is classified further in to different sections.Statistics are displayed as different types of chart.User can choose to see those reports either as for individual
environments or for all environments.Click on Views -> Reports to access those charts.On the extreme top right corner there is a button named Selections which is used to control the display of the charts.

[[File:ReportsFullSelections.jpg|border|100x100px]] will display the charts against data selected for migration.

[[File:ReportsNoneSelections.jpg|border|100x100px]] will display the charts against non selected data.

[[File:ReportsBothSelections.jpg|border|100x100px]] will display the charts against both selected and non selected data.

Below picture shows the charts against the selected data.

[[File:SelectedDataReports.jpg|border|1100x800px]]

===Alerts===

Any errors or failures will be logged under Alerts.

[[File:Alerts.jpg|border|1100x800px]]

===Activity Monitor===

Activity Monitor section provides information of all the jobs that has run or are running on the Tranzman appliance.Jobs could be filtered by Environment,Action,State,Job Number.

[[File:ActivityMonitor.jpg|border|1100x800px]]

===Restore Logs===

Restore specific logs are shown in the Restore logs section. It provides information for :-
Image - ImageId used for restore
Path - Source data path
Device - NFS/CIFS mounted on Appliance for restore
New path - Destination path for restore
State - State of restore like new,completed,error etc.

===Audit===

Auditing is enabled by default on tranzman and all the audit related logs could be viewed from Audit section.

[[File:AuditLogs.jpg|border|1100x800px]]

[[ Monitoring | Jump to the Dashboard to Monitor the transition ]]

Reporting and Logging

2020-09-02T12:46:32Z

Admin:

== Headline ==

In terms of reporting and logging Tranzman has categorised them in to five sections which can be viewed from Views on Tranzman UI on the sidebar.

[[File:Sidebar.jpg|border|160x340px]]

===Reports===

Tranzman Appliance has a reporting feature which is classified further in to different sections.Statistics are displayed as different types of chart.User can choose to see those reports either as for individual
environments or for all environments.Click on Views -> Reports to access those charts.On the extreme top right corner there is a button named Selections which is used to control the display of the charts.

[[File:ReportsFullSelections.jpg|border|100x100px]] will display the charts against data selected for migration.

[[File:ReportsNoneSelections.jpg|border|100x100px]] will display the charts against non selected data.

[[File:ReportsBothSelections.jpg|border|100x100px]] will display the charts against both selected and non selected data.

Below picture shows the charts against the selected data.

[[File:SelectedDataReports.jpg|border|1100x800px]]

===Alerts===

Any errors or failures will be logged under Alerts.

[[File:Alerts.jpg|border|1100x800px]]

===Activity Monitor===

Activity Monitor section provides information of all the jobs that has run or are running on the Tranzman appliance.Jobs could be filtered by Environment,Action,State,Job Number.

[[File:ActivityMonitor.jpg|border|1100x800px]]

===Restore Logs===

Restore specific logs are shown in the Restore logs section. It provides information for :-
Image - ImageId used for restore
Path - Source data path
Device - NFS/CIFS mounted on Appliance for restore
New path - Destination path for restore
State - State of restore like new,completed,error etc.

[[File:RestoreLogs.jpg|border|1100x800px]]

===Audit===

Auditing is enabled by default on tranzman and all the audit related logs could be viewed from Audit section.

[[File:AuditLogs.jpg|border|1100x800px]]

[[ Monitoring | Jump to the Dashboard to Monitor the transition ]]

File:ActivityMonitor.jpg

2020-09-02T12:46:03Z

Admin: Admin uploaded a new version of File:ActivityMonitor.jpg

2020-09-01T10:59:24Z

Admin:

Monitoring

2020-09-01T10:59:14Z

Admin:

== Headline ==

The Tranzman Dashboard provides the ability to check state of Environments, Tranzman Resources(CPU, RAM, Tranzman specific filesystems), Migration State, Service Status , Progress and Config Migration.
Tranzman UI is very flexible as it enables end user to perform majority of migration related steps through UI.

Below is a brief of all the sections :

===Tranzman Resources===

This section enables you to monitor:-

*Filesystem utilization.
*CPU utilization.
*Memory utilization.

[[File:Resources.JPG | border|400x400px]]

===Environments Details===

This sections enables you to check different backup environment related components. e.g. Number of backup images i.e #Img Count, amount of backup data #Size Protected(TB),platform etc.
Main highlight is the state of Environment. If the environment state is [[File:Pause.JPG | border|45x45px]] then it implies an error on the respective backup environment during transition and needs to
be resolved.The Views section on the sidebar can further help you dig further to find the root cause or to collect logs([[ Reporting and Logging| Reference for logs and reports ]]) and [[ Contact | Contact ]] Stone Ram Support for further assistance.
A [[File:Resume.JPG | border|45x45px]] is a normal state.

[[File:EnvironmentsDetails.JPG | border|1100x800px]]

===Migration State===

This section reports the progress of the catalog migrated (for same vendor migrations) ????

[[File:MigrationState.JPG | border|400x400px]]

===Service Status===

This section highlights the state of different services like NFS Service ,Audit service etc. Any red icon in this sections means the service is not running and need to be checked.

[[File:ServiceStatus.JPG | border|400x400px]]

===Progress===

The Progress section has details like migration start date,planned switchover date , possible switchover date based on transfer speed.

[[File:Progress.JPG | border|400x400px]]

===Config Migration===

The Config Migration section highlights the state of Objects(Storage Servers, Policies, Residencies etc.) selected for migration. If selected for migration then you can click and check the state of all those objects i.e. whether they
are imported(created on destination master server) or excluded from migration.

[[File:ConfigMigration.JPG | border|400x400px]]

Once transition is completed you can jump to the Recovery Documentation section to start restoring the data.

[[ Manage Hosts | Jump to Host Management for managing certificates ]]
[[ Recoverydocs | Jump to Recovery Documentation for restoring data ]]

Admin:

2020-07-15T10:00:53Z

Admin:

This is the installation guide for creating your own bootable USB for TZM install on to physical servers.
__NOTOC__

==='''Step 1'''===

Launch Rufus with administrator privileges.

[[ File: Picture_Step_1.JPG |20x|border ]]

==='''Step 2'''===

Give the machine a unique name that will make it easy to identify. i.e. Tranzman

[[File:Create_VA_02.JPG]]

==='''Step 3'''===

Choose in which '''DataStore''' the machine and all its files will reside. In our example we are using DS1.

[[File:Create_VA_03.JPG]]

==='''Step 4'''===

Select the Virtual Machine Version for the VA. Which version you require depends on your environment; your own Systems Administrator may advise you on this.

[[File:Create_VA_04.JPG]]

==='''Step 5'''===

Now we select the type of the Guest Operating System. We have chosen '''CentOS 4/5/6/7 (64-bit)''' for higher compatibility.

[[File:Create_VA_05.JPG]]

==='''Step 6'''===

Configure the machine's CPU. The number of '''Virtual Socket''' and '''Cores per Virtual Socket''' will have been determined [[Planning|during the planning phase]].

[[File:Create_VA_06.JPG]]

==='''Step 7'''===

Configure memory. The amount of RAM should have been determined [[Planning|during the planning phase]].

[[File:Create_VA_07.JPG]]

==='''Step 8'''===

For the network type, one adapter type of E1000 is recommended for better compatibility. Do not forget to tick the option '''"Connect at Power On"'''.

[[File:Create_VA_08.JPG]]

==='''Step 9'''===

Storage controller can be left on the default of '''"LSI Logic Parallel'''.

[[File:Create_VA_09.JPG]]

==='''Step 10'''===

Please select to use a new disk and give it a '''3GB''' size for OS installation.

[[File:Create_VA_3GB_Disk.JPG]]

==='''Step 11'''===

When '''Advanced Options''' has been reached, the default settings can be left in place for the '''Virtual Device Node'''.

==='''Step 12'''===

Before we complete the deployment of the machine, we need to tick '''"Edit the Virtual Machine Settings Before Completion"''' as extra hard drives need to be added.

==='''Step 13'''===

Add a new Hardware, select Hard Disk, and then '''"Create a new virtual disk"'''.

[[File:Create_VA_12.JPG]]

==='''Step 14'''===

Repeat the process in '''Step 13''' to add all of the required disks. Recommended values are as follows.

: '''SWAP''' = Twice the value of RAM assigned to the machine. (8GB RAM = 16GB of SWAP Partition)
: '''LOG''' = A minimum of 5GB is recommended
: '''DATA''' = A minimum of 25GB is recommended
: '''DATABASE''' = A minimum of 20GB is recommended
: '''DATASTORE''' = See [[Planning]]

If in doubt please get in contact with one of our consultants for optimal sizes depending on the size of the environment that would be migrated with Tranzman.

==='''Step 15'''===

While still under the Hardware options, add a new CD/DVD and point it to the location of the ISO file provided by Stone Ram Ltd, and ensure that the option or "Connect at power on" is enabled. In our case this has been copied to a "software" folder on the VMWare host itself.

[[File:Create_VA_Add_DVD.JPG]]

==='''Step 16'''===

Force the machine to launch the Bios Setup on first use, so that the option to boot from DVD can be changed.

[[File:Create_VA_Boot_Bios.JPG]]

==='''Step 17'''===

To finish click on '''"Power on Virtual Machine"''' and follow the next tutorial on [[Install TZM Server]].

----
[[Installation|Back to installation]].