Difference between revisions of "Overview"
| Line 3: | Line 3: | ||
==Transitioning Backup Environments== | ==Transitioning Backup Environments== | ||
| − | Transition refers to the process of migrating between backup environments. This can occur either within the same backup vendor or across different backup vendors. | + | 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). | + | 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> | |
| − | Currently, there are limited software solutions that can handle this transition smoothly and simply. | + | Currently, there are limited software solutions that can handle this transition smoothly and simply.<br> |
===Migration Use Cases=== | ===Migration Use Cases=== | ||
'''1. Operational Reasons:''' | '''1. Operational Reasons:''' | ||
| − | + | Changing software vendors | |
| − | + | Shifting platforms (e.g., adopting a new operating system, high availability solutions, or cloud services | |
| − | + | Simplifying management (consolidating multiple environments or splitting a large environment) | |
'''2. Business Reasons:''' | '''2. Business Reasons:''' | ||
| − | + | Mergers and acquisitions | |
| − | + | Spin-offs | |
| − | + | Compliance with regulations | |
===Introducing <b style='font-color:red'}>Tranzman</b>=== | ===Introducing <b style='font-color:red'}>Tranzman</b>=== | ||
[[File:Tranzman.jpg]] | [[File:Tranzman.jpg]] | ||
| − | Tranzman offers a unique software solution for transitioning enterprise backup environments. | + | 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> |
| − | Regardless of the operating system, clustering technologies, hardware, or software versions, Tranzman facilitates seamless migration. | + | Notably, it was developed by engineers who previously designed and built migration tools for Veritas.<br> |
| − | Notably, it was developed by engineers who previously designed and built migration tools for Veritas. | ||
| Line 31: | Line 30: | ||
'''1. Near ZERO Downtime:''' | '''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:''' | '''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:''' | '''3. Release Flexibility:''' | ||
| − | + | Tranzman allows direct transitions from older versions to the latest ones, bypassing intermediate upgrades. | |
'''4. Granular Selectivity:''' | '''4. Granular Selectivity:''' | ||
| − | + | Users can selectively choose images and configurations based on predefined rules, simplifying domain splits and partial transitions. | |
'''5. Concurrent Transitions:''' | '''5. Concurrent Transitions:''' | ||
| − | + | 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:''' | '''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:''' | '''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:=== | ===Tranzman Use Cases:=== | ||
'''1. Same Vendor Transition:''' | '''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:''' | '''2. Cross Vendor Transition:''' | ||
| − | + | Transitions all catalog objects (and some scheduling/workload information) from Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) to NetBackup. | |
'''3. Recovery Without Vendor:''' | '''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. | ||
Revision as of 08:16, 27 February 2024
Contents
Transitioning Backup Environments
Transition refers to the process of migrating between backup environments. This can occur either within the same backup vendor or across different backup vendors.
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).
Currently, there are limited software solutions that can handle this transition smoothly and simply.
Migration Use Cases
1. Operational Reasons: Changing software vendors Shifting platforms (e.g., adopting a new operating system, high availability solutions, or cloud services Simplifying management (consolidating multiple environments or splitting a large environment)
2. Business Reasons: Mergers and acquisitions Spin-offs Compliance with regulations
Introducing Tranzman
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.
Notably, it was developed by engineers who previously designed and built migration tools for Veritas.
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: 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: 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:
Useful when the hardware is incompatible with the latest backup software version or when transitioning to a new platform or adopting new technologies.
Tranzman currently supports transitions between NetBackup and NetBackup servers, as well as between DataProtector and DataProtector.
2. Cross Vendor Transition: Transitions all catalog objects (and some scheduling/workload information) from Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) to NetBackup.
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.
Tranzman efficiently retrieves and restores the indexed image information, making it a valuable alternative to traditional backup servers for legacy restores.
Refer supportability matrix page for more information
|
|