Difference between revisions of "Overview"

From Tranzman Documentation
Jump to: navigation, search
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
  
−
 
+
__TOC__
−
==Transitioning Backup Environments==
+
<br>
−
 
 
−
Transition refers to the process of migrating between backup environments. This can occur either within the same backup vendor or across different backup vendors. <br>
 
−
When migrating backup domains, the goal is to ensure quicker and easier access to the latest software, hardware, and technologies (such as cloud, virtualization, and clustering).<br>
 
 
<br>
 
<br>
−
Currently, there are limited software solutions that can handle this transition smoothly and simply.<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>
−
===Migration Use Cases===
+
  <p style="font-size:1.2em; text-align:left;">
−
 
+
    Migrating backup environments — whether within the same vendor or across different vendors
−
'''1. Operational Reasons:'''
+
      provides access to the latest software, hardware, and technologies such as cloud, virtualization, and clustering.<br>
−
Changing software vendors
+
    Currently, few solutions ensure a smooth transition.
−
Shifting platforms (e.g., adopting a new operating system, high availability solutions, or cloud services
+
  </p>
−
Simplifying management (consolidating multiple environments or splitting a large environment)
+
</div>
−
 
 
−
'''2. Business Reasons:'''
 
−
Mergers and acquisitions
 
−
Spin-offs
 
−
Compliance with regulations
 
−
 
 
−
===Introducing <b style='font-color:red'}>Tranzman</b>===
 
−
[[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, Tranzman facilitates seamless migration. <br>
 
−
Notably, it was developed by engineers who previously designed and built migration tools for Veritas.<br>
 
−
 
 
−
 
 
−
===Why Choose Tranzman for Migration?===
 
−
 
 
−
'''1. Near ZERO Downtime:'''
 
−
Tranzman ensures seamless migration without causing any disruptions to either the origin or destination backup environments. Downtime is only necessary during the switch-over to the destination.
 
−
 
 
−
'''2. Structured Approach with Risk Mitigation:'''
 
−
Tranzman follows a well-defined approach that emphasizes risk mitigation.
 
−
It provides the ability to easily revert to the original environment and automates the cleanup of any migrated components.
 
−
 
 
−
'''3. Release Flexibility:'''
 
−
Tranzman allows direct transitions from older versions to the latest ones, bypassing intermediate upgrades.
 
  
−
'''4. Granular Selectivity:'''
 
−
Users can selectively choose images and configurations based on predefined rules, simplifying domain splits and partial transitions.
 
  
−
'''5. Concurrent Transitions:'''
+
<div style="max-width:80%; margin: 0 auto;">
−
Tranzman supports both "many to one" merges in a single approach and "one to many" splits with selected components for each destination.
 
  
−
'''6. Detailed Assessment:'''
+
  <div style="background-color:#edf7ff; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
−
Pre-assessment and post-transition assessments provide comprehensive information about the origin and destination environments, ensuring consistency during the transition.
+
    <h2 style="border-bottom:2px solid #bbdefb; padding-bottom:0.5rem; font-size:1.5em;">Migration Use Cases</h2>
 +
    <h3 style="font-size:1.2em;">Operational Reasons</h3>
 +
    <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>
  
−
'''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:===
+
  <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>
  
−
'''1. Same Vendor Transition:'''
 
−
Useful when the hardware is incompatible with the latest backup software version or when transitioning to a new platform or adopting new technologies.<br>
 
−
Tranzman currently supports transitions between NetBackup and NetBackup servers, as well as between DataProtector and DataProtector.
 
  
−
'''2. Cross Vendor Transition:'''
+
  <div style="background-color:#eff8f0; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
−
Transitions all catalog objects (and some scheduling/workload information) from Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) to NetBackup.
+
    <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>
  
−
'''3. Recovery Without Vendor:'''
 
−
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''. <br>
 
−
Tranzman efficiently retrieves and restores the indexed image information, making it a valuable alternative to traditional backup servers for legacy restores.
 
  
 +
  <div style="background-color:#fffbf4; padding:1.5rem; border-radius:8px; box-shadow:0 2px 4px rgba(0,0,0,0.06);">
 +
    <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>
  
  
 +
  <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;">
 +
    <p style="font-size:1.2em; max-width:80%; margin:auto;">Refer to the supportability matrix page for more details. </p>
 +
  </div>
  
 +
</div>
  
−
'' Refer supportability matrix page for more information ''
 
  
  
  
  
−
{| class="wikitable"  style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
+
<div style="display:flex; justify-content:space-between; margin-top:2rem; padding:1rem; background-color:#ffffff; max-width:90%; margin: 2rem auto 0;">
−
|-
+
  <div style="text-align:left;">
−
| [[Image:prev_icon.jpg|30px|link=QuickLinks]]
+
    [[File:prev_icon.jpg|30px|link=QuickLinks]] [[QuickLinks|Previous]]
−
|| [[Image:next_icon.jpg|30px|link=Architecture]]
+
  </div>
−
|}
+
  <div style="text-align:right;">
 +
    [[Architecture|Next]] [[File:next_icon.jpg|30px|link=Architecture]]  
 +
  </div>
 +
</div>

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"