There are two ways to do this:
1- In place upgrade:
This is a direct upgrade of the existing installation, and here is how you do it:
- First its always backing up your configuration, so stop the BackupExec SQL instance service, and copy the directories “Data” and “Catalogs“ which are located here <root>:\Program Files\Symantec\Backup Exec\.
- Download the ISO image from here https://fileconnect.symantec.com/ you can either burn it, mount it via a virtual drive or extract it.
The installation is straight forward, just next your way out till its done.
- When the installation is done, run live update where you’ll get SP2 and some hotfixes.
- Finally, the setup doesn’t require a reboot but I do recommend to reboot the server in case you’re utilizing AOFO (Advanced Open File Options).
- When the server is up, push the new agent to the already published servers (a reboot might be required for those servers) and you’re done.
2- A fresh installation setup:
The draw back of this, is that Symantec DOES NOT SUPPORT TAKING A COPY OF THE BACKUP CONFIGURATION FROM 2010 AND THEN APPLYING IT TO AN 2010 R3 INSTALLATION using BE Utility, if you do so the Backup Exec services won’t start because of a database schema mismatch.
Even though I tried taking the BEDB.bak and recovering it, then I tried upgrading the schema via BEMIG.exe which is supposed to fix the database and insert the new schema in it along with all its tables and views yet at a certain point it fails because it can’t find a certain column.
So eventually you will have to return into a blank database and start all over.
After you’ve finished the installation and updated your server to SP2:
- Push the new agent to the published servers.
- Print all your jobs to an XPS file and copy them to the new server.
- Configure your devices, Backup-to-Disk folders, tape libraries, etc.
- Configure the default System Log-On Account.