How to: Multi-step upgrade path from Backup Exec 10.x for Windows Servers to Backup Exec 12.5

Article:TECH68071  |  Created: 2009-01-20  |  Updated: 2012-10-24  |  Article URL http://www.symantec.com/docs/TECH68071
Article Type
Technical Solution

Product(s)

Issue



How to: Multi-step upgrade path from Backup Exec 10.x for Windows Servers to Backup Exec 12.5


Solution



10.x versions of Backup Exec for Windows Servers can be directly upgraded to version 11.x and then a second upgrade to version 12.5 can be performed.  A fresh installation of Backup Exec 12.5 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 12.5, 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 for Windows Servers 12.5 SCL (Software Compatibility List) and HCL (Hardware Compatibility List) to confirm the applications and tape hardware being used with version 10.x are also compatible with version 12.5.
 
Symantec Backup Exec for Windows Servers 12.5 Software Compatibility List (SCL)
 
Symantec Backup Exec for Windows Servers (tm) 12.5 Hardware Compatibility List (HCL)
 
  http://www.symantec.com/docs/TECH62114  

5. Document the existing serial numbers (Product Activation Keys) from the existing 10.x version.  These keys are located in a file named besernum.xml at the root of the C:\Windows or C:\WINNT directory.

6. Stop the SQL Service (MSSQL$BKUPEXEC or SQL SERVER (BKUPEXEC) ) that Backup Exec uses.  Copy the catalogs and data folders from the X:\Program Files\Symantec\Backup Exec directory to an alternate, safe location. After the copy completes, start the SQL Server (BKUPEXEC) or MSSQL$BKUPEXEC services.

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

Figure 1
 

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 perform 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, media vaults, media that is stored offsite, 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 10.x version, then a fresh installation of Backup Exec 12.5 can be performed.  Uninstall version 10.x, reboot, and then run the Backup Exec 12.5 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.  It will require the inventory of all of the media to be able to be inserted back into the database so that the catalogs can be re-associated to the media to which it belongs.  If an inventory is not performed, this will prevent the catalog selections from being seen in the restore job.  For more information on this, review the following document:

 How to import Catalogs into a Backup Exec 12.x 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, media vaults, media that is stored offsite, 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.  

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 12.5.  These managed machines will need to be upgraded too, once the CASO or SSO Primary machine is at version 12.5.  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 the two stage upgrade process
 
1. If it is not readily available, download the Backup Exec 11.x and 12.5 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
 
(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 Article:
 
How to run a extensive database repair and cleanup of the Backup Exec database when it is found to be inconsistent
 
Please note:  There may not be any inconsistencies at all in the database.  Performing the steps in the Article 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 11.x Installation.  Select the same options for the installation that are listed in the besernum.xml 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 real-time virus scanner, are enabled or running (stop all third party, non-Windows Services if necessary), then launch the Backup Exec 12.5 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 12.5 Admin Guide:
 
Upgrading Backup Exec options on remote computers
 
Post-installation tasks
 

Supplemental Materials

SourceUMI
ValueV-225-170-3
Description

Documented two stage process to upgrade from Backup Exec 10.x to Backup Exec 12.5


SourceUMI
ValueV-225-170
Description

Upgrading this version of Backup Exec, or any version of Backup Exec that is prior to version 11d is not supported. Symantec Backup Exec (TM) 12.5 for Windows Servers supports upgrading from version 11d or later


SourceUMI
ValueV-269-13
Description

Upgrade fails



Legacy ID



319925


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


Terms of use for this information are found in Legal Notices