Architecture

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

High Level Process Flow

• All processes in the Tranzman Appliance depends on the Relational Database and the QueueManager process.

• The QueueManager is responsible for updating Actions into the Agents queue and the actions has a list of APIs for the Tranzman Agent. The QueueManager manages the flow of actions for all the migrations.

• Agent communicates with the Data Transfer Engine to retrieve Actions from the Queue and to PUT/GET catalog data associated with it.

• The Actions that the Agents retrieve from its Queue perform one of many different actions.

Logical design for Same Vendor Transition (SVT)

Logical design for Cross Vendor Transition (CVT)

Logical design for Recovery Without Vendor (RWV)

Actions

Actions has a sequence of instructions to be executed by the agent on the backup server to complete a specific procedure as part of Transition.

The below table shows all the Actions available in Tranzman.

Init	Runs once on origin and destination as part of the initial discovery to get system information.
QueryProduct	Runs once on origin and destination as part of the initial discovery for detecting the backup product on the system.
QueryConfig	Runs once on the origin and destination to determine the configuration objects (storage, credentials, workloads, etc) on the system.
QueryMedia	Runs cyclic on the origin and destination to determine the media information.
QueryImages	Runs cyclic on the origin and destination to discover all backup images.
CreateConfig	Runs once on the target to create required configuration components.
CreateWorkloads	Runs once on the target to create required backup configuration components.
CrossCheck	Runs daily during data transfer to compare origin and destination data.
ExportImages	Runs cyclic on the origin to export the selected images.
ManipulateImages	Converts / renames components that are mapped between origin and destination.
ImportImages	Runs cyclic on the destination to import the migrated images.
CreateMedia	Runs cyclic on the destination to create / update the media.
CheckConn	Runs on demand on origin and destination to test connectivity of clients, and to push NetBackup certificates
FinalizeOrigin	Runs once on origin during final switchover.
FinalizeDestination	Runs once on destination as part of final switchover.
Assessment	Runs on demand to run Pre-Assessment and Post Acceptance tests before and after migration respectively.
HouseKeeping	Runs cyclic to cleanup the completed info from the Tranzman Database.
PreDuplication	Runs cyclic based on rules to perform Duplications on the Origin if required, as part of a split.
PostDuplication	Runs cyclic based on rules to perform Duplications on the Destination if required,as part of storage migration.

Migration Flow

Same Vendor migration flow

• (1) Export the data and tranfer to Tranzman server.

• (2) Convert the data within Tranzman server.

• (3) Transfer the data to Destination and import it.

Cross Vendor Migration flow

If the backup data is on Tape

• (1) Data converter in Tranzman server reads the data from Tapes directly.

• (2) Optionally, the converted data can be duplicated to a destination storage

If the backup data is on Disk

• (1) Converter reads the data from Origin storage over NFS/CIFS

• (2) Optionally, can duplicate the converted images to native destination storage

If the backup data is encrypted or deduplicated

• (1) Pre-duplicate the data to shared storage

• (2) Converter reads the data from shared storage

• (3) Optionally, the data can be duplicated to native destination storage

Return to Previous

Go to Next