Difference between revisions of "Overview"
| Line 22: | Line 22: | ||
It is developed by engineers, who previously designed and developed migration tools for Veritas. | It is developed by engineers, who previously designed and developed migration tools for Veritas. | ||
| − | == Why Tranzman ?== | + | == Why Tranzman?== |
; Near ZERO Downtime | ; Near ZERO Downtime | ||
: Tranzman can perform the migration without any outage to the Origin or Destination backup environments. Downtime is only required when doing switch-over of Destination. | : Tranzman can perform the migration without any outage to the Origin or Destination backup environments. Downtime is only required when doing switch-over of Destination. | ||
| Line 45: | Line 45: | ||
== Tranzman Use cases == | == Tranzman Use cases == | ||
*'''Same Vendor Transition''' | *'''Same Vendor Transition''' | ||
| − | + | Transition between same Backup software. Mostly required when the hardware is unsupported for the latest version of backup software or changing the platform or for adopting new technologies. <br> | |
| + | Tranzman currently supports transition between '''NetBackup''' and '''NetBackup''' servers or between '''DataProtector''' and '''DataProtector''' | ||
*'''Cross Vendor Transition''' | *'''Cross Vendor Transition''' | ||
| − | Transitions all Catalog objects (and some scheduling/ workload information) from Commvault, BackupExec, DataProtector, SpectrumProtect (TSM) to NetBackup | + | Transitions all Catalog objects (and some scheduling/ workload information) from '''Commvault''', '''BackupExec''', '''DataProtector''', '''SpectrumProtect (TSM)''' to '''NetBackup''' |
*'''Recovery Without Vendor''' | *'''Recovery Without Vendor''' | ||
| − | Consolidate catalogs and restores on demand from NetBackup, BackupExec, Commvault, DataProtector and SpectrumProtect through Tranzman Appliance | + | Consolidate catalogs and restores on demand from '''NetBackup''', '''BackupExec''', '''Commvault''', '''DataProtector''' and '''SpectrumProtect''' through Tranzman Appliance.<br> |
| + | This doesn't require Backup vendor for restores, as Tranzman can be used to retrieve and restore the indexed image information.<br> | ||
| + | It is useful as a replacement to backup servers for legacy restores. | ||
| + | |||
| + | |||
| + | |||
| + | '' Refer supportability matrix page for more information '' | ||
Revision as of 08:47, 6 January 2023
Contents
Transitioning Backup Environment
Transition is a process of migrating between Backup Environments. This can be between same backup vendor or different backup vendor.
Migrating the backup domains, ensure quicker and easier access towards latest software/hardware and(or) Technlogies (Cloud/Virtualization/Clustering etc.,)
Currently, there are less software which can handle the transition smoother and simpler.
Use cases
Operational reasons:
- changing software vendors
- changing platform (operating system, high availability solutions, cloud adoption or virtualization)
- Simplified management (consolidation of multiple environments or splitting a large environment)
Business reasons:
- Merges and acquisitions
- Spin-off
- Regulations
Tranzman
Tranzman provides a unique software solution for the transitioning of enterprise backup environments, irrespective of the operating system, Clustering technologies, Hardware and in some cases software versions.
It is developed by engineers, who previously designed and developed migration tools for Veritas.
Why Tranzman?
- Near ZERO Downtime
- Tranzman can perform the migration without any outage to the Origin or Destination backup environments. Downtime is only required when doing switch-over of Destination.
- Structured approach with risk mitigation at its core
- Ability to easily revert to the original environment and automated clean-up of any migrated components.
- Ability to jump releases
- Can perform transitions directly from older to latest versions skipping the intermediate upgrades.
- Granular Selectivity
- Granular level selection of images and configurations based on rules. Makes domain split and partial transitions, simple and easier.
- Concurrent Transitions
- Can perform a "many to one" merge in a single approach. Can also perform "one to many" split with selected components for each destination.
- Detailed Assessment
- Pre-assessment and Post Transition assessment provides detailed information about the Origin and Destination environments and the consistency of the components transitioned.
- Topology Transitions
- Can perform a
- Cluster to non-cluster or vice versa
- Windows to *nix or vice versa
- Virtual to Physical or vice versa (including flex instances)
- BYO to Appliance or vice versa.
Tranzman Use cases
- Same Vendor Transition
Transition between same Backup software. Mostly required when the hardware is unsupported for the latest version of backup software or changing the platform or for adopting new technologies.
Tranzman currently supports transition between NetBackup and NetBackup servers or between DataProtector and DataProtector
- Cross Vendor Transition
Transitions all Catalog objects (and some scheduling/ workload information) from Commvault, BackupExec, DataProtector, SpectrumProtect (TSM) to NetBackup
- Recovery Without Vendor
Consolidate catalogs and restores on demand from NetBackup, BackupExec, Commvault, DataProtector and SpectrumProtect through Tranzman Appliance.
This doesn't require Backup vendor for restores, as Tranzman can be used to retrieve and restore the indexed image information.
It is useful as a replacement to backup servers for legacy restores.
Refer supportability matrix page for more information