Architecture

Tranzman Appliance Architecture & Migration Flow

Tranzman is delivered as an appliance, ready for deployment out-of-the-box.
It can be installed on either a virtual machine or a physical server using a bootable ISO or OVA.
Unlike traditional software binaries, Tranzman is an appliance and therefore not available as an executable binary or RPM.

Tranzman Components

Appliance Component

• Queue Manager (tzmqm)
• Data Transfer Engine (tzmtd)

• Built on Rocky Linux sources and utilizes an internal PostgreSQL database.
• Accessible via CLISH (Command Line Interface Shell) and web user interface (webUI), hosted on an internal web server running nginx.
• Configuration Converters, Catalog Converters, and Data Converters manage all data manipulations internally.

Agent Component

• Acts as the communication bridge between Tranzman and the backup server.
• Waits for instructions from the Tranzman Server.
• Executes received actions and reports status back to the Tranzman Server.
• Minimal standalone binary installed on the backup server, initiating tzmclnt and other necessary processes.

High-Level Process Flow

• All Tranzman Appliance processes rely on the relational database and the QueueManager.
• The QueueManager updates action queues for Agents, handling all migration-related operations.
• The Agent interacts with the Data Transfer Engine, fetching instructions and performing PUT/GET operations for catalog data.
• Actions retrieved by the Agents trigger various migration procedures.

Same Vendor Transition (SVT)

Cross Vendor Transition (CVT)

Recovery Without Vendor (RWV)

Actions

Actions are sequences of instructions executed by the agent on the backup server to facilitate transitions.

<thead> </thead> <tbody>

     </tbody>

Action	Description
Init	Runs once on both origin and destination during initial system discovery.
QueryProduct	Identifies the backup product installed on both origin and destination.
QueryConfig	Detects configuration objects (e.g., storage, credentials, workloads) on both systems.
QueryMedia	Continuously collects media-related data on both systems.
QueryImages	Continuously discovers all backup images on origin and destination.
CreateConfig	Creates necessary configuration components on the target system.
CreateWorkloads	Establishes required backup configurations on the target system.
CrossCheck	Performs daily data comparisons between origin and destination.
ExportImages	Cyclically exports selected images from the origin system.
ManipulateImages	Renames or converts components mapped between origin and destination.
ImportImages	Imports migrated images cyclically into the destination system.
CreateMedia	Updates or creates new media on the destination system.
CheckConn	Tests client connectivity and pushes NetBackup certificates.
FinalizeOrigin	Completes final origin system preparations before switchover.
FinalizeDestination	Completes final destination system preparations post-switchover.
Assessment	Executes pre-assessment and post-transition validation tests.
HouseKeeping	Cyclically clears completed records from the Tranzman Database.
PreDuplication	Performs pre-duplication on the origin based on split migration rules.
PostDuplication	Performs post-duplication on the destination storage as part of migration.

Migration Flow

Same Vendor Migration Flow

Cross Vendor Migration Flow

If the backup data is stored on Tape

• (1) The Tranzman server reads data directly from tapes via its Data Converter.
• (2) Optionally, converted data may be duplicated onto a destination storage system.

If the backup data is stored on Disk

• (1) The converter reads data from the origin storage over NFS/CIFS.
• (2) Optionally, converted images may be duplicated onto the native destination storage.

If the backup data is encrypted or deduplicated

• (1) Pre-duplicate the data onto shared storage.
• (2) The converter reads the data from shared storage.
• (3) Optionally, data may be duplicated onto native destination storage.

    Previous

   Next