Upgrading to Backup Exec 2010 Small Business Server Edition (SBSE)
| Article:TECH178289 | | | Created: 2012-01-05 | | | Updated: 2012-01-23 | | | Article URL http://www.symantec.com/docs/TECH178289 |
Problem
About upgrading from previous versions of Backup Exec SBSE
Solution
You can use the Backup Exec installation media to upgrade from Backup Exec version 11d and later to the current version. No separate upgrade utility is necessary. The current version of Backup Exec replaces any previous versions. Separate installations of different versions cannot exist on the same computer. Most settings and all catalogs and all data directories from previous versions of Backup Exec are kept, unless you choose to remove them. Backup Exec 2010 SBSE can read and restore data from any previous version of Backup Exec SBSE, except for data that is no longer supported.
For more information see the Backup Exec 2010 Software Compatibility list:
http://www.symantec.com/docs/TECH137682
When you upgrade, Backup Exec automatically converts your existing definitions, configurations, and jobs to the current version. If any aspect of the data migration fails, then Backup Exec displays an error message stating that the upgrade did not complete successfully. Backup Exec provides you with the choice to either return to the previous version of Backup Exec or to continue with the upgrade. If you choose to continue with the upgrade, then devices, media, and jobs are not migrated from the previous version of Backup Exec.
Backup Exec 2010 SBSE can communicate with Backup Exec 12 SBSE Remote Agent for Windows Systems and later (Small Business Server Premium Edition only). However, upgrading the remote computer to the latest version of the Remote Agent for Windows is recommended.
Before you upgrade Backup Exec, do the following:
- Delete the job histories and the catalogs that you no longer need to shorten the upgrade window.
- Run a database maintenance job.
- Upgrade any existing instances of SQL Server 2000 to either SQL Server 2005 with SP3 or to SQL Server 2008.
You cannot change the configuration of your media server during an installation. You cannot change the database location during the upgrade process. If you want to change the database location after the upgrade, use BEUtility.
Note: If you upgrade from a previous version of Backup Exec that uses a non-English version of Windows, you must download the SQL Express SP3 setup file for that language from the Microsoft Web site.
Steps for upgrading from Backup Exec 11.x or later
- Run a full backup of the media server.
- Reboot the computer to confirm that all Windows and other third party patches or updates have completed.
- Apply all of the latest firmware and driver updates to the computer's hardware (SCSI/Raid, network card, motherboard, video card, etc.). Updates for computers that are proprietary models (HP, Compaq, DELL) 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 computer should be applied.
- Review the Backup Exec 2010 SCL (Software Compatibility List) and HCL (Hardware Compatibility List) to confirm the applications and tape hardware is compatible with Backup Exec 2010
Hardware Compatibility List
http://www.symantec.com/business/support/index?page=landing&key=15047
Software Compatibility List
http://www.symantec.com/business/support/index?page=content&id=TECH137682&key=15047
- Write down the existing serial numbers (Product Activation Keys) from the existing version. These keys are located in a file named besernum.xml at the root of the C:\Windows , C:\Winnt directory,
C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec. Or
C:\Users\All Users\Symantec\Backup Exec.
- From Backup Exec, confirm there is a valid System Account. From the Network menu, click Logon Accounts. Logon to the media server as this account. Also make sure the Backup Exec Services are also running under this account (except for the Remote Agent which logs on as Local System) in the Windows Services Applet.
Note: 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
- If you don’t have installation media, download the Backup Exec 2010 R3 SBSE Installation Software from: https://www4.symantec.com/Vrt/offer?a_id=93355
- Launch the older version of Backup Exec and delete any unnecessary data, including jobs, selection lists, policies, media sets, job histories, catalogs, alerts, logon accounts, etc. which are no longer used.
- Make sure no jobs are scheduled to run.
- 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).
- Launch the Backup Exec 2010 SBSE installation from the installation media. Select the same options for the installation that are listed in the besernum.xml file. If you do not have valid Backup Exec 2010 license keys, select the evaluation mode for each of the options and obtain valid license keys from Symantec or your reseller. If you have valid license keys, enter them as appropriate. Accept the defaults for each dialog until the installation wizard completes.
- Run LiveUpdate to install all patches/updates when prompted.
- A reboot may be required.
- Launch Backup Exec 2010 SBSE and confirm that all the jobs, selection lists, policies, media sets, hardware, etc. show properly.
|
|
Article URL http://www.symantec.com/docs/TECH178289
Terms of use for this information are found in Legal Notices









Thank you.