Pre-Upgrade Preparation & Data Safety

• Identify the Backup Exec Service Account (BESA):

  Log in to the Backup Server using your Backup Exec service account credentials.

  Open the Windows Services Management Console (services.msc).

  Review the Log On As user account listed for the Backup Exec services. This account will be needed later during the upgrade process.

• Stop Backup Exec and Database Services:

  Stop all running Backup Exec services.

  Stop the SQL service hosting the Backup Exec database (SQL Server (BKUPEXEC64) or SQL Server (BKUPEXEC)).

• Backup Critical Data Folders:

  Create a copy of the Data and Catalogs folders and store them in a safe location:

  X:\Program Files\Veritas\Backup Exec\

  or X:\Program Files\Symantec\Backup Exec\ (Note: X represents the drive letter where Backup Exec is installed).

• Backup Custom Reports (If Applicable):

  If custom reports have been configured, back up the Reports directory:

  X:\Program Files\Veritas\Backup Exec\Reports

• Restart SQL Service:

  Start the SQL Server instance service (SQL Server (BKUPEXEC64) or SQL Server (BKUPEXEC)).

Phase 2: Unblocking & Running the Installer

• Unblock Downloaded Files & Mount ISO:

  Certain Windows operating system security policies block downloaded archive and image files. Unblock the file before extraction to prevent setup errors.

  Unblock Procedure: Right-click the downloaded .zip file, select Properties, check the Unblock box, and click Apply. Repeat this process for the extracted .iso file if necessary, then mount the ISO image.

• Launch Setup:

  Open the mounted ISO directory in File Explorer.

  Right-click Browser.exe and select Run as Administrator.

Important Notes regarding SQL Server (Backup Exec 22 and above):

• Upgrading to version 22.0 or higher deploys a 64-bit BKUPEXEC64 SQL 2017 Express instance. The legacy 32-bit BKUPEXEC SQL instance will be automatically removed near the end of the upgrade.
• If your existing Backup Exec uses a custom named SQL instance (anything other than default BKUPEXEC), the upgrade will retain that custom SQL instance and version.

• Start Installation Wizard:

  In the DVD Browser menu, click Backup Exec

• Accept License Agreement:

  Review the software license terms, select I accept the terms of the license agreement, and click Next.

• Select Installation Type:

  Select Install Backup Exec software and features (Local Installation) and click Next.

• Run Environment Check:

  Allow the wizard to complete the Windows Server environment checks. Resolve any highlighted prerequisites before proceeding.

Phase 3: Licensing & Migration

• Enter License Keys / Trial Mode Setup:

  Enter your Entitlement ID or click Import License File (.slf).

• Trial Mode Upgrade Path:

  If upgrading from a version earlier than v25 and you only have a license file for version 25, leave the key fields blank and click Next. A pop-up prompt will inform you that Trial Mode enables all options for 60 days. Click OK to proceed. You can import your permanent .slf license files after setup completes.

• Enter Service Account Credentials:

  Enter the User Name, Password, and Domain for the Backup Exec Service Account (BESA), then click Next.

• Database & Settings Migration:

  Advance through the wizard to the Migration step. Wait for the wizard to process and migrate configuration data.

• Review Migration Report:

  Once migration completes successfully, review the summary report. Select I have read and acknowledge the changes in the migration report and click Next.

• Installation Progress:

  Setup will begin deploying prerequisite packages and Backup Exec core installation files.

• Complete & Reboot:

  When prompted, select Reboot system and click Finish. All pre-existing configurations will be retained upon reboot.

Phase 4: Post-Upgrade Conversion & Agent Updates

• Deduplication Storage Conversion:

  Upon reboot, if a Deduplication Storage folder is present, it will initially appear as OFFLINE.

  Backup Exec will display an alert stating that Deduplication Storage conversion has started.

• Critical Deduplication Conversion Guidelines:
  • Storage Requirements: The drive hosting the Deduplication folder requires at least 12% free disk space for conversion to finish successfully.
  • Do Not Interrupt: Do NOT restart Backup Exec services while conversion is actively running.
  • Verification Log Location: Track conversion status in: C:\Program Files\Symantec\Backup Exec\Logs\PDDE10 Conversion log

• Restart Services:

  Once the log confirms completion ("Congratulations! The conversion has finished successfully!"), open Backup Exec Services Manager, enable deduplication services, and select Restart all services. Devices will come online.

• Upgrade Remote Agents:

  Remote agents running on client servers must be updated to match the backup server:

  • Automatic/Console Push Upgrade: Go to the Backup and Restore tab, right-click the target remote server, and click Update.
  • Manual Local Agent Upgrade:
    1. Copy the C:\Program Files\Veritas\Backup Exec\Agents folder from the Backup Exec server.
    2. Paste the Agents folder onto the target remote machine.
    3. Navigate to Agents\RAWS64 on the target server and execute setup.exe.
    4. Reboot the remote machine if prompted.
    5. From the Backup Exec Administration console, right-click the remote machine and select Establish Trust.