How to: Direct upgrade path from Backup Exec 11d/12.0/12.5/2010 for Windows Servers to Backup Exec 2010 R2

Article:TECH148394  |  Created: 2011-01-18  |  Updated: 2011-05-05  |  Article URL http://www.symantec.com/docs/TECH148394
Article Type
Technical Solution

Product(s)

Environment

Subject

Issue



How to: Direct upgrade path from Backup Exec 11d/12.0/12.5/2010 for Windows Servers to Backup Exec 2010 R2


Solution



Backup Exec for Windows Servers versions 11d/12.0/12.5/2010 can be directly upgraded to version 2010 R2.  A fresh installation of Backup Exec 2010 R2 can also be performed, if it is not necessary to retain the existing version's configuration information.

Note:  Before either performing a direct 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 11d/12.0/12.5/2010 are also compatible with version 2010 R2

 

Backup Exec (tm) 2010 and 2010 R2 Software Compatibility List (SCL) - http://www.symantec.com/docs/TECH137682

Backup Exec (tm) 2010 and 2010 R2 Hardware Compatibility List (HCL) - http://www.symantec.com/docs/TECH137050

 

5. Document the existing serial numbers (Product Activation Keys) from the existing version.  http://www.symantec.com/docs/TECH87335  -  Where does Backup Exec store the licensing information

 

6. Stop all of the Backup Exec services, including the SQL(BKUPEXEC) serviceCopy the catalogs and data folders from the <volume>:\Program Files\Symantec\Backup Exec directory to an alternate, safe location.

 

7. Confirm there is a valid System Account at Network > Logon Accounts in the Backup Exec User Interface.  Logon to the media server as this account.  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

 

 

 

 

WHEN NOT TO UPGRADE, WHEN TO UPGRADE AND HOW TO PERFROM A DIRECT UPGRADE:

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 an upgrade.  

If it is not necessary to retain the settings from the existing version, then a fresh installation of Backup Exec 2010 R2 can be performed by simply uninstalling the existing version, rebooting, and then running the Backup Exec 2010 R2 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 on this, review the following document:

How to import Catalogs into a Backup Exec 12.x or later for Windows Servers 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 an upgrade to retain this information.

It also may be necessary to upgrade a CASO (Central Administrator Server Option) or SSO (San Shared Storage Option) Primary Machine, so that all the managed media servers can still properly communicate with the main media server once it is running version 2010 R2.  These managed machines will need to be upgraded too, once the CASO or SSO Primary machine is at version 2010 R2.  For more information, review the "Upgrading a CASO Environment" Section in the following document:

Managing Backup Exec <CASO> (Central Administration Server Option) in a Large Scale Environment

http://www.symantec.com/docs/TECH60559



III.  How to perform a direct upgrade to 2010 R2

1.  If it is not readily available, download the Backup Exec 2010 R2 Installation Software.

Backup Exec 2010 R2  =  https://www4.symantec.com/Vrt/offer?a_id=93355

Backup Exec 2010 R2 for Windows Small Business Servers  =  https://www4.symantec.com/Vrt/offer?a_id=93356 

 

2.  In the Backup Exec Graphical User Interface (GUI), cleanup all unnecessary data

NOTE:  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:

How to run a extensive database repair and cleanup of the Backup Exec database when it is found to be inconsistent

http://www.symantec.com/docs/TECH67239

 

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 real-time virus scanner, are enabled or running (stop all third party, non-Windows Services if necessary), then launch the Backup Exec 2010 R2 installation.

 

6.  During the installation wizard, complete each section or accept the defaults and continue to click Next until the installation completes

NOTE:  Select the same options for the installation that are listed in the besernum.xml file and for which licensing (Product Activation Keys for version 2010 R2) is available

 

7.  Run LiveUpdate to install all patches/updates when prompted reboot (required)

 

8.  Review the following documents:

Post installation tasks (page 182) in BE 2010 R2 Administrator’s guide:  http://www.symantec.com/docs/DOC2211

 

Upgrading Backup Exec options on remote computers

Not yet available

 

Best Practices for Backup Exec 2010 R2 - Table of Contents

Not yet available (review Best Practices for Backup Exec 2010 – Table of Contents for similar information - http://www.symantec.com/docs/TECH126401)

 





Article URL http://www.symantec.com/docs/TECH148394


Terms of use for this information are found in Legal Notices