The Backup Exec™ Migration Assistant lets you migrate your data from one Backup Exec server (source) to another Backup Exec server (destination). If you are still using Backup Exec 2010 and would like to upgrade to Backup Exec 20.1, you can use the Backup Exec™ Migration Assistant.
It is also important to install any available updates for your current Backup Exec version before attempting an upgrade. I highly recommend running a database maintenance job and deleting any job histories and catalogs you won't need in the future. The next step is to clean up your existing Backup Exec deployment. First, you need to determine the licensing requirements (see the infographic below). When planning a Backup Exec 20.1 upgrade, there are two main steps. When performing an in-place upgrade, Backup Exec preserves all of the catalogs and data directories from the previous version, unless you opt to remove them. This means the organization would have to perform a preliminary upgrade to version 2014 or higher, and then a secondary Backup Exec 20.1 upgrade. Organizations running an earlier version of Backup Exec can theoretically still perform an in-place upgrade if Backup Exec is running on a 64-bit OS, but a multi-step upgrade would be required. In-place upgrades are possible as long as an organization is using version 2014 or higher, and is not running Backup Exec on a 32-bit OS. Speaking of upgrades, it is important to note that customers who are still on older versions will need to be on at least Backup Exec 2014 in order to upgrade to Backup Exec 20.1.
If you’ve been waiting to upgrade your Backup Exec, then wait no longer! Please review the full release notes and I’d also recommend the blog series on VOX if you need help getting started. Along with the numerous enhancements, there are several bug fixes that should make your experience even better. With Backup Exec 20.1, Veritas introduced the largest functional release in Backup Exec’s history delivering key functionality that simplified data protection and recovery.