Difference between revisions of "Architecture"

Revision as of 15:10, 6 January 2023

Introduction

Tranzman comes as an appliance out-of-the-box. It can be deployed in a Virtual machine or physical server using a bootable ISO or OVA.
Tranzman is an appliance and not a software binary and so it is not available as an executable binary or rpm.

Tranzman has two components - An Appliance and an Agent component.

Appliance component

The core framework of Tranzman appliance (TZM) has

Queue Manager (tzmqm)

Data Transfer Engine (tzmtd)

• TZM is built on RHEL8.6 sources and uses an internal database (postgresql).
  
• Appliance can be accessed via CLISH and webUI. Hosts an internal web server running nginx for webUI.
  
• Additionally, Configuration Converters, Catalog Converters and Data Converters (applicable to CVT and RWV) performs all the manipulation internally.
  

Agent component

• This is an interface between Tranzman and the Backup server
• Awaits Actions from the Tranzman Sever
• Execute the Actions received from Tranzman server
• Return the Action status result to the Tranzman Server

Agent is a minimal standalone binary installed on Backup server and it starts tzmclnt and other processes on Backup server

Logical design for Same Vendor Transition (SVT)

Logical design for Cross Vendor Transition (CVT)

Logical design for Recovery Without Vendor (RWV)