Symantec 2010 upgrade to 2012

[sanjay_patel]

Hello,

i have Symantec Exec 2010 R3 on my production server.

now we have purchase license for Symantec Exec 2012. so can i upgrade my productoin server from 2010 to 2012 ?

Thanks

Sanjay

[Backup_Exec1]

Hi
If you are going to upgrade to BE2012 on same server ,were BE2010 is already installed ,then it will be an in place upgrade. Were all your settings and catalog would be migrated when you install BE2012 on top of existing version ,please refer to upgrade guide link below,

http://www.symantec.com/docs/TECH180232
If you have BE2010 on 1 machine and BE2012 on other machine and you want to migrate your all setting of BE2010 from one machine to other machine were BE2012 is installed please follow steps below,

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

To summarize this BE2012 is completely different version that older version of backup exec ,so it is different is design and working too, for example in earlier version use resource centric approach but BE2012 uses server centric approach due to which you will see job per server and not as like single selection and multiple servers selected in it. So to understand the changes in BE2012 please read upgrade guide carefully.

Thanks.

[AmolB · Accepted solution]

Hello Sanjay

 Direct upgrade is possible from BE2010 to BE2012.

 Before upgrading stop SQL server BKUPEXEC service and make a copy of DATA and CATALOGS

 folder located in the installation directory of Backup Exec.

Also refer to install blog https://www-secure.symantec.com/connect/articles/preparing-install-or-upgrade-be-2012

Note: There are lot of enhancements and UI changes in BE2012 so i would suggest you to install

2012 in a test environment and play with the UI and get a feel of new features.

[sanjay_patel]

Hi Amol,

Thanks for the response, i will try and update how does it works

Many Thanks,

Sanjay

[sanjay_patel]

Hello,

Thanks, let me work on it and will give you updates.

Sanjay

[JavierTI]

a technical guide to upgrade in place, sometimes put a lot of documentation, which is not bad but is needed in the field guides.