Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog

Upgrading your old Backup Exec to brand new ver. 12.5

Created: 09 Jun 2009 • 2 comments
Chris_L's picture
+3 3 Votes
Login to vote

 I just wanted to share with you what I have found useful for upgrading your old version of BE for Windows Servers. There are a couple of steps that must be performed before doing any upgrades in order to have sufficient backup of your current BE server. Before beginning the upgrade, you need to backup your C:\Program Files\Symantec\Backup Exec\Data; C:\Program Files\Symantec\Backup Exec\Catalogs folders (if you are using external SQL database make sure you have your BEDB backed up) but before that make sure you have stopped your BE and embedded DB service (Backup Exec Server and BEDB service), so if something goes wrong with the upgrade you'll have your Catalogs and DB with you. The following is step by step upgrade from older than 11d version ov BE (only 11d can be upgraded to 12.5) that you need to perform one by one.

Download link for the Backup Exec 11d:

Step 3:
Run the Browser.exe from the BE 11d folder to upgrade from 10d to 11d.

Step 4:
Download Backup Exec 12.5.

Step 5:
Run the Browser.exe from the BE 12.5 folder to upgrade from 11d to 12.5.
(Refer: Document for Multi-step upgrade path from Backup Exec 10.x for Windows Servers to Backup Exec 12.5:

Upgrade process for the Remote Agents on the Remote servers:

Step1 :
Uninstall the "Remote agent for the Windows Servers" version 10d from each remote servers Add/remove program.

Step 2:
Reboot the Remote server.

Install the Remote Agent version 12.5.

Comments 2 CommentsJump to latest comment

MitchR's picture

BE V12.5 already has some service packs out.  Don't forget to patch while you're at it...

I'm not sure about v10, but recent versions of BE have a bulk agent upgrade utility.  It's automated, and saves a lot of time.  See Appendix E of the BE 12 admin guide.

Mark this post as the solution, and have good luck for 7 years.
Forget to mark this as the solution, and tomorrow your server will crash.

Login to vote
A_ride_4_ever's picture

It has been my experience when updating from 10d to 12.5 to have a solid backup plan in the event the upgrade doesn't go smoothly. I have had a particularly difficult time with updated to 12.5 when 10d had over 70 jobs.  It hosed my database requiring reinstalling and restore of an older database. That and the upgrade of the clients on SQL and cluster  can become a nightmare in itself especially on production machines. The upgrade process to 3 days and 17 hrs of support calls to get it up and running again. Had I been prepared with redundant backup server I would not have missed 3 days of backups.

Login to vote