Difference between revisions of "Overview"
| 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. | ||
| − | + | Currently, there are limited software solutions that handle this transition smoothly and simply. | |
| − | + | === Migration Use Cases === | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | ===Migration Use Cases=== | ||
'''1. Operational Reasons:''' | '''1. Operational Reasons:''' | ||
| − | Changing software vendors | + | * Changing software vendors |
| − | Shifting platforms (e.g., adopting a new operating system, high availability solutions, or cloud services | + | * 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) | + | * Simplifying management (consolidating multiple environments or splitting a large environment) |
'''2. Business Reasons:''' | '''2. Business Reasons:''' | ||
| − | Mergers and acquisitions | + | * Mergers and acquisitions |
| − | Spin-offs | + | * Spin-offs |
| − | Compliance with regulations | + | * Compliance with regulations |
| + | |||
| + | === Introducing '''Tranzman''' === | ||
| − | |||
[[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. Developed by engineers who previously designed migration tools for Veritas, Tranzman facilitates seamless migration. |
| − | |||
| − | + | === Why Choose Tranzman for Migration? === | |
| − | ===Why Choose Tranzman for Migration?=== | ||
'''1. Near ZERO Downtime:''' | '''1. Near ZERO Downtime:''' | ||
| − | Tranzman ensures seamless migration without | + | Tranzman ensures seamless migration without disrupting either the origin or destination backup environments. Downtime is only required 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 | + | 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:''' | '''3. Release Flexibility:''' | ||
| − | Tranzman | + | Tranzman enables direct transitions from older versions to the latest ones, bypassing intermediate upgrades. |
'''4. Granular Selectivity:''' | '''4. Granular Selectivity:''' | ||
| Line 43: | Line 38: | ||
'''5. Concurrent Transitions:''' | '''5. Concurrent Transitions:''' | ||
| − | Tranzman supports both "many to one" merges | + | Tranzman supports both "many to one" merges and "one to many" splits with selected components for each destination. |
'''6. Detailed Assessment:''' | '''6. Detailed Assessment:''' | ||
| Line 50: | Line 45: | ||
'''7. Topology Transitions:''' | '''7. Topology Transitions:''' | ||
Tranzman can handle various topology changes, including: | Tranzman can handle various topology changes, including: | ||
| − | Cluster to non-cluster (and vice versa) | + | * Cluster to non-cluster (and vice versa) |
| − | Windows to *nix (and vice versa) | + | * Windows to *nix (and vice versa) |
| − | Virtual to physical (and vice versa, including flex instances) | + | * Virtual to physical (and vice versa, including flex instances) |
| − | Bring Your Own (BYO) to appliance (and vice versa) | + | * Bring Your Own (BYO) to appliance (and vice versa) |
| − | ===Tranzman Use Cases:=== | + | === Tranzman Use Cases: === |
'''1. Same Vendor Transition:''' | '''1. Same Vendor Transition:''' | ||
| − | + | 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. | |
| − | |||
'''2. Cross Vendor Transition:''' | '''2. Cross Vendor Transition:''' | ||
| − | + | Tranzman 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 | + | 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. |
| − | Tranzman efficiently retrieves and restores the indexed image information, making it a valuable alternative to traditional backup servers for legacy restores. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | ''Refer to the supportability matrix page for more information.'' | ||
| − | {| class="wikitable" | + | {| 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]] |
|} | |} | ||
Revision as of 04:49, 20 February 2025
Contents
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.
Currently, there are limited software solutions that 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. Developed by engineers who previously designed migration tools for Veritas, Tranzman facilitates seamless migration.
Why Choose Tranzman for Migration?
1. Near ZERO Downtime: Tranzman ensures seamless migration without disrupting either the origin or destination backup environments. Downtime is only required during the switch-over to the destination.
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: Tranzman enables 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 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: 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.
2. Cross Vendor Transition: Tranzman transitions all catalog objects (and some scheduling/workload information) from Commvault, BackupExec, DataProtector, and SpectrumProtect (TSM) to NetBackup.
3. Recovery Without Vendor: 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.
Refer to the supportability matrix page for more information.
|
|