Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to reinstall Backup Exec 2012 on the same server while saving settings, jobs definitions and current catalog information

Created: 26 Nov 2012 • Updated: 03 Feb 2013 | 2 comments
This issue has been solved. See solution.

I need to reload a Windows Server 2003 (32-bit) server to Windows Server 2008 R2.  It will have the same host name but will be in a different domain.  I am running Backup Exec 2012 14.0 Rev. 1798 32-bit.

I found a great article "How to reinstall Backup Exec on the same server while saving settings, jobs definitions and current catalog information". 

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

Of course, it is for Backup Exec 2010, 12.5, 12.0, 11d (11.0) ...

Does anybody know where a Backup Exec 2012 (14.0) version might be, or if this article is valid.

Comments 2 CommentsJump to latest comment

Backup_Exec's picture

Hi

Please follow simple steps and you will be able to preserver all information

1 Take copy of data and catalogs folder by stopping SQl service for bkupexec

2 Once done take backup of symantec shared folder which hold your SLF files for BE 2012

3 Then you can upgrade or install the new OS on the server & considering it will same name and will be part of same domain

4 Install BE 2012 again with SLF will be in Symantec shared folder by which you can import it and ensure you patch it to same level as before like BE 2012 sp1 and few updates after it

5 Once done stop SQL service again and take backup of current data folder on desktop and backup of data and catalog folder before taken by you just paste it here directly and click on yes to overwrite

6 Then start all services and you will see you will see the previous configuration back

Yes article given by you is the perfect one only BE 2012 doesn't have besernum.xml instead edit that with Symantec shared folder & location of it is C-program file -common file -Symantec Shared if it is wi2008 then C-Program data- Application data-Symantec Shared

 

Hope that helps

Thanks

 

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

SOLUTION
pkh's picture

Since your media server will not be in the same domain, you would probably have to re-create your jobs.  It might be easier to just start afresh and not load your old jobs, i..e. do not replace the new Data directory with the old Data directory.  There should be no problems retaining your old catalogs by replacing the new Catalog directory with the old one.