Difference between revisions of "Overview"

From Tranzman Documentation
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Transitioning Backup Environments ==
 
  
−
Transitioning backup environments involves migrating between backup setups, whether within the same vendor or across different vendors. The goal is to provide faster and easier access to the latest software, hardware, and technologies, including cloud, virtualization, and clustering.
+
__TOC__
 +
<br>
 +
<br>
 +
<div style="background-color:#fde9e9; padding: 2rem; text-align:center; margin-bottom:2rem; border-radius:8px; max-width:80%; margin: 0 auto;">
 +
  <h1 style="border-bottom:none; font-size:2.5em; font-weight:bold;">Transitioning Backup Environments</h1>
 +
  <p style="font-size:1.2em; text-align:left;">
 +
    Migrating backup environments — whether within the same vendor or across different vendors
 +
      provides access to the latest software, hardware, and technologies such as cloud, virtualization, and clustering.<br>
 +
    Currently, few solutions ensure a smooth transition.
 +
  </p>
 +
</div>
  
−
Currently, there are limited software solutions that handle this transition smoothly and simply.
 
  
−
=== Migration Use Cases ===
+
<div style="max-width:80%; margin: 0 auto;">
  
−
'''1. Operational Reasons:'''
+
  <div style="background-color:#edf7ff; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
−
* Changing software vendors
+
    <h2 style="border-bottom:2px solid #bbdefb; padding-bottom:0.5rem; font-size:1.5em;">Migration Use Cases</h2>
−
* Shifting platforms (e.g., adopting a new operating system, high availability solutions, or cloud services)
+
    <h3 style="font-size:1.2em;">Operational Reasons</h3>
−
* Simplifying management (consolidating multiple environments or splitting a large environment)
+
    <ul>
 +
      <li>Switching software vendors</li>
 +
      <li>Adopting new platforms (e.g., operating systems, cloud solutions, high availability setups)</li>
 +
      <li>Streamlining management (merging environments or splitting a large one)</li>
 +
    </ul>
 +
    <h3 style="font-size:1.2em;">Business Reasons</h3>
 +
    <ul>
 +
      <li>Mergers and acquisitions</li>
 +
      <li>Spin-offs</li>
 +
      <li>Regulatory compliance</li>
 +
    </ul>
 +
  </div>
  
−
'''2. Business Reasons:'''
 
−
* Mergers and acquisitions
 
−
* Spin-offs
 
−
* Compliance with regulations
 
  
−
=== Introducing '''Tranzman''' ===
+
  <div style="background-color:#fef3f7; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
 +
    <h2 style="border-bottom:2px solid #f8bbd0; padding-bottom:0.5rem; font-size:1.5em;">Introducing '''Tranzman'''</h2>
 +
    [[File:Tranzman.jpg|thumb|center|300px|Tranzman Logo]]
 +
    <p>
 +
      Tranzman is an advanced solution for enterprise backup migration, handling various operating systems, clustering technologies, hardware, and software versions.
 +
      Developed by engineers who previously designed migration tools for Veritas, it ensures seamless transitions.
 +
    </p>
 +
  </div>
  
−
[[File:Tranzman.jpg]]
 
  
−
Tranzman offers a unique software solution for transitioning enterprise backup environments, regardless of the operating system, clustering technologies, hardware, or software versions. Developed by engineers who previously designed migration tools for Veritas, Tranzman facilitates seamless migration.
+
  <div style="background-color:#eff8f0; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
 +
    <h2 style="border-bottom:2px solid #c8e6c9; padding-bottom:0.5rem; font-size:1.5em;">Why Choose Tranzman for Migration?</h2>
 +
    <ul style="padding-left:0; list-style:none;">
 +
      <li style="margin-bottom:1rem;">'''Near ZERO Downtime:''' Migration occurs without disruption, requiring downtime only during final switch-over.</li>
 +
      <li style="margin-bottom:1rem;">'''Structured Approach with Risk Mitigation:''' Easy rollback to the original environment and automated cleanup of migrated components.</li>
 +
      <li style="margin-bottom:1rem;">'''Release Flexibility:''' Direct transitions from older versions to the latest without intermediate upgrades.</li>
 +
      <li style="margin-bottom:1rem;">'''Granular Selectivity:''' Selective migration based on predefined rules, allowing domain splits and partial transitions.</li>
 +
      <li style="margin-bottom:1rem;">'''Concurrent Transitions:''' Supports "many to one" merges and "one to many" splits with tailored components for each destination.</li>
 +
      <li style="margin-bottom:1rem;">'''Detailed Assessment:''' Comprehensive pre- and post-transition assessments to ensure consistency.</li>
 +
      <li style="margin-bottom:1rem;">'''Topology Transitions:''' Transitions across various setups:<br>
 +
        <ul>
 +
          <li>Cluster to non-cluster (and vice versa)</li>
 +
          <li>Windows to Linux-based systems (and vice versa)</li>
 +
          <li>Virtual to physical environments (including flexible instances)</li>
 +
          <li>BYO (Bring Your Own) to appliance models (and vice versa)</li>
 +
        </ul>
 +
      </li>
 +
    </ul>
 +
  </div>
  
−
=== Why Choose Tranzman for Migration? ===
 
  
−
'''1. Near ZERO Downtime:'''
+
  <div style="background-color:#fffbf4; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
−
Tranzman ensures seamless migration without disrupting either the origin or destination backup environments. Downtime is only required during the switch-over to the destination.
+
    <h2 style="border-bottom:2px solid #ffe0b2; padding-bottom:0.5rem; font-size:1.5em;">Tranzman Use Cases</h2>
 +
    <h3 style="font-size:1.2em;">Same Vendor Transition</h3>
 +
    <p>Useful when hardware is incompatible with the latest backup software or when transitioning to a new platform.</p>
 +
    <ul>
 +
      <li>NetBackup to NetBackup</li>
 +
      <li>DataProtector to DataProtector</li>
 +
    </ul>
 +
    <h3 style="font-size:1.2em;">Cross Vendor Transition</h3>
 +
    <p>Migrates catalog objects (and some scheduling/workload details) across:</p>
 +
    <ul>
 +
      <li>Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) → NetBackup</li>
 +
    </ul>
 +
    <h3 style="font-size:1.2em;">Recovery Without Vendor Dependence</h3>
 +
    <p>The '''Tranzman appliance''' consolidates catalogs and enables on-demand restores from:</p>
 +
    <ul>
 +
      <li>NetBackup, BackupExec, Commvault, DataProtector, and SpectrumProtect</li>
 +
    </ul>
 +
    <p>Tranzman efficiently retrieves and restores indexed image data, serving as a powerful legacy recovery alternative.</p>
 +
  </div>
  
−
'''2. Structured Approach with Risk Mitigation:'''
 
−
Tranzman follows a well-defined approach focused on risk mitigation, allowing easy reversion to the original environment and automating the cleanup of any migrated components.
 
  
−
'''3. Release Flexibility:'''
+
  <div style="background-color:#f8e2b3; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06); text-align:center; font-style:italic; margin: 0 auto;">
−
Tranzman enables direct transitions from older versions to the latest ones, bypassing intermediate upgrades.
+
    <p style="font-size:1.2em; max-width:80%; margin:auto;">Refer to the supportability matrix page for more details. </p>
 +
  </div>
  
−
'''4. Granular Selectivity:'''
+
</div>
−
Users can selectively choose images and configurations based on predefined rules, simplifying domain splits and partial transitions.
 
  
−
'''5. Concurrent Transitions:'''
 
−
Tranzman supports both "many to one" merges and "one to many" splits with selected components for each destination.
 
  
−
'''6. Detailed Assessment:'''
 
−
Pre-assessment and post-transition assessments provide comprehensive information about the origin and destination environments, ensuring consistency during the transition.
 
  
−
'''7. Topology Transitions:'''
 
−
Tranzman can handle various topology changes, including:
 
−
* Cluster to non-cluster (and vice versa)
 
−
* Windows to *nix (and vice versa)
 
−
* Virtual to physical (and vice versa, including flex instances)
 
−
* Bring Your Own (BYO) to appliance (and vice versa)
 
  
−
=== Tranzman Use Cases: ===
 
  
−
'''1. Same Vendor Transition:'''
+
<div style="display:flex; justify-content:space-between; margin-top:2rem; padding:1rem; background-color:#ffffff; max-width:90%; margin: 2rem auto 0;">
−
Tranzman is useful when the hardware is incompatible with the latest backup software version or when transitioning to a new platform or adopting new technologies. It currently supports transitions between NetBackup and NetBackup servers, as well as between DataProtector and DataProtector.
+
  <div style="text-align:left;">
−
 
+
    [[File:prev_icon.jpg|30px|link=QuickLinks]] [[QuickLinks|Previous]]
−
'''2. Cross Vendor Transition:'''
+
  </div>
−
Tranzman transitions all catalog objects (and some scheduling/workload information) from Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) to NetBackup.
+
  <div style="text-align:right;">
−
 
+
    [[Architecture|Next]] [[File:next_icon.jpg|30px|link=Architecture]]  
−
'''3. Recovery Without Vendor:'''
+
  </div>
−
The Tranzman appliance enables the consolidation of catalogs and on-demand restores from NetBackup, BackupExec, Commvault, DataProtector, and SpectrumProtect—all without relying on a specific backup vendor for restoration. Tranzman efficiently retrieves and restores the indexed image information, making it a valuable alternative to traditional backup servers for legacy restores.
+
</div>
−
 
 
−
''Refer to the supportability matrix page for more information.''
 
−
 
 
−
{| class="wikitable" style="margin:auto;width:100%;color:blue;text-align:center;border-style:ridge;"
 
−
|-
 
−
| [[File:prev_icon.jpg|30px|link=QuickLinks]]
 
−
|| [[File:next_icon.jpg|30px|link=Architecture]]
 
−
|}
 

Latest revision as of 08:23, 11 September 2025



Transitioning Backup Environments

Migrating backup environments — whether within the same vendor or across different vendors provides access to the latest software, hardware, and technologies such as cloud, virtualization, and clustering.
Currently, few solutions ensure a smooth transition.


Migration Use Cases

Operational Reasons

  • Switching software vendors
  • Adopting new platforms (e.g., operating systems, cloud solutions, high availability setups)
  • Streamlining management (merging environments or splitting a large one)

Business Reasons

  • Mergers and acquisitions
  • Spin-offs
  • Regulatory compliance


Introducing Tranzman

Tranzman Logo

Tranzman is an advanced solution for enterprise backup migration, handling various operating systems, clustering technologies, hardware, and software versions. Developed by engineers who previously designed migration tools for Veritas, it ensures seamless transitions.


Why Choose Tranzman for Migration?

  • Near ZERO Downtime: Migration occurs without disruption, requiring downtime only during final switch-over.
  • Structured Approach with Risk Mitigation: Easy rollback to the original environment and automated cleanup of migrated components.
  • Release Flexibility: Direct transitions from older versions to the latest without intermediate upgrades.
  • Granular Selectivity: Selective migration based on predefined rules, allowing domain splits and partial transitions.
  • Concurrent Transitions: Supports "many to one" merges and "one to many" splits with tailored components for each destination.
  • Detailed Assessment: Comprehensive pre- and post-transition assessments to ensure consistency.
  • Topology Transitions: Transitions across various setups:
    • Cluster to non-cluster (and vice versa)
    • Windows to Linux-based systems (and vice versa)
    • Virtual to physical environments (including flexible instances)
    • BYO (Bring Your Own) to appliance models (and vice versa)


Tranzman Use Cases

Same Vendor Transition

Useful when hardware is incompatible with the latest backup software or when transitioning to a new platform.

  • NetBackup to NetBackup
  • DataProtector to DataProtector

Cross Vendor Transition

Migrates catalog objects (and some scheduling/workload details) across:

  • Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) → NetBackup

Recovery Without Vendor Dependence

The Tranzman appliance consolidates catalogs and enables on-demand restores from:

  • NetBackup, BackupExec, Commvault, DataProtector, and SpectrumProtect

Tranzman efficiently retrieves and restores indexed image data, serving as a powerful legacy recovery alternative.


Refer to the supportability matrix page for more details. 



   Prev icon.jpg Previous

   Next Next icon.jpg
Retrieved from "https://docs.stoneram.com/index.php?title=Overview&oldid=3445"