Please enter search query.
Search <product_name> all support & community content...
Article: 100049026
Last Published: 2025-04-21
Ratings: 3 2
Product(s): Backup Exec
Description
Tips and recommendations to help you upgrade Backup Exec more effectively.
Steps for Backup Exec Upgrades/Migrations.
- Apply the Latest Backup Exec Patch or Hotfix to the existing Version of Backup Exec. Run Arctera Update before you upgrade Backup Exec to install the latest Feature pack, Service pack, or Hotfixes for the version of Backup Exec that is currently installed. The patch can also be downloaded manually from 100019916.
- Restart the Backup Exec server after BE Patches are installed.
- Apply the latest SQL Service Pack or update to the Backup Exec SQL Instance “BKUPEXEC64” if you use the default SQL Express instance for the Backup Exec Database. Latest updates for Microsoft SQL Server
- Restart the server after installing the SQL Updates.
- Ensure that the most recent version of Microsoft.NET framework is installed on the computer on which you want to install Backup Exec. Install the Net 3.5 Framework Role/Feature and the latest version of .Net framework 4.x supported by the Operating System version (Recommended).
- Run Microsoft Windows Update. Backup Exec uses many Microsoft technologies that may have been updated since Backup Exec's release.
- Document your current configuration and settings before you upgrade Backup Exec. You can verify that your configuration after the upgrade is complete.
- Delete any unnecessary job history and alert history before an upgrade to help expedite the process.
- Perform database maintenance on your Backup Exec Database immediately before an upgrade.
- Back up your server before you install or upgrade any software, including Backup Exec. Make a copy of Backup Exec's Catalogs and Data folders.
- Upgrade the central administration server first if you perform a rolling upgrade in an existing Central Admin Server Option (CASO) environment. Upgrade the managed Backup Exec servers as soon as possible afterwards.
Note: Review the chart from this Technote 100018032 to confirm if an upgrade path exists from the version Backup Exec is being upgraded. - Disable communications with managed Backup Exec servers in CAS environments.
- Logon to the server as the Backup Exec System Logon Account (BESA) during the installation. The BESA account is the account that will be used to run the Backup Exec services and perform backups. Reference: What rights does the Backup Exec service account need?
- Temporarily disable Antivirus software installed on the BE server during the Backup Exec software upgrade or installation.
- Disable any monitoring utilities that may restart services.
- Disable UAC (Recommended during Installation).
- Install Backup Exec to a drive that is neither compressed nor encrypted if you use SQL Express for the Backup Exec Database.
- Run the installation wizard from the local server, from a DVD image on the local server. (Recommended)
Note: Ensure that the path to the Backup Exec installation media does not exceed 60 characters. If the Backup Exec installation media is on a network share or in a custom folder that exceeds 60 characters, the installation may fail. To resolve this issue, shorten the path name or move the installation media to the root of the drive on the local system, and then run the installation again. - Ensure that you review and acknowledge the upgrade notice about the disk reclamation process called data lifecycle management (DLM) during the upgrade.
Note: This may not be seen in newer Backup Exec release upgrades. - Ensure that you review and acknowledge the Migration Report after the migration completes to continue the upgrade process.