9.x versions of Backup Exec for Windows Servers can only be directly upgraded to version 11.x and then a second upgrade to version 2010 or 2010 R2 must be performed. A fresh installation of Backup Exec 2010 or 2010 R2 can also be performed, if it is not necessary to retain the existing version's configuration information.
Please Note: Before either performing a two stage upgrade or fresh install of Backup Exec 2010, the following is strongly recommended:
1. Run a full backup of the local media server.
2. Reboot the machine to confirm all Windows and other third party patches or updates have completed.
3. Make sure all the latest firmware and driver updates have been applied to the machine's hardware (i.e.: SCSI/Raid, Network Card(s), Motherboard, Video Card, etc...). Updates for machines that are proprietary models (not a custom built clone) should be obtained from the hardware manufacturer. For example, if the media server is an HP Model, all the latest SofPaqs and RomPaqs for that machine should be applied.
4. Review the Backup Exec 2010 and 2010 R2 SCL (Software Compatibility List) and HCL (Hardware Compatibility List) to confirm the applications and tape hardware being used with version 9.x are also compatible with version 2010.
5. Document the existing serial numbers (Product Activation Keys) from the existing 9.x version. These keys are located in a file named besernum.txt at the root of the C:\Windows or C:\Winnt directory.
6. Stop the MSSQL$BKUPEXEC SQL Service that Backup Exec uses. Copy the catalogs and data folders from the \Program Files\Veritas\Backup Exec\NT directory to an alternate, safe location.
7. Confirm there is a valid System Account at Network, Logon Accounts in the Backup Exec User Interface (Figure 1). Logon to the media server as this account. Make sure this same account is also running the Backup Exec Services (except for the Remote Agent which logs on as Local System) in the Windows Services Applet.
: If the services are running under a different account and/or if the System Account/credentials are no longer valid, perform the steps in the following document: How to resynchronize the Backup Exec for Windows Servers System Logon/Service account and installation to potentially resolve functional issues with the application - http://www.symantec.com/docs/TECH59776
WHEN NOT TO UPGRADE, WHEN TO UPGRADE AND HOW TO PERFROM THE TWO STAGE UPGRADE PROCESS
I. When not to upgrade
In stand-alone instances of Backup Exec, when there are a limited number of jobs, selection lists, policies, media sets, etc... , there may not be a benefit to performing a two stage upgrade. It may even take less time to recreate the configuration from a fresh install than it takes to perform the upgrade.
If it is not necessary to retain these settings from the 9.x version, then a fresh installation of Backup Exec 12.5 can be performed. Uninstall version 9.x, reboot, and then run the Backup Exec 2010 installation. After the installation completes, the catalogs from the previous installation can be copied into the new catalogs directory to retain the previous restore selections, so the previous backup media do not have to be cataloged. For more information, review the following document: How to import Catalogs into a Backup Exec Installation - http://www.symantec.com/docs/TECH68896
II. When to upgrade
When there are a large number of selection lists, jobs, policies, media sets, etc... that would take a considerable amount of time to recreate, it may be desirable to perform the two stage upgrade to retain this information.
III. How to perform the two stage upgrade process
1. If it is not readily available, download the Backup Exec 11.x and 2010 R2 Installation Software
Please note: If for any reason the downloads are not available after clicking on the links above, contact Customer Care to obtain the software for the intermediary upgrade.
2. In the Backup Exec Graphical User Interface (GUI), cleanup all unnecessary data
Example: delete any jobs, selection lists, policies, media sets, job histories, catalogs, alerts, logon accounts, etc... which will not be used and are obsolete
3. Make sure no jobs are scheduled to run and stop all the Backup Exec Services on any other media servers that are being managed by this media server.
4. Launch BEUtility and perform the steps in the following Technote:
Please note: There may not be any inconsistencies at all in the database. Performing the steps in the Technote above is the best way to confirm this and to optimize the database. If all of the tasks in this document complete successfully and without errors, proceed with the upgrade. If there are any failures, contact Symantec Technical Support for further assistance.
5. Make sure no other third party applications, such as a realtime virus scanner, are enabled or running (stop all third party, non-Windows Services if necessary), then launch the Backup Exec 11.x installation. Select the same options for the installation that are listed in the besernum.txt file. If any Product Activation Keys are listed, remove them, and click Next to go into evaluation mode. Continue to click Next and accept the defaults until the installation completes. Reboot if prompted.
6. Launch the Backup Exec 11.x GUI. Confirm that all the jobs, selection lists, policies, media sets, hardware, etc... show properly. If so, close the GUI and proceed to step 7. If not, contact Symantec Technical Support for further assistance.
7. Make sure, once again, that no other third party applications, such as a realtime virus scanner, are enabled or running (stop all third party, non-Windows Services if necessary), then launch the Backup Exec 2010 or 2010 R2 installation. Enter the Product Activation Keys, select the proper options, and click Next until the installation completes successfully. Run LiveUpdate to install all patches/updates when prompted. Reboot.
8. Review the following documents from the Backup Exec 2010 or 2010 R2 Admin Guide:
Upgrading Backup Exec options on remote computers & Post-installation tasks