Architecture

1. 1. Overview of Tranzman Appliance

Tranzman is a specialized appliance designed for workload migrations between different backup systems. It is delivered as a complete solution, deployable on either virtual machines or physical servers using bootable ISO or OVA formats. Unlike traditional software binaries, Tranzman is not available as an executable binary or RPM, emphasizing its appliance nature.

1. 1. 1. Components of Tranzman

Tranzman consists of two primary components:

• • 1. Appliance Component**

- **Core Framework:** The Tranzman appliance (TZM) includes:

 - **Queue Manager (tzmqm)**
 - **Data Transfer Engine (tzmtd)**

- **Technical Specifications:**

 - Built on **Rocky Linux** with an internal **PostgreSQL** database.
 - Accessible via a **Command Line Interface Shell (CLISH)** and a web user interface (webUI), hosted on an internal **nginx** web server.
 - Includes Configuration Converters, Catalog Converters, and Data Converters for internal manipulations.

• • 2. Agent Component**

- The Agent acts as the interface between Tranzman and the backup server with key functions:

 - Awaits and executes actions from the Tranzman Server.
 - Returns action status results to the Tranzman Server.

- It is a minimal standalone binary installed on the backup server, initiating processes like **tzmclnt**.

1. 1. High-Level Process Flow

The operational flow within the Tranzman appliance relies heavily on its relational database and Queue Manager:

- The **Queue Manager** updates actions into the Agents' queue, managing migration flows effectively. - The **Agent** retrieves actions from the queue and communicates with the Data Transfer Engine to perform necessary PUT/GET operations related to catalog data.

1. 1. 1. Logical Designs

Tranzman supports various migration scenarios with logical designs for:

- **Same Vendor Transition (SVT)** - **Cross Vendor Transition (CVT)** - **Recovery Without Vendor (RWV)**

These designs facilitate structured transitions tailored to specific vendor requirements.

1. 1. Actions in Tranzman

Actions in Tranzman are sequences of instructions executed by the Agent during the transition process. Below is a summary of available actions:

| Action | Description | |---------------------|-----------------------------------------------------------------------------| | **Init** | Runs once on both origin and destination to retrieve system information. | | **QueryProduct** | Detects the installed backup product during initial discovery. | | **QueryConfig** | Determines configuration objects present in the system. | | **QueryMedia** | Gathers media-related information cyclically on both systems. | | **QueryImages** | Discovers all backup images cyclically on both systems. | | **CreateConfig** | Creates necessary configuration components on the target system. | | **CreateWorkloads** | Creates required backup configuration components on the target system. | | **CrossCheck** | Compares data between origin and destination daily during data transfer. | | **ExportImages** | Exports selected images cyclically from the origin system. | | **ManipulateImages** | Converts or renames components mapped between origin and destination. | | **ImportImages** | Imports migrated images cyclically on the destination system. | | **CreateMedia** | Creates or updates media cyclically on the destination system. | | **CheckConn** | Tests connectivity of clients on demand on both systems. | | **FinalizeOrigin** | Finalizes actions on origin during switchover. | | **FinalizeDestination** | Finalizes actions on destination during switchover. | | **Assessment** | Performs Pre-Assessment and Post Acceptance tests around migration events. | | **HouseKeeping** | Cleans up completed information from the Tranzman Database cyclically. | | **PreDuplication** | Performs duplications on origin based on rules if required. | | **PostDuplication** | Performs duplications on destination based on rules if required. |

1. 1. Migration Flows

1. 1. 1. Same Vendor Migration Flow

1. Export data to the Tranzman server. 2. Convert data within the Tranzman server. 3. Transfer and import data to the destination.

1. 1. 1. Cross Vendor Migration Flow

- If backup data is on Tape:

 1. The data converter reads directly from tapes.
 2. Optionally duplicate converted data to destination storage.

- If backup data is on Disk:

 1. The converter reads data from origin storage over NFS/CIFS.
 2. Optionally duplicate converted images to native destination storage.

- If backup data is encrypted or deduplicated:

 1. Pre-duplicate data to shared storage.
 2. Read data from shared storage for conversion.
 3. Optionally duplicate to native destination storage.

This structured approach ensures efficient management of workload migrations across various environments while maintaining integrity and performance throughout the process.

---

This overview provides a comprehensive understanding of Tranzman's architecture, functionality, and operational flows tailored for effective workload migration between different backup vendors.